New instance of RT 4.2.2 on CentOS 6.5 with Apache 2.2.15-29 and FCGI
2.3.9-1.
Everything runs fine for the most part, however, intermittently the
following log entries show up and I get an internal server error.
[Fri Jan 31 22:48:36 2014] [warn] [client 192.168.236.64] mod_fcgid: read
data timeout in 40 seconds, referer:
http://rt.example.com/Ticket/Display.html?id=2
[Fri Jan 31 22:48:36 2014] [error] [client 192.168.236.64] Premature end of
script headers: rt-server.fcgi, referer:
http://rt.example.com/Ticket/Display.html?id=2
FastCGI: manager (pid 8954): received signal TERM
FastCGI: manager (pid 8954): sending TERM to PIDs, 8960
[Fri Jan 31 22:48:46 2014] [warn] mod_fcgid: process 8954 graceful kill
fail, sending SIGKILL
FastCGI: server (pid 8960): safe exit after SIGTERM
I’ve looked around and while there are various posts regarding the
premature end of script headers I have yet to find one that mentions read
data timeouts or SIGKILLs.
Could the server simply be running slow? Load averages are sub-1.
Restarting httpd doesn’t show any errors. It’s a virtual machine so I
suppose the underlying hardware might be causing performance issues.
-Mathew
“When you do things right, people won’t be sure you’ve done anything at
all.” - God; Futurama
“We’ll get along much better once you accept that you’re wrong and neither
am I.” - Me
Looking for support on an issue that I haven’t found online through
searches.
New instance of RT 4.2.2 on CentOS 6.5 with Apache 2.2.15-29 and FCGI
2.3.9-1.
Everything runs fine for the most part, however, intermittently the
following log entries show up and I get an internal server error.
[Fri Jan 31 22:48:36 2014] [warn] [client 192.168.236.64] mod_fcgid: read
data timeout in 40 seconds, referer:
http://rt.example.com/Ticket/Display.html?id=2
[Fri Jan 31 22:48:36 2014] [error] [client 192.168.236.64] Premature end of
script headers: rt-server.fcgi, referer:
http://rt.example.com/Ticket/Display.html?id=2
FastCGI: manager (pid 8954): received signal TERM
FastCGI: manager (pid 8954): sending TERM to PIDs, 8960
[Fri Jan 31 22:48:46 2014] [warn] mod_fcgid: process 8954 graceful kill
fail, sending SIGKILL
FastCGI: server (pid 8960): safe exit after SIGTERM
I’ve looked around and while there are various posts regarding the
premature end of script headers I have yet to find one that mentions read
data timeouts or SIGKILLs.
Could the server simply be running slow? Load averages are sub-1.
Restarting httpd doesn’t show any errors. It’s a virtual machine so I
suppose the underlying hardware might be causing performance issues.
-Mathew
“When you do things right, people won’t be sure you’ve done anything at
all.” - God; Futurama
“We’ll get along much better once you accept that you’re wrong and neither
am I.” - Me
Looking for support on an issue that I haven’t found online through searches.
New instance of RT 4.2.2 on CentOS 6.5 with Apache 2.2.15-29 and FCGIÂ
2.3.9-1.Â
You really need to show your RT debug logs, the logs you’re showing are
what apache is getting back from RT (or failing to get back from RT).
Since you’re running 4.2.2, go to Admin → Tools → System Configuration
and read the Logging summary box.
40 seconds to display a ticket is much too slow and points to either a
bad local modification, a misconfigured database or some other
problem, but we can’t comment without details.
-kevin
Everything runs fine for the most part, however, intermittently theÂ
following log entries show up and I get an internal server error.Â
[Fri Jan 31 22:48:36 2014] [warn] [client 192.168.236.64] mod_fcgid: readÂ
data timeout in 40 seconds, referer:Â
[1]http://rt.example.com/Ticket/Display.html?id=2Â
[Fri Jan 31 22:48:36 2014] [error] [client 192.168.236.64] Premature end ofÂ
script headers: rt-server.fcgi, referer:Â
[2]http://rt.example.com/Ticket/Display.html?id=2Â
FastCGI: manager (pid 8954): received signal TERMÂ
FastCGI: manager (pid 8954): sending TERM to PIDs, 8960Â
[Fri Jan 31 22:48:46 2014] [warn] mod_fcgid: process 8954 graceful killÂ
fail, sending SIGKILLÂ
FastCGI: server (pid 8960): safe exit after SIGTERMÂ
-kevin
Unfortunately, the log seems to have been recreated and all of the
timestamps which would line up with the already-provided log entry are
gone. I’ll have to keep an eye on this and provide it at a later date.
-Mathew
“When you do things right, people won’t be sure you’ve done anything at
all.” - God; Futurama
“We’ll get along much better once you accept that you’re wrong and neither
am I.” - MeOn Wed, Feb 5, 2014 at 5:38 AM, Kevin Falcone falcone@bestpractical.comwrote:
On Mon, Feb 03, 2014 at 11:22:16AM -1000, Mathew Snyder wrote:
Looking for support on an issue that I haven’t found online through
searches.
New instance of RT 4.2.2 on CentOS 6.5 with Apache 2.2.15-29 and FCGIÂ
2.3.9-1.Â
You really need to show your RT debug logs, the logs you’re showing are
what apache is getting back from RT (or failing to get back from RT).
Since you’re running 4.2.2, go to Admin → Tools → System Configuration
and read the Logging summary box.
40 seconds to display a ticket is much too slow and points to either a
bad local modification, a misconfigured database or some other
problem, but we can’t comment without details.
-kevin
Everything runs fine for the most part, however, intermittently theÂ
following log entries show up and I get an internal server error.Â
[Fri Jan 31 22:48:36 2014] [warn] [client 192.168.236.64] mod_fcgid:
readÂ
data timeout in 40 seconds, referer:Â
[1]http://rt.example.com/Ticket/Display.html?id=2Â
[Fri Jan 31 22:48:36 2014] [error] [client 192.168.236.64] Premature
end ofÂ
script headers: rt-server.fcgi, referer:Â
[2]http://rt.example.com/Ticket/Display.html?id=2Â
FastCGI: manager (pid 8954): received signal TERMÂ
FastCGI: manager (pid 8954): sending TERM to PIDs, 8960Â
[Fri Jan 31 22:48:46 2014] [warn] mod_fcgid: process 8954 graceful
killÂ
fail, sending SIGKILLÂ
FastCGI: server (pid 8960): safe exit after SIGTERMÂ
-kevin