Re: Debugging comm with (dynamic) server aborted
Bill Moseley <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Oct 31, 2006 at 02:26:58PM +0000, Chris Lightfoot wrote: > ok, that sounds like the thing's failing at startup. move > trac to some other location and replace the fastcgi script > with something like, > > #!/bin/sh > exec strace -o /tmp/my-trac-$$.strace /real/path/to/trac Bah. Now it finally is working. But, when it wasn't working it didn't seem like it was ever running my script as the first few attempts didn't generate a strace output at all -- the script just timed out with that same error. Weird. /index.fcgi worked from the start and /trac took many attempts and now it is working for now obvious reason. The only difference between /index.fcgi and /trac is that /trac requires a .htaccess to determine it's a fastcgi script. But I don't think that has anything to do with it as it was, after all, generating a fastcgi timeout error when it wasn't working. That's Frustrating. -- Bill Moseley [email protected] ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/