First of all, I’m using Windows, just to make that clear. I am using cmd.exe to manage runserver and the server runs just fine. However, sometimes, on a seemingly random basis, Django simply stops writing to stdout! The server responds to my requests and everything, but nothing gets printed.
To make it even clearer, I’m not even talking about print in my Django code, so that cannot be the problem. I’m talking about when it prints e.g. GET /someurl HTTP/1.1, yada-yada… Hitting Ctrl+Break and restarting the server doesn’t help. However, if I exit the command prompt and start a new one and run the server in that one, it starts working again.
Any ideas about what’s going on? This is with Django 1.0.2 final and Python 2.6.2.
Maybe a bit of a stretch,but under Python 2.6 under Linux using the Twisted framework (instead of Django), I had this behaviour occur anytime my application sent a NULL to stdout and stdout was redirected to syslog. I had assumed this was a bug in the twisted framework’s syslog implementation, but maybe its something more. Can you tell from either logging or client activity what the last thing it was doing before losing stdout and see if it is a) always in one of a handful of places and 2) if you are sending anything funky out at the time?