It seems the configuration you've done is being ignored? This shouldn't
Are you sure Apache has access to the directory of rt installation
completely since you seem to run it from /home?
On 09-Sep-2016 1:15 AM, "Pavneet Arora" wrote:
Log to syslog option will generate messages in system log which is
/var/log/messages or it's equivalent based on distribution.
Or you can add
Set(@LogToSyslogConf, (facility => 'local2'));
To get the messages in local2 facility so that it can be filtered out via
syslog daemon to a separate
Sorry, I misunderstood. Here is the output from the shell command. I
am just reconfiguring RT_SiteConfig and will get that to you shortly.
# /opt/rt4/sbin/rt-server.fcgi -processes 5 -idle-timeout 300
Possible attempt to separate words with commas at
/opt/rt4/etc/RT_SiteConfig.pm line 24.
I was asking about the Perl errors. What do you see on the console or in RT's
logs (enable debug logging in RT_SiteConfig) when you run rt-server.fcgi
On Thu, 2016-09-08 at 13:57 -0400, Pavneet Arora wrote:
> Observed behaviour is that the browser request times out.
Observed behaviour is that the browser request times out.
/var/log/apache2/error.log shows as quoted originally (same error as
immediately after upgrade to 16.04.1):
'FastCGI: server "/opt/rt4/sbin/rt-server.fcgi" has failed to remain
running for 30 seconds given 3 attempts, its restart
On Thu, 2016-09-08 at 11:24 -0400, Pavneet Arora wrote:
> Okay, I have tried scouring the archives, but haven't found a solution
> to my problem, although rt-server.fcgi errors is mentioned with other
> Here is a summary of the configuration:
> 1. Originally, a working rt-4.2.10
Request Tracker 4.0, originally released in April of 2011, will reach end of
life on February 15, 2017. After that date, Best Practical will no longer
support the 4.0 series or publish new releases with bug fixes, security
updates, or new features. We recommend all RT 4.0 users upgrade
Okay, I have tried scouring the archives, but haven't found a solution
to my problem, although rt-server.fcgi errors is mentioned with other
Here is a summary of the configuration:
1. Originally, a working rt-4.2.10 installation under Ubuntu 14.04.
Perl was installed locally and
our RT system has been suffering from this annoying problem for months
where, only sometimes, when you go to the "People" tab of a ticket it
displays the error "An internal RT error has occurred". In the system
logs I see:
Sep 8 09:30:16 rt RT:  Can't call method "head" on an