LOL - that makes sense - I'll get this amended As always, thanks for the quick response!
Cal On Wed, Dec 21, 2011 at 6:49 AM, Roberto De Ioris <[email protected]> wrote: > > > Hey Roberto, > > > > Seem to be having an issue with logdate. > > > > Log shows: > > 1 - spawned uWSGI worker 1 (pid: 21363, cores: 1) > > 1 - spawned uWSGI worker 2 (pid: 21364, cores: 1) > > 1 - spawned uWSGI worker 3 (pid: 21366, cores: 1) > > 1 - spawned uWSGI worker 4 (pid: 21367, cores: 1) > > 1 - *** HARAKIRI ON WORKER 4 (pid: 21367) *** > > 1 - HARAKIRI: --- uWSGI worker 4 (pid: 21367) WAS managing request > > /bulklpscan since Tue Dec 20 20:27:47 2011 --- > > 1 - DAMN ! worker 4 (pid: 21367) died :( trying respawn ... > > 1 - Respawned uWSGI worker 4 (new pid: 24228) > > > > > > Config says: > > <logto>/home/chroot/home/duke_dev/webapps/ddcms/log/uwsgi.log</logto> > > <logdate/> > > > > Yet the timestamp isn't shown on the log file, and it shows the number > "1" > > also.. not sure why :X > > > > Any thoughts?? > > > > > > On pre-1.0 releases you have to use > > <logdate>true</logdate> > > as <logdate/> translates to > > logdate = 1 > > and strftime parses it as a date :( > > (in latest tip a special condition has been added) > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
