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