Yeah, that seems to work okay:
$ TRAC_ENV_PARENT_DIR=/data/trac python /usr/lib/python2.3/site- packages/Trac-0.11.2.1-py2.3.egg/trac/web/fcgi_frontend.py WSGIServer: missing FastCGI param REQUEST_METHOD required by WSGI! WSGIServer: missing FastCGI param SERVER_NAME required by WSGI! WSGIServer: missing FastCGI param SERVER_PORT required by WSGI! WSGIServer: missing FastCGI param SERVER_PROTOCOL required by WSGI! Status: 200 Ok Cache-control: must-revalidate Content-Type: text/html;charset=utf-8 Content-Length: 584 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http:// www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml";> <head> <title>Available Projects</title> </head> <body> <h1>Available Projects</h1> <ul> <li> <a href="/ibboard" title="My example project">IBBoard utils</ a> </li><li> <a href="/warfoundry" title="Bug tracking and source control integration for WarFoundry - the cross-platform, open-source, multi- system army builder application">WarFoundry</a> </li> </ul> </body> </html> $ As I said, it works fine after a Lighttpd restart, just not the first time that Lighttpd starts up after a server reboot. Thanks. On Dec 26, 7:25 pm, Noah Kantrowitz <[email protected]> wrote: > Check if you can run the .fcgi script manually from the console. > > --Noah > > On Dec 26, 2008, at 6:57 AM, IBBoard wrote: > > > > > I don't know if this is a Trac issue or a Lighttpd issue, but as > > everything else works okay and Trac works fine later I suspect it's > > Trac specific. > > > Basically, if I restart Lighttpd then the Trac FastCGI process gets > > restarted and Trac runs okay. If I kill the Trac FastCGI process then > > the next request is a bit slow, but the process is started again. If I > > restart the entire server then Lighttpd and PHP restart without a > > problem but Trac just won't work - the page just sits and waits but > > never loads. > > > Unfortunately I can't remember whether the Trac process was still > > there after the server restart, but restarting Lighttpd spawned a new > > Trac process and everything ran smoothly from there. All I get in the > > logs is: > > > 2008-12-23 15:26:46: (log.c.97) server started > > 2008-12-23 15:26:48: (mod_fastcgi.c.1768) connect failed: Connection > > refused on unix:/tmp/trac-fastcgi.sock-0 > > 2008-12-23 15:26:48: (mod_fastcgi.c.2956) backend died; we'll disable > > it for 5 seconds and send the request to another backend instead: > > reconnects: 0 load: 1 > > 2008-12-23 15:26:48: (mod_fastcgi.c.1051) the fastcgi-backend /usr/ > > lib/ > > python2.3/site-packages/Trac-0.11.2.1-py2.3.egg/trac/web/ > > fcgi_frontend.py failed to start: > > 2008-12-23 15:26:48: (mod_fastcgi.c.1055) child exited with status 1 / > > usr/lib/python2.3/site-packages/Trac-0.11.2.1-py2.3.egg/trac/web/ > > fcgi_frontend.py > > 2008-12-23 15:26:48: (mod_fastcgi.c.1058) If you're trying to run PHP > > as a FastCGI backend, make sure you're using the FastCGI-enabled > > version. > > You can find out if it is the right one by executing 'php -v' and it > > should display '(cgi-fcgi)' in the output, NOT '(cgi)' NOR '(cli)'. > > For more information, check > >http://trac.lighttpd.net/trac/wiki/Docs%3AModFastCGI#preparing-php-as... > > this is PHP on Gentoo, add 'fastcgi' to the USE flags. > > 2008-12-23 15:26:48: (mod_fastcgi.c.2759) ERROR: spawning fcgi > > failed. > > > Anyone experienced this before and know why it works all of the time > > except after a server restart? > > > Thanks, > > > IBBoard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
