I ran into a very similar problem with any attachment over 50MB or so… the process that takes the email and converts it to a ticket would chew up memory until the system started swapping, which essentially locked the system(30s-5mins for a command to execute).
I turned the config setting on to reject large file sizes… but it would be nice if an extention/mod was built to take emails with attachments, and store the attachment as a link to a config defined FTP site… as our graphics team here wanted to use RT, but since they got large email attachments on a regular basis, we had to give them a different solution
If you do figure out a solution to this issue, please share with the list!!
Northern Ontario School of Medicine
955 Oliver Road
Thunder Bay, ON P7B 5E1
Phone: (807) 766-7331
Technology assistance: email email@example.com
Technology Emergency Contact (TEC) Mon-Fri, 8am to 5pm excluding stat holidays:
Off campus toll free 1 (800) 461-8777, option 8, or locally either
(705) 662-7120 or (807) 766-7500
“Gary Greene” firstname.lastname@example.org 4/19/2010 6:47 PM >>>
I am hoping to use RT to help manage a printshop, but am having severe
performance issues when I upload a 76M file. My hardware has 2 CPUs and
4GB of ram. The upload was ok, but when I try to look at the ticket,
the system just locks up with almost 100% system cpu use and uses up all
ram and starts in on swap. Has anyone else used RT with large files
(100 - 200MB). Does RT’s design allow for this or should I just set up
links to an FTP site that can be accessed from the RT ticket?
Thanks in advance.
From what I’ve found, since the attachments get stored in the DB, it’s best
not to upload such huge files as attachments and rather host them elsewhere
and link to them. Besides, email over all was never meant for such monster
Gary L. Greene, Jr.
Minerva Networks, Inc.
Cell: (650) 704-6633
Phone: (408) 240-1239