Huge attachments result in invisible tickets

Well, I’ve solved the problem with large attachments
being truncated with RH8/RT3.0.4/apache2/mod_perl2.
(What a tangled web that was! [in part because the
server has to support php as well…])

However, now I’ve got a new, slightly different
(I think) problem.

Attachments of, say, 600KB work just fine whether
send by email or from the web page. But if I try
a larger attachment (2MB, e.g.) the ticket vanishes.
(Never arrives, but the ticket number gets incremented.
This is whether the ticket is sent via email or
created via the web interface…

For the tickets sent by email, ‘mailq’ gives a clue:

->mailq
/var/spool/mqueue (2 requests)
-----Q-ID----- --Size-- -----Q-Time-----
------------Sender/Recipient-----------h931tSQ8001863* 2220297 Thu Oct 2 18:55 sbw@tapestry.tucson.az.us
(Deferred: prog mailer (/usr/sbin/smrsh) exited with
EX_TEMPF)
"|/opt/rt3/bin/rt-mailgate
–queue uni
h931ogQ8001750 2220313 Thu Oct 2 18:50 sbw@tapestry.tucson.az.us
(Deferred: prog mailer (/usr/sbin/smrsh) exited with
EX_TEMPF)
"|/opt/rt3/bin/rt-mailgate
–queue uni
Total requests: 2

But I haven’t seen any messages in the various log
files.

Any ideas? Has anyone seen this? Would upgrading to
RT3.0.[56] help?

Steve Wampler sbw@tapestry.tucson.az.us

What if you enter the ticket number manually into the
“goto ticket [ ]” field? Does it show up as ‘dead’
maybe?— Steve Wampler sbw@tapestry.tucson.az.us wrote:

Well, I’ve solved the problem with large attachments
being truncated with RH8/RT3.0.4/apache2/mod_perl2.
(What a tangled web that was! [in part because the
server has to support php as well…])

However, now I’ve got a new, slightly different
(I think) problem.

Attachments of, say, 600KB work just fine whether
send by email or from the web page. But if I try
a larger attachment (2MB, e.g.) the ticket vanishes.
(Never arrives, but the ticket number gets
incremented.
This is whether the ticket is sent via email or
created via the web interface…

For the tickets sent by email, ‘mailq’ gives a clue:

->mailq
/var/spool/mqueue (2 requests)
-----Q-ID----- --Size-- -----Q-Time-----
------------Sender/Recipient-----------
h931tSQ8001863* 2220297 Thu Oct 2 18:55
sbw@tapestry.tucson.az.us
(Deferred: prog mailer
(/usr/sbin/smrsh) exited with
EX_TEMPF)

"|/opt/rt3/bin/rt-mailgate
–queue uni
h931ogQ8001750 2220313 Thu Oct 2 18:50
sbw@tapestry.tucson.az.us
(Deferred: prog mailer
(/usr/sbin/smrsh) exited with
EX_TEMPF)

"|/opt/rt3/bin/rt-mailgate
–queue uni
Total requests: 2

But I haven’t seen any messages in the various log
files.

Any ideas? Has anyone seen this? Would upgrading to
RT3.0.[56] help?


Steve Wampler sbw@tapestry.tucson.az.us


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at
http://fsck.com/rtfm

“I’m the Commander, see … I do not need to explain why I say things. That’s the interesting thing about being the President … [I] don’t feel like I owe anybody an explanation.” – President George W. Bush to the National Security Council

Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

Steve Wampler wrote:

Any ideas? Has anyone seen this? Would upgrading to
RT3.0.[56] help?

It might. The code to recover from unexpected failures at
ticket creation time was made a lot more robust around
3.0.5pre-something, IIRC.
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances