[Trac-dev] Re: t.e.o updated to latest trunk

Christian Boos wrote:
> Indeed, it was a cache issue in Firefox - I thought I did a force
> reload, but probably didn't. I'm not sure why this explicit reload is
> needed at all (Firefox bug? server setup?).

Probably a browser issue since the server doesn't send any Expires 
headers at all, just normal Last-Modified and Etag headers. Are you 
perhaps behind some kind of (transparent) http proxy?

>> This morning I removed a trac restart script from the t.e.o crontab and
>> so far the memory usage seems to be fairly stable without it, but I'll
>> continue monitoring it:
>>
>> http://www.edgewall.org/rrd/mem-day.png
> 
> Interesting, so what exactly happened near 6:20 AM this morning?
> (I guess that what happened at 09:40 AM was a server restart  ).

Yeah, it took a while to figure out what happend at 6:25 but then I 
realized that that's the exact time the daily crontab jobs are started.
The spike in memory allocation was caused by logrotate restarting 
lighttpd in a way that didn't manage to kill all running fastcgi 
processes before starting a new set of processes. This should be fixed 
now so tomorrow at the same time we should see a drop in memory usage 
instead of an increase.

/ Jonas

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---