| 1 |
On Tue, May 3, 2011 at 11:15 PM, Joost Roeleveld <joost@××××××××.org> wrote: |
| 2 |
|
| 3 |
> On Wednesday 04 May 2011 13:48:48 Adam Carter wrote: |
| 4 |
> > > Well, 2.2.17 is indeed my server, but I decided to stop it and start it |
| 5 |
> > > again. Current log files showed up. |
| 6 |
> > > Problem solved, by brute force again, and without any epiphanies of |
| 7 |
> > > understanding. |
| 8 |
> > |
| 9 |
> > Last guess - logrotate is managing the log files but not reloading apache |
| 10 |
> > afterwards. Check that the entries in /etc/logrotate.d/apache2 have a |
| 11 |
> line |
| 12 |
> > 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 |
> -- |
| 27 |
> Joost |
| 28 |
> |
| 29 |
> Indeed they do. I used to teach it to my students as a "technique" for |
| 30 |
getting |
| 31 |
a *really* temporary private file (combined with O_EXCL). |
| 32 |
|
| 33 |
I'm about to try this, and I may change it a bit because when I restarted |
| 34 |
apache, |
| 35 |
reload didn't work. I had to stop it and restart it. Maybe I'll submit a |
| 36 |
bug if I |
| 37 |
can make sense out of what happens with 'reload' and it always happens. |
| 38 |
|
| 39 |
-- |
| 40 |
Kevin O'Gorman, PhD |
Archives