I am experiencing some issue when RT 3.8.8 is going down intermittently when a user is doing a search. I have been trying to investigate this issue and noticed several strange errors in the /var/log/rt3.log
First, I noticed that the time in this log in 5 hours off. My OS time is set correctly and is connected to our NTP servers. I also noticed in /opt/rt3/etc/RT_Siteconfig.pm that it is set to pull the time from /etc/timezone.
my $zone = “US/Eastern”;
if -f “/etc/timezone”;
Second, these type of errors show up repeatedly around the time the end-user is experiencing intermittent connection issues.
This error appears several times in the log.
[Mon Mar 2 11:08:53 2015] [crit]: Apache2::RequestIO::print: (103) Software caused connection abort at /usr/lib/perl5/site_perl/5.10.0/HTML/Mason/ApacheHandler.pm line 1019 (/opt/rt3/libexec/webmu
[Mon Mar 2 11:08:53 2015] [crit]: Apache2::RequestIO::rflush: (103) Software caused connection abort at /usr/lib/perl5/site_perl/5.10.0/HTML/Mason/ApacheHandler.pm line 1020 (/opt/rt3/libexec/webm
Later on this error appears several times.
[Mon Mar 2 12:34:40 2015] [error]: Impossible to assign the ticket to 3680: That user may not own tickets in that queue ((eval 8596):14)
In addition, this error appeared a few days before during one occurrence, but not with recent incident.
[Fri Feb 27 20:54:43 2015] [error]: Couldn’t set date: That is already the current value (/usr/local/share/request-tracker3.8/plugins/RT-IR/lib/RT/Action/RTIR_SetStartedToNow.pm:26)
Any help with understanding these errors would be helpful!