Let's see a copy of your lighttpd.conf, it might clear some things up. -Dan
On Tue, Oct 27, 2009 at 8:26 AM, Hraban Luyat <[email protected]> wrote: > > Hello everyone, > > For http://nophilosophy.com/ I am using a set-up consisting of a web.py > app, connected to lighttpd via fcgi, behind a Squid in accelerator mode. > The application uses web.modified() and cache-control: headers a lot to > make optimal use of caching on the client and accelerator side. > > When I run web.py in debug mode, ./code.py, it seems to act normally. > Recursively fetching the entire website with wget works fine. When I > start it through lighttpd, however, it does not even survive one such a > recursive fetch. The fcgi process dies and the website becomes > non-responsive. > > I find myself having to restart lighttpd every day because the thing > breaks down. No error messages in the lighttpd logs, no idea what is > going wrong. Can anybody help me to look for whatever is causing this? > The only thing that shows up in Lighttpd error logs after a while is > this: > > 2009-10-27 14:39:09: (mod_fastcgi.c.2494) unexpected end-of-file (perhaps > the fastcgi process died): pid: 11273 socket: > unix:/tmp/fastcgi-py-nophilosophy.com.socket-0 > > As is, both sides (lighttpd + fcgi + PHP, for example, and web.py > stand-alone) work fine by themselves, but not when combined. I am at > wit's end. > > Greetings, > > Hraban Luyat > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
