Nope, nothing in the Satchmo.log, or in the site's lighttpd logs. When the site crashes (when running in threaded mode), the process just disappears, as if the whole python/manage.py fastcgi process segfaulted. I am running more than a dozen Satchmo stores on the same machine, and they don't have this trouble. Any ideas in what route to pursue? For the time being, I wrote a program that checks the lighttpd error log file and automatically resurrects the site if it sees those error messages in the file.... and nagios paging my phone when the dead site resurrection program quits working ;)
Sincerely, Dan On Jan 8, 3:03 pm, "Chris Moffitt" <[email protected]> wrote: > Do you seeing anything in the Satchmo logs? > > Is there any chance you're having a memory issue on the system(running out > in some way). > > -Chris > > On Thu, Jan 8, 2009 at 2:10 PM, [email protected] < > > [email protected]> wrote: > > > This may be more of a Django-specific question. Have others > > experienced this same issue? I have a Django & Satchmo store that > > crashes often (one to three times a day) at random. I'm using > > Lighttpd + fastcgi for the setup. I check my lighttpd error.log and I > > get the following items in the log: > > > 2009-01-08 11:30:28: (mod_fastcgi.c.2961) got proc: pid: 0 socket: > > unix:/tmp/website.socket load: 6 > > 2009-01-08 11:30:29: (mod_fastcgi.c.2471) unexpected end-of-file > > (perhaps the fastcgi process died): pid: 0 socket: unix:/tmp/ > > website.socket > > 2009-01-08 11:30:29: (mod_fastcgi.c.3281) response not received, > > request sent: 660 on socket: unix:/tmp/website.socket for / > > website.dispatch.fcgi , closing connection > > 2009-01-08 11:30:29: (mod_fastcgi.c.1490) released proc: pid: 0 > > socket: unix:/tmp/website.socket load: 5 > > > And sometimes this: > > > 2009-01-04 19:57:33: (mod_fastcgi.c.3524) all handlers for / > > website.dispatch.fcgi/shop/product/gentle-flowers/ on / > > website.dispatch.fcgi are down. > > > I have checked the access log to see if someone was hitting some > > magical page on the site making the site crash, but that doesn't seem > > to be the case; it's a different page every time. I'm running the > > site in threaded mode (not prefork). I switched it to prefork, but > > got a similar issue; instead of crashing out right, the website > > "freezes" at random. The browser connects to the site and waits for > > the response until it times out. I run top on the server, but no > > particular process is running out of hand. > > > Any ideas? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
