Hi guys, I'm having a strange problem. When you upload to my forum and download everything works great. I uploaded an attachment that was 100megs and it uploaded/downloaded fine and it worked great for about a week. Now whenever I click on the attachment it gives me a "Internal Server Error 500" but all other downloads are working fine. How come it only does this with uploads over 100megs?
I checked the server log and here's the error;
FATAL: emalloc(): Unable to allocate 109973575 bytes
[Wed Jun 6 17:45:09 2007] [error] Premature end of script headers: /var/chroot/home/content/g/u/i/mysite/html/forums/attachment.php
Any ideas?
You need to up your php.ini's max_post_size and max_upload_size. Contact your host if you can't.
I configed the php.ini about a month ago and everything is working fine. You think this might be a .htaccess problem?
Here's a screen shot, as you can see it uploaded fine but clicking on it is another thing.
Tikitiki Wrote:You need to up your php.ini's max_post_size and max_upload_size. Contact your host if you can't.
Tikitiki, I don't mean to be rude I understand you're trying to help. But I already posted that I configed php.ini a long time ago.
post_max_size = 200M
file_uploads = On
upload_max_filesize = 200M
If it were not, how would I be able to upload 104.88megs in a post as you see here
http://community.mybboard.net/attachment.php?aid=6495
It's when I click on the link I get the error. Thanks for your help.
Mass, did you google it?
Google
This was the most interesting
Quote:We had this same issue and sent over 2 weeks researching the cause and finding the solution. This is what worked for us; for you it could be something different. The error turned out to be an Apache issue. We had to use the DisableAcceptEx() directive in Apache2.2 under Windows. Once this was turned on, the apache service started consuming more and more memory, and throw the above errors, and restart itself every few hours. (See issue and some solutions here: http://issues.apache.org/bugzilla/show_bug.cgi?id=34664 ) We changed the ThreadsPerChild setting as suggested in that thread and the problem went away. Hope it helps.
Sam4 Wrote:Mass, did you google it? Google
This was the most interesting Quote:We had this same issue and sent over 2 weeks researching the cause and finding the solution. This is what worked for us; for you it could be something different. The error turned out to be an Apache issue. We had to use the DisableAcceptEx() directive in Apache2.2 under Windows. Once this was turned on, the apache service started consuming more and more memory, and throw the above errors, and restart itself every few hours. (See issue and some solutions here: http://issues.apache.org/bugzilla/show_bug.cgi?id=34664 ) We changed the ThreadsPerChild setting as suggested in that thread and the problem went away. Hope it helps.
Thanks Sam. That's prob it then.
Mass Wrote:Tikitiki Wrote:You need to up your php.ini's max_post_size and max_upload_size. Contact your host if you can't.
Tikitiki, I don't mean to be rude I understand you're trying to help. But I already posted that I configed php.ini a long time ago.
post_max_size = 200M
file_uploads = On
upload_max_filesize = 200M
If it were not, how would I be able to upload 104.88megs in a post as you see here http://community.mybboard.net/attachment.php?aid=6495
It's when I click on the link I get the error. Thanks for your help.
I was under the impression you didn't read my reply because saying 'You configed the php.ini a long time ago' doesn't tell me anything relevant to my response.
If you were uploading a large image, GD probably maxed out the memory limit trying to generate a thumbnail.