Questions[request-tracker](server)

I have a setup where a certain link on my Web Server is redirected to a FCGID module.

When I disable SELinux with 'setenforce 0' the site works. When I enable it won't work, it gives me a "Error 500 - Internal Server error".

I'm used to fixing these SELinux erros, but when I looked in the audit.log there's no new entry related to apache or my fcgid program. In the past, when I had a SELinux error, everytime I refreshed the page it gave me a new entry on this file.

My apache error_log adds these entries after refreshing the site:

[Thu Jul 07 14:34:04.240551 2016] [fcgid:warn] [pid 18054] (104)Connection reset by peer: [client XXX.XXX.XXX.XXX:34622] mod_fcgid: error reading data from FastCGI server
[Thu Jul 07 14:34:04.240629 2016] [core:error] [pid 18054] [client XXX.XXX.XXX.XXX:34622] End of script output before headers: rt-server.fcgi

This is my server information:

OS: CentOS Linux release 7.2.1511 (Core)
Apache: 2.4.6
FCGID program: Request Tracker 4.2 (rt-server.fcgid)

How can I be certain which policies I have to enable on SELinux for my module to work when I have no log on the audit.log file? Please don't tell me I have to read the code to know this. It's huge and written in Perl. Everytime someone opens a Perl script a puppy dies somewhere.

Is it possible to install the latest RT on Windows Server?

I've found some installers online for previous versions, but can't find any tutorials for the current version.

Currently trying to do something with Cygwin, but I've got a feeling I'm approaching this the wrong way.

I am using Ubuntu 10.04 and by following this tutorial I have made RT run well in everything except for sending outbound emails. The difference is, I need to make RT use an external, existing mail server. The mail server is accessible via SMTP with authentication so I am looking for a place to insert the username and password, but nothing like that seems to exist.

The closest thing that I found by googling is that I need to setup ssmtp or msmtp and use it to forward my outbound emails to the mail server (sorry I lost the link). Is that true? Are there any (perhaps better) other ways?

I'm trying to get incoming e-mail to automatically go directly into whichever queue/ticket they are related to or create a new one if none exist and the right queue e-mail setup in the web interface is used.

I will have too many queues to have two line items within mailgate per queue.

A similar issue was discussed here (Procmail: Pipe to Program, Otherwise Return Error to Sender), but I thought it best to open a new case instead of tagging on what appeared to be an answer to that person's query.

I'm able to send and receive e-mail (via PostFix) to the default rt user and this user successfully accepts all e-mail for the relative domain.

I have no idea where the e-mail goes - it's successfully delivered, but it does not update existing tickets (with a Subject line match) and it does not create any new.

Here's and example of my ./procmail.log:

procmail: [23048] Mon Aug 23 14:26:01 2010
procmail: Assigning "MAILDOMAIN=rt.mydomain.com
"
procmail: Assigning "RT_MAILGATE=/opt/rt3/bin/rt-mailgate
"
procmail: Assigning "RT_URL=http://rt.mydomain.com/
"
procmail: Assigning "LOGABSTRACT=all
"
procmail: Skipped "
"
procmail: Skipped "
"
procmail: Assigning "LASTFOLDER={
"
procmail: Opening "{
"
procmail: Acquiring kernel-lock
procmail: Notified comsat: "rt@18337:./{
"
From [email protected]  Mon Aug 23 14:26:01 2010
 Subject: RE: [RT.mydomain.com #1] Test Ticket 
  Folder: {            1616

Does the notified comsat portion mean that it notified RT?

The contents of my ./procmailrc:

#Preliminaries
 SHELL=/bin/sh               #Use the Bourne shell (check your path!)
 #MAILDIR=${HOME}        #First check what your mail directory is!
 MAILDIR="/var/mail/rt/"
 LOGFILE="home/rt//procmail.log"
 LOG="--- Logging ${LOGFILE} for ${LOGNAME}, "
 VERBOSE=yes
 MAILDOMAIN="rt.mydomain.com"
 RT_MAILGATE="/opt/rt3/bin/rt-mailgate"
 #RT_MAILGATE="/usr/local/bin/rt-mailgate"
 RT_URL="http://rt.mydomain.com/"

 LOGABSTRACT=all


 :0
 {
 # the following line extracts the recipient from Received-headers.
 # Simply using the To: does not work, as tickets are often created
 # by sending a CC/BCC to RT
 TO=`formail -c -xReceived: |grep $MAILDOMAIN |sed -e 's/.*for *<*\(.*\)>* *;.*$/\1/'`
 QUEUE=`echo $TO| $HOME/get_queue.pl`
 ACTION=`echo $TO| $HOME/get_action.pl`
 :0 h b w 
 |/usr/bin/perl $RT_MAILGATE --queue $QUEUE --action $ACTION --url $RT_URL
 }

I know that my get_queue.pl and get_action.pl scripts work, as those have been previously tested.

Any help and/or guidance you can give would be greatly appreciated.

• Nicôle

Recently I heard someone suggest that RT request tracker may have scalability issues due to its non-normalized database (someone at a Perl meeting I went to referred to it in a positive light as hyper-normalized, but I think he may have misunderstood what normalization is all about). On the other hand I know that large scale enterprises such as Perl's CPAN use RT. Do es this level of scale require special measures to be taken to handle what happens when the db grows too large? What have your experiences been?