UPLOAD folder large file problem

[okaven]

Hello, All.

I have a strange problem "uploading" large JPEG files (around 1.5MB and larger [I didn't try to figure out where the breaking point is]) from the upload folder to their destination directories.

As a note, I am not trying to FTP the files to the server, but have the files already in the UPLOAD folder. And, I am trying this with one file at a time. The version ee is 1.5 RC 4.

Everything works fine with files at under ~1.5MB. The files go into the directoies where they belon, into the database and are visible online, including thumbs and all.

When I use large JPEG files (i.e. 4MB) the ee upload page immediately jumps to a "The page cannot be displayed" page and nothing happens. No pictures uploaded added, etc. No nothing in the logs either.

Are there any size limitations as to the individual size of files that can be used in the UPLOAD folder?

If you have any thoughts, I would appreciate it.

Thank you for your help!

Oliver

[wkitty42]

it almost sounds like your problem might be a memory settings problem with php sessions/tasks... in php.ini, there are settings for things like "how much memory can a script use?" it is possible that your settings are limiting not only the memory for php tasks but also the memory used for GD (internal to php) and/or ImageMagik... i don't know how the systems allocate "per process" memory but it is possible that only one block is allocated and everything has to run in that one allocation...

this also seems to possibly be related to a/the known "bug" that limits the number of images that can be selected (CTRL-Click) in the upload folder and processed during the upload to database phase... on my system, i can (generally) select up to seven (7) images but not eight (8)... its not a timing problem that i can see as i'm set to allow up to 1800 seconds... my setup is also configured to use persistent connections between my web server and my mysql server... these connections do have a timeout period in them and that might be timing out and terminating the connection... i've not had much of a chance to really dig into these settings and test them... these are some thoughts on what might be happening, though...

[okaven]

wkitty42:

Yes, I have suspected php or vsftpd as the culprit, rather than ee, since nobody here seems to have the problem. However, my filesizes in php.ini were all set to 8M.

No comes the weird part. I just went into the php.ini again and changed all values to 16M. I also adjusted the logging --and voila-- suddenly no more problems.

While I really cannot explain it, my problems are solved ;-)

Thanks again for the time responding,

-Oliver

[wkitty42]

wkitty42:

Yes, I have suspected php or vsftpd as the culprit, rather than ee, since nobody here seems to have the problem. However, my filesizes in php.ini were all set to 8M.
right, by "filesizes", it sounds like that was the max upload filesize..

No comes the weird part. I just went into the php.ini again and changed all values to 16M. I also adjusted the logging --and voila-- suddenly no more problems.
interesting... was the max memory for a process (or whatever it is called) one of those settings? if so, that might have been it...

While I really cannot explain it, my problems are solved ;-)

Thanks again for the time responding
excellent! no problem on the responding... i'm playing with stuff all the time... sometimes i just happen to be able to add 2 and 2 and get 4 for others when they need it :)

BTW: many settings for php can be set in yout .htaccess (or whatever you may call it) file... in my setup, i set some things for php to larger values than i do for other projects and i do this via the .htaccess rather than in the php.ini... this allows me to make the changes immediately and to keep smaller tasks from consuming more memory than necessary... it also allows me to keep the server up and running without having to reboot it... some systems can terminte tasks like the webserver and php allocation (i run my php as a module within the confines of my apache server's memory space) and restart them without having to reboot the entire machine... i can't do that in my setup for various reasons...

[dscottf]

BTW: many settings for php can be set in yout .htaccess (or whatever you may call it) file... in my setup, i set some things for php to larger values than i do for other projects and i do this via the .htaccess rather than in the php.ini... this allows me to make the changes immediately and to keep smaller tasks from consuming more memory than necessary... it also allows me to keep the server up and running without having to reboot it... some systems can terminte tasks like the webserver and php allocation (i run my php as a module within the confines of my apache server's memory space) and restart them without having to reboot the entire machine... i can't do that in my setup for various reasons...

Could your perhaps start a new thread explaining that? Please? example .htaccess maybe. That sounds really interesting