Page 1 of 1
Problem with large file upload
Posted: Mon Nov 26, 2007 12:01 pm
by Maouk
Hi,
I have some problems with "large" files (from 200 to 700mb more or less).
When I hit the "Go" or "Go & enter properties" the system return, after few second, to the frontpage without add the file.
To do some tests, I have modified the php.ini with:
upload_max_filesize 750MB
post_max_size 750MB
max_input_time 3600
but the result is the same.
Can someone help me?
Ah sorry: I have a linux slackware 11.0 with apache 2.2.4, php 5.2.5 and serendipity 1.2
Re: Problem with large file upload
Posted: Mon Nov 26, 2007 12:14 pm
by garvinhicking
Hi!
You must also raise your memory_limit to about twice the size of the file you're uploading, because it is parsed by PHP.
Regards,
Garvin
Posted: Mon Nov 26, 2007 1:03 pm
by Maouk
Now I have, just for test,
memory_limit 1024MB
upload_max_filesize 1024MB
post_max_size 1024MB
max_input_time 3600
and I try to upload a 200MB file but there is no difference.
After five seconds (more or less) the "Add media" page switch to "Frontpage" like before.
Any other suggestion?
Posted: Mon Nov 26, 2007 1:16 pm
by garvinhicking
Hi!
Did you enter a maximum file size limit in the s9y configuration options?
Can you check your PHP and Apache errorlogs? It might be that your processes are somehow coredumping?!
Regards,
Garvin
Posted: Mon Nov 26, 2007 3:01 pm
by Maouk
The maximum file size limit in the s9y config is not set and I don't see any error in the Apache or Php logs when I upload a 200mb file.
I don't know if it coredump but I don't see anything useful in the log system.
If php settings are ok, where I can check for other errors? File inside serendipity maybe?
Posted: Mon Nov 26, 2007 4:04 pm
by garvinhicking
Hi!
Maybe you need to check the PHP.ini option "log_errors" and "error_log"? Did you check also the Apache core error logfile?
Check your whole /var/log for files with a updated timestamp after you uploaded the file. Usually in /var/log/syslog your coredump should be listed.
The error seems to happen on the Apache-/PHP-level, so s9y can't log that.
Regards,
Garvin
Posted: Mon Nov 26, 2007 4:43 pm
by Maouk
log_errors and error_log already "on" and all the system logs goes into /var/log/messages. I try to check, again, my php/apache config.
Thanks for help me.
Posted: Tue Nov 27, 2007 1:28 pm
by Maouk
After a test i've found this on the Apache access_log:
IP - - [ date ] "GET /serendipity_admin.php?serendipity[adminModule]=media&serendipity[adminAction]=addSelect HTTP/1.1" 200 22142
IP - - [ date + 4 sec ] "POST /serendipity_admin.php HTTP/1.1" 200 11911
I check also the Apache error_log and the PHP logs but this is the only log of the upload action.
Any suggestion?
Posted: Tue Nov 27, 2007 1:37 pm
by garvinhicking
Hi!
Access_log doesn't log such things. You'll have to check Apache error_logs as well as the PHP Error logs and your syslog.
Regards,
Garvin
Posted: Tue Nov 27, 2007 2:19 pm
by Maouk
Yes, i know but as I write before I check also the Apache error_log and the PHP logs but this is the only log of the upload action.
Thanks however.
Posted: Tue Nov 27, 2007 3:05 pm
by garvinhicking
Hi!
Hm, but there must be other entries. If PHP bails out, and your server is configured to log syslog errors and php errors, there must be a logfile which contains the error.
This can be a multitude of server settings, I would need root level access to a server to debug this, so I can't really offer you more help on this. But I am quite sure it is related to PHP, not Serendipity.
Regards,
Garvin