| 1 |
Apparently, though unproven, at 08:15 on Wednesday 04 May 2011, Joost |
| 2 |
Roeleveld did opine thusly: |
| 3 |
|
| 4 |
> On Wednesday 04 May 2011 13:48:48 Adam Carter wrote: |
| 5 |
> > > Well, 2.2.17 is indeed my server, but I decided to stop it and start it |
| 6 |
> > > again. Current log files showed up. |
| 7 |
> > > Problem solved, by brute force again, and without any epiphanies of |
| 8 |
> > > understanding. |
| 9 |
> > |
| 10 |
> > Last guess - logrotate is managing the log files but not reloading apache |
| 11 |
> > afterwards. Check that the entries in /etc/logrotate.d/apache2 have a |
| 12 |
> > line in there that runs /etc/init.d/apache2 reload. |
| 13 |
> |
| 14 |
> Adam, |
| 15 |
> |
| 16 |
> I think you got a really good guess. :) |
| 17 |
> Especially as the log-files listed by lsof have status "deleted": |
| 18 |
> ** |
| 19 |
> apache2 5288 root 9w REG 8,44 57327591 204998 |
| 20 |
> /var/log/apache2/access_log-20110204 (deleted) |
| 21 |
> ** |
| 22 |
> |
| 23 |
> Interesting things happen when a file is deleted while a process still has |
| 24 |
> access. |
| 25 |
|
| 26 |
You mean like as in it's name goes away and absolutely nothing else changes |
| 27 |
whatsoever? |
| 28 |
|
| 29 |
The only trouble you can run into is that new process that did not have the |
| 30 |
file open now cannot find it. |
| 31 |
|
| 32 |
-- |
| 33 |
alan dot mckinnon at gmail dot com |
Archives