Fatal Error Image Message

[Norma Kennedy]

I have been using my gallery with no problems for a few months now.
I have not changed or touched any settings with fear that it would start getting glitchy on me.

Well today I went to upload an image and it loaded it to my queue
and showed me this error

Fatal error: Allowed memory size of 75497472 bytes exhausted (tried to allocate 19200 bytes) in /data/21/2/93/15/2093993/user/2296109/htdocs/image-inc.php on line 116

What does this mean ?
How do I empty out my queue?

THANKS !
Norma

[Norma Kennedy]

This is what I currently have in my pp-inc.php file:

error_reporting (E_ALL ^ E_NOTICE);
define('PP_SCRIPT', 'PP_Pro');
ini_set("memory_limit", "72M");

I know on other post you mention to change this line but it allready is set
properly.

So what do I do now?

thanks, Norma

[Chuck S]

Well the only possible thing for you to try is two things because your memory is already enough.

1. Delete all numeric directories under your uploads directory.

You can then try uploading

2. Make sure under admin upload options your max image height width are 1500 or below.

You can try uploading

3. Switch to Imagemagick as your image processor if at all possible.


The issue is with GD2 and server memory so you must try these steps one at a time in order.

[Norma Kennedy]

Originally Posted by Chuck S

Well the only possible thing for you to try is two things because your memory is already enough.

1. Delete all numeric directories under your uploads directory.
Is this in the admin panel or the FTTP on my server?
You can then try uploading

2. Make sure under admin upload options your max image height width are 1500 or below.

You can try uploading

3. Switch to Imagemagick as your image processor if at all possible.


The issue is with GD2 and server memory so you must try these steps one at a time in order.

Thanks!

[Chuck S]

Your welcome

[Norma Kennedy]

Are These the files you are talking about?
I have 4 pages of these files. I should delete all files that have a numeric number ?
Just wanting to double check as I would hate to delete something I should not !


Parent Directory
1 File Folder 02-Aug-2010 10:02 2093993.2296109 rwx rwx rwx
10 File Folder 22-Jul-2010 07:53 2093993.2296109 rwx rwx rwx
100 File Folder 19-Jun-2010 22:37 2093993.2296109 rwx rwx rwx
101 File Folder 01-Aug-2010 09:21 2093993.2296109 rwx rwx rwx
102 File Folder 21-Jun-2010 10:35 2093993.2296109 rwx rwx rwx
103 File Folder 20-Jul-2010 15:15 2093993.2296109 rwx rwx rwx
104 File Folder 13-Jul-2010 09:30 2093993.2296109 rwx rwx rwx
106 File Folder 16-Jul-2010 17:00 2093993.2296109 rwx rwx rwx
107 File Folder 28-Jul-2010 20:16 2093993.2296109 rwx rwx rwx
109 File Folder 21-Jul-2010 21:14 2093993.2296109 rwx rwx rwx
11 File Folder 27-Jul-2010 17:10 2093993.2296109 rwx rwx rwx
110 File Folder 03-Jul-2010 18:36 2093993.2296109 rwx rwx rwx
112 File Folder 29-Jun-2010 09:28 2093993.2296109 rwx rwx rwx
113 File Folder 08-Jul-2010 14:45 2093993.2296109 rwx rwx rwx
114

[Chuck S]

Yes ALL numeric directories beneath UPLOADS can be safely removed. You dont want to touch anything under DATA.

[Norma Kennedy]

Yay Chuck this worked Beautifully !

If this happens again will similar files re build and should I try deleting them again?

Hey.... I am starting to get around much better now

Thanks !
Norma

[Chuck S]

More than likely one large file became stuck and prevented other files so you where clogged.

[stmpspaz]

Originally Posted by Chuck S

More than likely one large file became stuck and prevented other files so you were clogged.

Is there any way to make it so when a large image upload is attempted & fails that it doesn't clog the queue?

We have 1300+ members and they frequently upload an image that is too large and clogs their queue (and if they're unregistered, it not only affects them, but all other unregistered users too).

When they get the error message that the image was too large, they resize it and then get frustrated because when they try again they think their newly resized image is too large also - when in actuality, the original image is still sitting there causing the block.

It would be ideal if that "too large image" was not stored in the queue, so once they got the error message that it was too large, they could immediately resize and upload again without us having to intervene and clear out the too large image out of their queue.

Suggestions?

[Chuck S]

Not really if the image is stopped by the server. If your server stalls PHP then the script can not do anything. we clear things we can in the script but if your server stops php our script is not running hense there is nothing it can do.

I would suggest you use imagemagick as a processor and if not then make what changes you can when using GD2 like adding more memory via an ini_set line and also under upload options making sure your max image thresholds are like 1200 or so not 2500.

[stmpspaz]

I've already added both (to pp-inc.php):
ini_set("memory_limit", "48M");
ini_set("max_execution_time", 0);
with no change in results.

My "Maximum multimedia upload size in Kb" was 8000, so I lowered it to 1200. Then uploaded a photo that was 1900KB - it still loaded fine. Also tried a 2500KB picture with got the error message and then clogged the queue.

So I don't understand what the "Maximum multimedia upload size in Kb" really does if it doesn't stop a member from uploading something larger than that.

[Chuck S]

multimedia image setting has nothing to do with images those are the max height width settings at top of upload options.

You can never upload a file over your PHP servers max upload filesize which is normally 2mb unless you have modified PHP so anything over 2048 and you will have a problem.

Nothing is going to stop a member uploading anything if it makes the server stop PHP. when your server stops PHP it stops our application which is what I said above. Server trumps software every time.

[stmpspaz]

I want to make sure I understand this correctly, so please bear with me if I'm asking you to repeat yourself.

If a person selects a large file to upload (greater than the 2MB PHP server max) then there isn't really anything the software can do to warn them / stop the upload to the queue as they never get back to the Photopost software because the PHP upload croaks (and leaves the large uploaded file in the "queue" which blocks them from further uploads) - Correct?

So it doesn't really matter what I set the Max allowable image width/height in pixels to as this check is done AFTER the image is uploaded, so it never gets there (assuming the file is larger than 2MB), Correct?

Is there a way in the Photopost software BEFORE they upload to check to see if their upload queue is "blocked" (or even if it's totally empty) and either:
1) Give them a warning that says the queue needs to be cleared contact xyz for assistance
or
2) Delete all files that reside in their upload queue before attempting the next PHP upload?
or
3) A combined option - Warning, your queue is blocked, would you like to delete the failed images that are causing you upload problems? With a yes/no option for them to proceed with.

It appears from searching the forum that this is a common problem and if there was a way to address it from the software/user end it would be fantastic!

[Chuck S]

Well its not really about size really. You can alter your PHP settings to allow larger file uploads but your using GD2 which is part of PHP.

It really is knowing your server limitations. There are things you can do but if your going to be processing large file uploads you really need to use Imagemagick which is not part of PHP.

Photopost is a PHP program and constrained by your php settings on the server. If PHP shuts down then our script is not running and therefore can not do anything.

Now we could in the future as there is no option for that right now do some uploads clear thing but there is a real reason it is not done because that would for alot of people be a bug. what happens if you upload a large amount of files and you do not process them all and want to come back later and finish. You expect them to be there.

If you upload a file larger than your server allows that file is DELETED. If you upload a file larger than GD2 can process then GD2 caused PHP to shut down. Thats the issue. One that happens our script is no longer running till you refresh your page.

Now as I have stated in numerous threads you can try lowering the max image sizes in upload options that will help from having alot of GD2 issues to happen but there is a size limit for any server setup if your using GD2 and large images where they will always cause an issue. Once you know this the easiest thing to do is make sure you use mogrify ( imagemagick ). You will not have this issue using imagemagick