[rt-users] Errors with new instance on 4.2.0

Fri Oct 18 17:00:18 EDT 2013

Kevin I found the issue.  The web user could not write to the RT logfile.  I now have a happy new instance of RT 4.0.18 & RTIR 3.  It took me a bit to figure out how to run rt-server.fcgi as the web user since a shell login was not allowed for that user (sudo su wouldn't execute command).  I just edited vipw quick and gave it a shell, tested the command and found the issue and set the shell back to false after.

Thank you,
Tim

-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Thursday, October 17, 2013 9:39 AM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Errors with new instance on 4.2.0

On Wed, Oct 16, 2013 at 07:27:29PM +0000, Flynn, Timothy wrote:
> I reinstalled perlbrew to /opt/perl5 in case it was a permissions
> issue with perl. Rebuilt rt 4.0.18 and all dependencies under new
> perl. I've verified that RT is configured to use perl at that
> location:

Since your intent is to run 4.2.0 - why are you testing with 4.0.18?
I suggest you install the version you intend to deploy with (4.2.0) and then run /opt/rt4/sbin/rt-server.fcgi as the web user and see what permission errors or other messages you get.

-kevin

>
> #!/opt/perl5/perls/perl-5.18.1/bin/perl -w (first line of
> rt-server.fcgi)
>
> I still get a 500 http error when accessing the page with apache.   I did try the standalone rt server and it works fine.  I had to install Module::Refresh to get it to work.
>
> I checked and when I start apache (/var/lib/apache2/fcgid/shm) is created and removed when stopped so I believe apache does have write access to this file and location:
>
>
> I do have other RT servers with the same configuration aside from perlbrew and they work fine.   Reason I was using perlbrew is that I have plans for RT 4.2 and it's perl version requirement exceeds what my SLES 11 server has available.
>
> This is the only error I really have to go on in apache.  Nothing is being presented in the RT log.
>
> Apache error file:
> [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi server error.
>  [error] [client XXXXX] Premature end of script headers:
> rt-server.fcgi
>
> Here is my apache vhost config (servername blanked out for security)
>
>
> <VirtualHost "servername here">
>         ### Optional apache logs for RT
>         # Ensure that your log rotation scripts know about these files
>         ErrorLog /var/log/apache2/"servername"-error_log
>         CustomLog /var/log/apache2/"servername"-access_log combined
>         LogLevel debug
>
>         AddDefaultCharset UTF-8
>
>         Alias /NoAuth/images/ /opt/rt4/share/html/NoAuth/images/
>         ScriptAlias / /opt/rt4/sbin/rt-server.fcgi/
>
>         DocumentRoot "/opt/rt4/share/html"
>         <Location />
>             Order allow,deny
>             Allow from all
>
>             Options +ExecCGI
>             AddHandler fcgid-script fcgi
>         </Location>
> </VirtualHost>
>
>
> -Tim
>
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Flynn,
> Timothy
> Sent: Tuesday, October 15, 2013 3:27 PM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Errors with new instance on 4.2.0
>
> Ok thank you for the recommendations Kevin.  Apologies for replying to the wrong post.
>
> Tim
>
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin
> Falcone
> Sent: Tuesday, October 15, 2013 1:28 PM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Errors with new instance on 4.2.0
>
> On Tue, Oct 15, 2013 at 05:57:37PM +0000, Flynn, Timothy wrote:
> > I deleted rt 4.2.0 and dropped the database, downloaded and
> > installed rt 4.0.18. Appear to have the same errors without doing
> > anything with RTIR. I did see some old threads on mod fcgi with
> > similar errors and returning exit 255. This is my first time
> > installing RT using perlbrew. Could that be the issue?
>
> Please don't hijack someone else's thread on the mailing list.
>
> I highly doubt that perlbrew is causing mod_fcgid problems.
>
> The most common problems are permission related (can apache write into /var/lib/apache2/fcgid ?) and SELinux related (does selinux allow apache to write into /var/lib/apache2/fcgid ?).
>
> You can also run the standalone RT server /opt/rt4/sbin/rt-server manually as root to ensure that you've installed and configured RT correctly.  After doing so, be sure to clean your mason cache before trying to configure mod_fcgid.
>
> -kevin
>
> On Tue, Oct 15, 2013 at 05:07:20PM +0000, Flynn, Timothy wrote:
> >    I am trying an install on a new server with Perlbrew 0.66, perl-5.18.1, fast cgi , RT 4.2.0,
> >    and RTIR 3.0.  Pretty much vanilla install right now with freshly initialized db.
> >
> >    When I access webpage I get the following errors in the logfile.
> >
> >    [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi server error.
> >
> >    [debug] arch/unix/fcgid_proc_unix.c(525): (111)Connection refused: mod_fcgid: can't connect
> >    unix domain socket: /var/lib/apache2/fcgid//28251.1
> >
> >    [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi server error.
> >
> >    [error] [client (IP ADDRESS)] Premature end of script headers:
> > rt-server.fcgi
> >
> >    [info] mod_fcgid: server /opt/rt4/sbin/rt-server.fcgi(28139)
> > started
> >
> >    [notice] mod_fcgid: process /opt/rt4/sbin/rt-server.fcgi(28139) exit(communication error),
> >    terminated by calling exit(), return code: 255
>
>
>
> ________________________________
> Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
> ________________________________
>
>
> ________________________________
> Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
> ________________________________

________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
________________________________