[rt-users] RT4.0.1 post-upgrade rt-server.fcgi won't start

[Adam Thompson]

Well, as I said, nothing really changed.  CentOS 5.6 with lighttpd from 
RPMForge.  The following config block was appended to 
/etc/lighttpd/conf.d/fastcgi.conf:

	alias.url = (
	        "/NoAuth/images/" => "/opt/rt4/share/html/NoAuth/images/",
	)
	$HTTP["url"] !~ "^/NoAuth/images/" {
	        fastcgi.server = (
	                "/" => (
	                        "rt" => (
	                                "port"        => "9000",
	                                "bin-path"    => 
"/opt/rt4/sbin/rt-server.fcgi",
	                                "check-local" => "disable",
	                                "fix-root-scriptname" => "enable",
	                        )
	                )
	        )
	}


What RT error log?  I included everything lighttpd logged, and RT didn't 
log anything except what I showed, not to stderr, nor syslog, nor any 
file.  (Hence my question about what would be useful to turn on for 
debugging here...)

I turned LogToScreen and LogToSyslog both up to "debug", but still nothing 
shows up anywhere... it's as though something is failing around exec(2) 
rather than inside the RT fcgi daemon, but everything *looks* ok, and as 
I've reiterated, it worked fine under 4.0.0.

Thanks,
-Adam Thompson
 athompso at athompso.net
 (204) 291-7950 - direct
 (204) 489-6515 - fax

> -----Original Message-----
> From: Alex Vandiver [mailto:alexmv at bestpractical.com]
> Sent: Thursday, June 23, 2011 15:51
> To: athompso at athompso.net
> Cc: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] RT4.0.1 post-upgrade rt-server.fcgi won't start
>
> On Thu, 2011-06-23 at 15:17 -0500, Adam Thompson wrote:
> > Followed the instructions in README: did configure, make upgrade,
> > updated schema, now rt-server.fcgi+lighttpd is broken.
> >
> > Lighttpd error log only says:
>
> What does the RT error log say?  What does your lighttpd configuration
> look like?
>
> > I can verify that manually executing rt-server.fcgi fails, as in:
>
> This also happens with RT 4.0.0; for questionable reasons, 
> rt-server.fcgi
> ignores the --port option entirely, and thus produces a spurious warning
> about the port being already in use.  This should be fixed in 4.0.2, and 
> rt-
> server.fcgi should become usable as an external fcgi process.  Until 
> then,
> it will only function if its STDOUT is attached to a pipe.
>  - Alex
>