On 23-03-12 14:49, Scott Gould wrote:
Our syslog has been filling up for some time with this stuff and we only just noticed due to logrotate breaking on us. For what appears to be every django request across all virtual hosts, we are getting a pair of lines, like so (blank lines inserted by me): Jan 27 14:48:52 cloweb01 apache2: SessionMiddleware.process_request - id 0x7f6dabfb35d0 - cookie None - session 915ffaa7831b5de78876abb7746dfc1f - path /serverstatus/api/v1/status/ Jan 27 14:48:52 cloweb01 apache2: WSGIHandler.__call__ - id 0x7f6dabfb35d0 - cookie None - session 879f844cb6ea0213b445f60e11b22978 - path /serverstatus/api/v1/status/
I looked at django/contrib/sessions/middleware.py and there's no logging or printing happening there.
That the syslog ends up with this info probably means that django prints it out on the console, which would normally end up in your apache's error log. Probably you configured apache to send it to the syslog instead.
Printing on the console means "print ..." or a logger that's configured to print to the console. Did you do the latter?
My guess: someone put a print statement in django/contrib/sessions/middleware.py for debug purposes. So check the django that your site is using and see if you have to beat someone with a stout stick.
Reinout -- Reinout van Rees http://reinout.vanrees.org/ rein...@vanrees.org http://www.nelen-schuurmans.nl/ "If you're not sure what to do, make something. -- Paul Graham" -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
