erikcw schrieb:
> Hi,
>
> I'm running Django through mod_wsgi and Apache (2.2.8) on Ubuntu 8.04.
>
> I've been running Django on this setup for about 6 months without any
> problems. Yesterday, I moved my database (postgres 8.3) to its own
> server, and my Django site started refusing to load (the browser
> spinner would just keep spinning).
>
> Pages will load when I first start apache, but after about 10 mintues,
> it just stops. Apache is still able to serve static files. Just
> nothing through Django.
The select timeout could be a network problem. Or a problem between
mod_wsgi and apache.
Since it works during the first minutes, it does not look like
a network problem. Except you have a firewall that slows down
new connections if there are too many.
Maybe you can find out with "ls -l /proc/PID/fd" and/or netstat/lsof
which tcp/ip connections the process waits for in the system call select.
You can write a simple script with python and psycopg2 (without django,
just execute a simple SELECT statement) and check if you can still connect
after the pages don't get through django anymore.
Thomas
--
Thomas Guettler, http://www.thomas-guettler.de/
E-Mail: guettli (*) thomas-guettler + de
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
