On Sun, Oct 11, 2009 at 9:23 AM, Roodie <istvan.far...@gmail.com> wrote:
> > Hello, > > I have a hard-to-identify problem on one of our production servers. We > host some Django-based websites, and one of them ( a small news > portal ) produces this strange error - sometimes users get blank pages > when they try to access the portal. A browser refresh a few second > later solves the problem, but the issue is more serious on the admin > interface, where it means data loss ( users post the form, and the > data simply disappears ). > > The setup: > Ubuntu Linux server > Apache2 > Latest Django ( packaged release version ) > Latest MySQL version > > The Django site is running using flup / FCGI. > > The same portal "engine" ( in reality just a bunch of modules ) is > running perfectly on 2 other servers using the same setup. The only > difference is that the failing portal has much more information > displayed on the front page ( many-many queries, most of them > cachedusing the filesystem cache ) and slightly higher traffic. The > log files are empty ( OK, not exactly, but nothing relevant there ). > > Also interesting to note that the problem usually occurs during high > traffic periods ( but the server is not overloaded, we are not out of > mysql connections either, and there should enough apache processess ), > and when it occurs, it happens on the php-based forum and 2 other php- > based apps also. There were no such problems before we installed the > Django app. > > Any ideas where should I look? We tried everything we could think of, > but nothing really helped, and this issue is extremely annoying to our > users. > My bet is the response on these pages is 500. This is most likely a server configuration problem than a Django problem. When this happens how many connections do you have the server? I bet it is more than the max-connections that you have on apache. Especially if apache is serving your media and everything. Web servers when they exceed the number of connections to the server just bounce empty 500 responses back. These won't show up in logs and are a pain to diagnose. Just up the number of connections for that virtualhost and that should fis your problem (at the expense of CPU cycles). I hope that fixes it for you. Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
