Greetings all-
So, I recently moved our RT application from CentOS 4.6 (32 bit) to a
new machine running CentOS 5.1 (64 bit). It’s RT 3.6.6. Installed all
the perl stuff and compiled FastCGI just fine. I imported the MySQL
database and everything seems great, users can log in and browse, change
tickets, etc.
However, we’re seeing this odd thing happening now. Whenever someone
tried to create a ticket through the RT web interface, it pauses for 2
minutes, then returns a ‘500 Internal Server Error’. I looked at the
apache error logs and saw this:
[Fri May 16 10:17:46 2008] [error] [client 23.66.56.35] FastCGI: comm
with server “/usr/local/rt3/bin/mason_handler.fcgi” aborted: idle
timeout (120 sec), referer: http://barnyard/Ticket/Create.html?Queue=23
[Fri May 16 10:17:46 2008] [error] [client 23.66.56.35] FastCGI:
incomplete headers (0 bytes) received from server
“/usr/local/rt3/bin/mason_handler.fcgi”, referer:
http://barnyard/Ticket/Create.html?Queue=23
Weird thing is, if you go back to the RT home page, the new ticket is
there!! But it’s a pain to have this error, we don’t want folks to have
to wait 2 minutes and get an apache error, then go back to the RT home
page after that. It’s got to be something with FastCGI but I can’t
figure out what… Here’s the apache configuration include file for
FastCGI:
FastCgiIpcDir /tmp/
FastCgiServer /usr/local/rt3/bin/mason_handler.fcgi -idle-timeout 120
-processes 8
FastCgiConfig -restart
I’ve seen a few other posts with people having similar FastCGI problems
- can anyone point me in the right direction?
Thanks a million!
-erich
Try upgrade of Text::Quoted it can cause seg faults with similar symptoms.
Turn on debug logging everywhere (RT, apache, db server).On Fri, May 16, 2008 at 9:58 PM, Erich Weiler weiler@soe.ucsc.edu wrote:
Greetings all-
So, I recently moved our RT application from CentOS 4.6 (32 bit) to a
new machine running CentOS 5.1 (64 bit). It’s RT 3.6.6. Installed all
the perl stuff and compiled FastCGI just fine. I imported the MySQL
database and everything seems great, users can log in and browse, change
tickets, etc.
However, we’re seeing this odd thing happening now. Whenever someone
tried to create a ticket through the RT web interface, it pauses for 2
minutes, then returns a ‘500 Internal Server Error’. I looked at the
apache error logs and saw this:
[Fri May 16 10:17:46 2008] [error] [client 23.66.56.35] FastCGI: comm
with server “/usr/local/rt3/bin/mason_handler.fcgi” aborted: idle
timeout (120 sec), referer: http://barnyard/Ticket/Create.html?Queue=23
[Fri May 16 10:17:46 2008] [error] [client 23.66.56.35] FastCGI:
incomplete headers (0 bytes) received from server
“/usr/local/rt3/bin/mason_handler.fcgi”, referer:
http://barnyard/Ticket/Create.html?Queue=23
Weird thing is, if you go back to the RT home page, the new ticket is
there!! But it’s a pain to have this error, we don’t want folks to have
to wait 2 minutes and get an apache error, then go back to the RT home
page after that. It’s got to be something with FastCGI but I can’t
figure out what… Here’s the apache configuration include file for
FastCGI:
FastCgiIpcDir /tmp/
FastCgiServer /usr/local/rt3/bin/mason_handler.fcgi -idle-timeout 120
-processes 8
FastCgiConfig -restart
I’ve seen a few other posts with people having similar FastCGI problems
- can anyone point me in the right direction?
Thanks a million!
-erich
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Best regards, Ruslan.
Try upgrade of Text::Quoted it can cause seg faults with similar symptoms.
Turn on debug logging everywhere (RT, apache, db server).
I tried updating Text::Quoted but it seems I already have the latest
version… One thing I did notice in the logs (/var/log/messages) was
this when I try to create a ticket:
May 17 07:04:31 barnyard RT:
rt-3.6.6-25749-1211033071-977.1533-3-0@myco.edu #1533/14192 - Scrip 3
(/usr/local/rt3/lib/RT/Action/SendEmail.pm:266)
May 17 07:04:31 barnyard perl: nss_ldap: reconnecting to LDAP server
(sleeping 4 seconds)…
May 17 07:04:36 barnyard perl: nss_ldap: reconnecting to LDAP server
(sleeping 8 seconds)…
May 17 07:04:44 barnyard perl: nss_ldap: reconnecting to LDAP server
(sleeping 16 seconds)…
May 17 07:05:00 barnyard perl: nss_ldap: reconnecting to LDAP server
(sleeping 32 seconds)…
May 17 07:05:32 barnyard perl: nss_ldap: reconnecting to LDAP server
(sleeping 64 seconds)…
May 17 07:06:36 barnyard perl: nss_ldap: could not search LDAP server -
Server is unavailable
May 17 07:06:36 barnyard RT:
rt-3.6.6-25749-1211033071-977.1533-3-0@myco.edu sent To:
weiler@soe.ucsc.edu (/usr/local/rt3/lib/RT/Action/SendEmail.pm:297)
May 17 07:06:36 barnyard RT:
rt-3.6.6-25749-1211033071-255.1533-4-0@myco.edu #1533/14192 - Scrip 4
(/usr/local/rt3/lib/RT/Action/SendEmail.pm:266)
May 17 07:06:36 barnyard RT:
rt-3.6.6-25749-1211033071-255.1533-4-0@myco.ucsc.edu No recipients
found. Not sending. (/usr/local/rt3/lib/RT/Action/SendEmail.pm:278)
May 17 07:06:36 barnyard RT: Ticket 1533 created in queue
‘Cluser-Admin-Projects’ by weiler
(/usr/local/rt3/lib/RT/Ticket_Overlay.pm:756)
I don’t care that the email failed to send because I actually don’t want
any email sent, but it appears to be doing some kind of LDAP lookup or
something… LDAP is enabled on this machine and it works fine for
everything else? The ticket gets created after some time, but that
delay while waiting for the LDAP server is annoying… Anyone seen this
before? Or know how to fix it?
Thanks again!
-erich