Attaching large files via Customer web interface.
Hi I, like lots of people it would appear, am having trouble with attaching large files to tickets. In my case, I am only testing OTRS and I have found that if you try to create a ticket and attach a file of more than 5Mb, then the Apache process handing the request goes into a loop and eats all the available memory until the Linux OOM killer terminates it. I have changed the MySQL config variable from 1M to 10M (before doing this, I got the "Got a bigger packet" message) and I can successfully attach a 4.8Mb file. I have now changed the Ticket::Storage config to use the FS module and the same thing still happens, a 4.8Mb attachment works and is stored in the file system, a 5.7Mb attachment causes the Apache process to die. Something the same was briefly discussed in http://www.mail-archive.com/otrs@otrs.org/msg04089.html but that got sidetracked into browsers and firewalls etc. Running OTRS 2.0.4 on Suse Linux 9.3. Dave -- Dave Hill Newnham Research Ltd
I solved my problem configuring mySQL ini file. I'm working on a MSWindows installation, OTRS setup create the my.ini file with a section named [mysqld-nt], the section contain the correct "max_allowed_packet = 50M", but problem persist. I have to change the section name to [mysqld] in order to solve the problem. I hope this help Ciao Simone -----Messaggio originale----- Da: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org]Per conto di Dave Hill Inviato: martedì 28 febbraio 2006 18.11 A: otrs@otrs.org Oggetto: [otrs] Attaching large files via Customer web interface. Hi I, like lots of people it would appear, am having trouble with attaching large files to tickets. In my case, I am only testing OTRS and I have found that if you try to create a ticket and attach a file of more than 5Mb, then the Apache process handing the request goes into a loop and eats all the available memory until the Linux OOM killer terminates it. I have changed the MySQL config variable from 1M to 10M (before doing this, I got the "Got a bigger packet" message) and I can successfully attach a 4.8Mb file. I have now changed the Ticket::Storage config to use the FS module and the same thing still happens, a 4.8Mb attachment works and is stored in the file system, a 5.7Mb attachment causes the Apache process to die. Something the same was briefly discussed in http://www.mail-archive.com/otrs@otrs.org/msg04089.html but that got sidetracked into browsers and firewalls etc. Running OTRS 2.0.4 on Suse Linux 9.3. Dave -- Dave Hill Newnham Research Ltd _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
In article
I solved my problem configuring mySQL ini file.
I'm working on a MSWindows installation, OTRS setup create the my.ini file with a section named [mysqld-nt], the section contain the correct "max allowed packet = 50M", but problem persist.
I have to change the section name to [mysqld] in order to solve the problem.
I hope this help
Ciao
Simone
Nope, it's not that one. I have increased the max_allowed_packet as I said in my initial post and I know it is working because I no longer get the error message "Got a packet bigger than 'max_allowed_packet'" in the log file. Also, I'm now storing in the file system, not in the database. Thanks anyway, Dave -- Dave Hill Newnham Research Ltd
participants (2)
-
Dave Hill -
Simone Girlanda