LSWS 3.0RC2 and trac-fcgi
 

I'm trying to get LSWS 3.0RC2 running with trac.

I have a functioning trac installation and an functioning installation of LSWS 3.0RC2. Some further informations about the setup of my server:
My trac project resides in /srv/trac/dystopia
All files are marked readable by LSWS.
The trac.fcgi ist marked readable and executable and resides in /srv/trac

I tried to run the trac.fcgi manually through python and piped the output through lynx and then i see a functioning website with my trac project. So the trac.fcgi can't be the problem.

I set up everything according to the wiki-tutorial. A restart of LSWS shows, that the Listener and the Virtual Host are correctly set up. When trying to access trac via Browser i get a 503.

Accordings to the LSWS stderr.log the following has happened:
Everytime I try to access I get a bunch of these written to the stderr.log.

So I pushed LSWS into debug logging mode in the hope of finding some instructing insights.

I tried to read it all through but I can't figure out, where the problem is buried.

The debug server log gives the following messages, when I try to access the trac project via browser.
And after this everything happens again with the next connection try.


I'm at the end of my latin, please help me.

Please try the 3.0 preview release by change 3.0RC2 to 3.0 in the download package. that might be caused by a bug has been fixed in 3.0 package.

Ok I updated LSWS to 3.0 from RC2.

After successful update and a restart I get a bunch of the following debug errors when I try to access trac.fcgi
I have no clue what this error message is trying to tell me. 'mpstat'? o_O Have I missed something crucial?

That's because mpstat shell command was not installed on your server, which is not a big deal, we use mpstat output in our realtime status report, you can ignore that. It does not related to the trac.fcgi 503 errors.

After compiling sysstats and gaining mpstat with this, I don't get this message anymore. That's quite fine with me, but now my trac-FastCGI doesn't throw any debug message in the LSWS logs. Curios enough as it might be it doesn't load in browser either.

The only message which stays constant ist die "bad file descriptor" message in the stderr.log

Is it possible to install an older LSWS over an newer one and then degrade LSWS to an older version?

Or do you have another idea what might help me?

Yes, you downgrade to 2.2.6 release by running the installer then select "upgrade".

There is another tutorial you can follow at the end of
http://www.deveiate.org/projects/Blu...ki/TracFastCgi

There might be configuration errors, please double check your configurations.

You can also check out the configuration of our demo server, there is a Trac demo.

Yes thanks a lot, this I will do and then report back if I had success.

Ok I triple checked everything. I have exactly the same configurations as your demo server. The tutorial you linked for me is the same as in your wiki. This is the tutorial I followed initally when setting up the trac project virtual host for the first time.

After trying it so many times I believe that it isn't a problem of lsws. Maybe it is a problem of trac 0.11dev itself and its .fcgi script. I don't know right now and what's troubling me in solving is the message from the stderr.log
You don't happen to have an idea what this is trying to tell me? For my understanding this normally tries to tell me, that a file is not correctly accessible via the file system. But this can't be the point here and why is it a failure during a closure?

Nonetheless I will try to get to the bottom of this problem and first of all I will test if my lsws installation is capable of serving another python script.

OK I know this is a really old ticket but I'm having the same problems. I've tested my trac install with tracd and I've followed this tutorial

http://www.litespeedtech.com/support...ac_fcgi_python

but I always get a 503 error every time I try to load the trac url. any idea how it was solved/what the issue was?