Issue with rt-mailgate

RT Users
1

Hi,

I’ve got an RT 3.4.4 setup running (mysql 4.1.11-Debian_4sarge1-log/FastCGI
2.4.2/Apache 2.0.54/Perl 5.8.4), and it was working well until a day or two
ago.

For some reason, the messages stopped being inserted into the database
reliably.

When trying rt-mailgate outside of the sendmail pipe, with --debug, I get
this:

/opt/rt3/bin/rt-mailgate --queue support --action correspond --url

http://example.com/ --debug < /tmp/mail.msg
Connecting to http://example.com//REST/1.0/NoAuth/mail-gateway at
/opt/rt3/bin/rt-mailgate line 99, <> line 1.
An Error Occurred

500 read timeout
This is /opt/rt3/bin/rt-mailgate exiting because of an undefined server
error at /opt/rt3/bin/rt-mailgate line 147, <> line 1.

This happens with all kinds of messages, both plain-text, and mime-encoded.
It doesn’t happen consistantly, as in sometimes it doesn’t work, other times
it does.

Sometimes this message gets inserted into the database, but it returns this,
so is considered at failed delivery, so it is queued, and tried again later.

Thinking it might be due to concurrent attempts at running mailgate, I upped
apache’s max-clients, and also the ‘FastCgiServer’ -connections option, but
it still occurs.

The database is in a good state (although I wouldn’t mind pruning the
Attachments table a bit (over a GB now)), and is responsive.

I’m not really sure where I should be looking next.

Any advice would be welcomed.

Stuart

2

try to increase fast_cgi server timeout time
also good thing to do is configure your MTA to only pipe message by
message to mailgate script, because LWP (module that is used by
mailgate script to deliver message to RT server) has problems and uses
a lot of memory.On 3/10/06, Stuart J. Browne sjbrowne@bluebottle.com wrote:

Hi,

I’ve got an RT 3.4.4 setup running (mysql 4.1.11-Debian_4sarge1-log/FastCGI
2.4.2/Apache 2.0.54/Perl 5.8.4), and it was working well until a day or two
ago.

For some reason, the messages stopped being inserted into the database
reliably.

When trying rt-mailgate outside of the sendmail pipe, with --debug, I get
this:

/opt/rt3/bin/rt-mailgate --queue support --action correspond --url

http://example.com/ --debug < /tmp/mail.msg
Connecting to http://example.com//REST/1.0/NoAuth/mail-gateway at
/opt/rt3/bin/rt-mailgate line 99, <> line 1.
An Error Occurred

500 read timeout
This is /opt/rt3/bin/rt-mailgate exiting because of an undefined server
error at /opt/rt3/bin/rt-mailgate line 147, <> line 1.

This happens with all kinds of messages, both plain-text, and mime-encoded.
It doesn’t happen consistantly, as in sometimes it doesn’t work, other times
it does.

Sometimes this message gets inserted into the database, but it returns this,
so is considered at failed delivery, so it is queued, and tried again later.

Thinking it might be due to concurrent attempts at running mailgate, I upped
apache’s max-clients, and also the ‘FastCgiServer’ -connections option, but
it still occurs.

The database is in a good state (although I wouldn’t mind pruning the
Attachments table a bit (over a GB now)), and is responsive.

I’m not really sure where I should be looking next.

Any advice would be welcomed.

Stuart

Best regards, Ruslan.

3

Hi,

I’ve got an RT 3.4.4 setup running (mysql
4.1.11-Debian_4sarge1-log/FastCGI
2.4.2/Apache 2.0.54/Perl 5.8.4), and it was working well until a day or
two
ago.

/opt/rt3/bin/rt-mailgate --queue support --action correspond --url

http://example.com/ --debug < /tmp/mail.msg
Connecting to http://example.com//REST/1.0/NoAuth/mail-gateway at
/opt/rt3/bin/rt-mailgate line 99, <> line 1.
An Error Occurred

500 read timeout
This is /opt/rt3/bin/rt-mailgate exiting because of an undefined server
error at /opt/rt3/bin/rt-mailgate line 147, <> line 1.

try to increase fast_cgi server timeout time
also good thing to do is configure your MTA to only pipe message by
message to mailgate script, because LWP (module that is used by
mailgate script to deliver message to RT server) has problems and uses
a lot of memory.

From my Apache config:
FastCgiServer /opt/rt3/bin/mason_handler.fcgi -idle-timeout
300 -processes 15

The idle-timeout is how it’s always been set up. Is there another timeout I
should be setting?

As for deliverying one message at a time, do you know how to configure
sendmail to do this?

Stuart