0011161: Uploading of larger files (> 1 MB) doesn't work

ID	Project	Category	View Status	Date Submitted	Last Update
0011161	mantisbt	attachments	public	2009-11-11 14:30	2011-08-05 02:30

Reporter	markus.humm	Assigned To	atrol
Priority	normal	Severity	block	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	1.1.8

Summary	0011161: Uploading of larger files (> 1 MB) doesn't work
Description	When I try to upload a file larger than approx. 1 MB it doesn't work. I get a "Error received frorn database was 0002006: MySQL Server has gone away for the quert': INSEKT lNTO rnantis_project_file_table (project_id, title, description, diskfile, filename, folder, filesize, file_type, date_added, content) VALUES" and the contents of the file to be uploaded is shown in binary (in my recent test case it was a large bmp file). I already looked at the php.ini of the server for a few minutes but didn't notice anything bad up to now.
Additional Information	It works if the file is smaller than 1 MB and the limit on our mantis is set up 5000K.
Tags	Upload files
Attached Files	mantiserror.jpg (955,362 bytes)

yw84ever 2009-11-11 17:22 reporter ~0023660	greetings. are you uploading the files from afar? possibly taking too long? check your php.ini config file for the settings regarding uploads and the time/memory allotted for a script max_execution_time = max_input_time = max_input_nesting_level = memory_limit = upload_max_filesize = not sure if this one is related to 0007853

thraxisp 2009-11-11 20:32 reporter ~0023665	You may also try looking at http://www.mantisbt.org/manual/manual.troubleshooting.file.downloads.php . There are also some mysql settings that need to be updated for large files.

markus.humm 2009-11-12 05:32 reporter ~0023677	We'll test these suggestions.

markus.humm 2009-11-17 05:16 reporter ~0023736	After some changes of php.ini and expanding the IIS memory limit to 128 MB I'm now back to the original state of "APPLICATION ERROR 0000401" "Database query failed. Error received from database was 0002006: MySQL server has gone away for the query: INSERT INTO mantis_project_file_table (project_id, title, description, diskfile, filename, folder, filesize, file_type, date_added, content) VALUES" and subsequently showing the content of the file to be uploaded in the browser. Now it seem's the only thing left to investigate is mySQL, right? Which params would have to be altered to test this? (I'm not familiar with mySQL, only with other DBs)

atrol 2010-10-17 16:47 developer ~0027062	setting max_allowed_packet should fix the problem

markus.humm 2010-10-18 14:16 reporter ~0027066 Last edited: 2010-10-18 14:29	How can somebody close this problem as solved with a ... should fix the problem? Why isn't it left open until the original author of the issue report has tested the suggested fix and confirmed that should = does? Should can also turn out to fail! Only a test in the target system will show the outcome. And another thing: what's sort of setting is max_allowed_packet? Is it in php.ini or on the MySQL side? If the latter, in which configuration file?

thraxisp 2010-10-18 14:51 reporter ~0027068	The issue is marked as "resolved" which means that the developers believe that it is fixed. If the originator disagrees, they can reopen the issue. max_allowed_packet is a mysql thing and is usually in the /etc/my.cnf file.

atrol 2010-10-18 15:21 developer ~0027071	Sorry, I should have written: Feel free to reopen the issue if your problem is not solved by setting max_allowed_packet. You wrote: "Now it seem's the only thing left to investigate is mySQL, right? Which params would have to be altered to test this? (I'm not familiar with mySQL, only with other DBs)" I thought this was enough that max_allowed_packet is a mySQL setting.

markus.humm 2010-10-18 15:31 reporter ~0027073	Ok, now I understand. Sorry for my note then. Everybody runs such a bugtracking system with a different process in mind.

View Issue Details

Activities