Issue with attachments table

Hi,

We run RT3, 20 queues, 110,000 tickets and about 40 users. Versions are
RT 3.2.3, mysql 4.0.20 and apache 2.0.52 on CentOS4.2 with kernel
2.6.9-22. We recently started experiencing an issue where tickets were
being created in our queues with no message body. We tracked it down to
a problem with the attachment table in the RT database. A mysql
maintenance job temporarily fixed the issue and it happened again. The
size of our database is about 4.2GB which doesn’t seem too large from
what I’ve read on this mailing list. Has anyone seen this issue before
and have any recommendations?

We’ve toyed with the idea of using rtx-shredder or archiving older
tickets and making them available via another instance of RT but we
don’t want to have to do either unless it’s absolutely necessary.

Thanks all!

Keith Hochberg

Hi,

We run RT3, 20 queues, 110,000 tickets and about 40 users. Versions are
RT 3.2.3, mysql 4.0.20 and apache 2.0.52 on CentOS4.2 with kernel
2.6.9-22. We recently started experiencing an issue where tickets were
being created in our queues with no message body. We tracked it down to
a problem with the attachment table in the RT database. A mysql
maintenance job temporarily fixed the issue and it happened again. The
size of our database is about 4.2GB which doesn’t seem too large from

Are you 100% sure your filesystem doesn’t have a 4GB filesize limit (Or
your mysql build :wink:

Thanks for the quick reply. We don’t have a limit on either the fs or
mysql. I believe we’ve been over 4gb for a while now. I wish that was
it though!From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Wednesday, August 30, 2006 5:12 PM
To: Hochberg, Keith
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] issue with attachments table

Hi,

We run RT3, 20 queues, 110,000 tickets and about 40 users. Versions
are RT 3.2.3, mysql 4.0.20 and apache 2.0.52 on CentOS4.2 with kernel
2.6.9-22. We recently started experiencing an issue where tickets
were being created in our queues with no message body. We tracked it
down to a problem with the attachment table in the RT database. A
mysql maintenance job temporarily fixed the issue and it happened
again. The size of our database is about 4.2GB which doesn’t seem too

large from

Are you 100% sure your filesystem doesn’t have a 4GB filesize limit (Or
your mysql build :wink:

what I’ve read on this mailing list. Has anyone seen this issue
before and have any recommendations?

We’ve toyed with the idea of using rtx-shredder or archiving older
tickets and making them available via another instance of RT but we
don’t want to have to do either unless it’s absolutely necessary.

Thanks all!

Keith Hochberg


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com Commercial support:
sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

I was actually mistaken, our dba group found that we did indeed have a
4gb limit on the attachments table in mysql. This issue is now
resolved. I appreciate the assistance Jesse.

KeithFrom: Hochberg, Keith
Sent: Wednesday, August 30, 2006 5:19 PM
To: 'Jesse Vincent’
Cc: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] issue with attachments table

Thanks for the quick reply. We don’t have a limit on either the fs or
mysql. I believe we’ve been over 4gb for a while now. I wish that was
it though!

From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Wednesday, August 30, 2006 5:12 PM
To: Hochberg, Keith
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] issue with attachments table

Hi,

We run RT3, 20 queues, 110,000 tickets and about 40 users. Versions
are RT 3.2.3, mysql 4.0.20 and apache 2.0.52 on CentOS4.2 with kernel
2.6.9-22. We recently started experiencing an issue where tickets
were being created in our queues with no message body. We tracked it
down to a problem with the attachment table in the RT database. A
mysql maintenance job temporarily fixed the issue and it happened
again. The size of our database is about 4.2GB which doesn’t seem too

large from

Are you 100% sure your filesystem doesn’t have a 4GB filesize limit (Or
your mysql build :wink:

what I’ve read on this mailing list. Has anyone seen this issue
before and have any recommendations?

We’ve toyed with the idea of using rtx-shredder or archiving older
tickets and making them available via another instance of RT but we
don’t want to have to do either unless it’s absolutely necessary.

Thanks all!

Keith Hochberg


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com Commercial support:
sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com