Error creating ticket - attachment insert failed

A user sent a message via e-mail to our RT instance with a spreadsheet
attached, which has worked before. In this case, the attachment was a
bit large (about 300K), and the following happened:

May 30 07:55:08 monitor RT: RT::Handle=HASH(0x832e168) couldn’t execute
the query ‘INSERT INTO Attachments (Creator, ContentEncoding,
ContentType, Filename, Subject, TransactionId, Headers, Content,
Created, Parent) VALUES (?, ?, ?, ?, ?, ?
, ?, ?, ?, ?)’ at
/usr/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Handle.pm line 392.
(/opt/rt3/lib/RT.pm:226)
May 30 07:55:08 monitor RT:
rt-3.0.2pre6-163-840.6.48643396910337@kapcousa.com
#163/840 - Scrip 2 (/opt/rt3/lib/RT/Action/SendEmail.pm:91)
May 30 07:55:09 monitor RT:
rt-3.0.2pre6-163-840.6.48643396910337@kapcousa.com
No recipients found. Not sending.
(/opt/rt3/lib/RT/Action/SendEmail.pm:171)
May 30 07:55:09 monitor RT:
rt-3.0.2pre6-163-840.14.8025652032685@kapcousa.com
#163/840 - Scrip 3 (/opt/rt3/lib/RT/Action/SendEmail.pm:91)
May 30 07:55:22 monitor RT:
rt-3.0.2pre6-163-840.14.8025652032685@kapcousa.com
sent To: Cc: Bcc: ADDRESS-LIST-REMOVED
(/opt/rt3/lib/RT/Action/SendEmail.pm:217)
May 30 07:55:36 monitor RT: Ticket 163 created in queue ‘General’ by
RickC@KAPCO
USA.com (/opt/rt3/lib/RT/Ticket_Overlay.pm:598)
May 30 07:56:12 monitor RT: WebRT: Could not load ticket 163 ()
(/opt/rt3/share/html/Elements/Error:54)
May 30 07:56:16 monitor RT: WebRT: Could not load ticket 163 ()
(/opt/rt3/share/html/Elements/Error:54)
May 30 07:56:29 monitor RT: Tickets->LimitRequestor is deprecated.
please rewrite call at HTML::Mason::Commands -
/opt/rt3/lib/RT/Interface/Web.pm: 595
(/opt/rt3/lib/RT/Tickets_Overlay.pm:1304)
May 30 07:56:42 monitor RT: WebRT: Could not load ticket 163 ()
(/opt/rt3/share/html/Elements/Error:54)
May 30 07:57:51 monitor RT: WebRT: Could not load ticket 163 ()
(/opt/rt3/share/html/Elements/Error:54)

All attempts to load the ticket failed. The original attachment was sent
via email in the notifications, so I saved it and created the ticket
manually via the web interface. It worked in that case just fine.
Anyone have an idea on what might be going on?

The environment is Red Hat 7.3 with RT 3.02pre6. The database is MySQL
3.23.56 using InnoDB tables. I haven’t tried recreating yet via e-mail,
but with luck it will be reproducible – if so, I’ll see if I can turn
up debugging to capture more information.

MarkMark D. Nagel, CCIE #3177 mnagel@willingminds.com
Principal Consultant, Willing Minds LLC
tel/fax: 949-623-9853, web: http://www.willingminds.com/