Fatal error: Allowed memory size exhausted

[AnotherJacob]

Hi,

I just installed the newly released v3.8.1 vBulletin board.

It's a clean install with NO mods/upgrades made on a newly created empty database ( MySQL 5.0.51a ).

The installation worked like a charm with no errors at all, then setting up the catagories and forums went smooth also. Then my problem began when starting adding threads to my forum, there i created threads with informations about a file and then attached the file as an attatchment. It went fine the first 3 times, but when it came to the 4th thread the filesize was a bit larger than the first 3 (5.5 mb) and i get this error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 5092453 bytes) in /hsphere/local/home/*deleted*/*deleted*/includes/class_core.php on line 748

Now, before you ask ... yes, I have increased the filesize for that correct file extension in the controlpanel for attachments, I've set the file limit to 25mb, and it also shows when i enter the attachment feature in the threads. I've tried compressing the file using different file extensions (rar, zip and such), but the problem persists ..... The line 748 that this error refers to are also changing from time to time, it has been like foru different lines ranging from number 748 to 2102, so i don't think it's something that i can change manualy in the class_core.php file?

I've used the search function and have read other threads having this issue back to v3.0 board, but none of the suggested "workarrounds" does the trick for me.
plz help me .... any suggestions are most welcome

thx in advance!

[Wayne Luke]

Which specific workarounds did you try?

If you haven't already, I would suggest telling vBulletin to store attachments in the file system. This will lower the memory requirements needed for uploading larger files. You can do this in the Admin CP under Attachments -> Attachment Storage Type.

The default is to store it in the database which requires the entire file to be added to a variable for the SQL query to be generated.

[AnotherJacob]

I've tried that ..... but then i get this error mesage:

Your server has PHP's SAFE_MODE enabled. You cannot move attachments to files while SAFE_MODE is enabled. Please contact your host and ask them to consider disabling it if you wish to use the file system for attachments.

I've mailed them and asked them to do the changes, but they refused the first time so I've asked them nicely to reconsider again.

Are there any other ways to force the attachments to the filesystem? I mean .... why does it go into the DB in the first place?

So far I've tried the suggestings i found in these threads:

http://www.vbulletin.com/forum/showthread.php?t=299138&highlight=fatal+error+allowed

http://www.vbulletin.com/forum/showthread.php?t=293985&highlight=fatal+error+allowed

http://www.vbulletin.com/forum/showthread.php?t=290065&highlight=fatal+error+allowed

http://www.vbulletin.com/forum/showthread.php?t=289893&highlight=fatal+error+allowed

http://www.vbulletin.com/forum/showthread.php?t=287988&highlight=fatal+error+allowed

http://www.vbulletin.com/forum/showthread.php?t=282313&highlight=fatal+error+allowed

http://www.vbulletin.com/forum/showthread.php?t=282274&highlight=fatal+error+allowed

and more .... seems the best idea is to uppen the memory to 32 ... I'm there but doesn't work still.

[Wayne Luke]

Well it goes into the database in the first place because we don't know if you have safe mode enabled or not. There is no way to store them in the file system if you have safe mode enabled that I am aware of.

[AnotherJacob]

oh sry .. i edited the above post before i saw your reply ....

ehm ... not sure i understand what you mean, but maybe the way the board is build? .. i can run phpbbX with all the attachments i want with np at all? I have 2 phpbb2 boards on the same DB server running fine with attachments.

I'll await my hosts reply on my request and see if they've changed opinion.

[AnotherJacob]

OK .. I've got the reply:

Safe mode kan ikke slåes fra hos surftown, det er en global indstilling for alle servere, men det er nu heller ikke det der er dit problem, du
ville ikke kunne ændre det alligevel, det skyldes at dit problem består i at du vil bruge mere hukommelse end der er til din rådighed på
den server du ligger på og med det abb. du har.

Du har 32Mb til din rådighed som privat kunde og 128Mb som erhvervskunde, så det eneste der ville kunne løse dit problem er at opgradere til erhverv.

It's in Danish so 'll try and translate as best as i can:

Safe Mode cannot be disabled from Surftown (the host), it's a global setting for all servers, but that is not your problem, it wouldn't change your situation anyway, the problem is that you want to use more memory than you have available on the server you are hosted at and the subscription you have.
You have 32Mb available as private customer and 128Mb as companyclient, so the only thing that will solve your problem is to upgrade your subsricption.

So .... does that mean i cannot use vBulletin to host files larger than 33554432 bytes ??? plz, there must be a way, this cannot be?

[AnotherJacob]

Is there anyone who also "just" have 32Mb available who would take the time and try and upload a file, say of 6Mb size as an attachment? Upgrading my account is not an option, that is too expensive for me and I'd rather go back to phpbb type board again. So it would be great to have double checked that it is impossible to attach such "large" files with "only" 32Mb available.

[Steve Machol]

That is probably not going to work. Plus there are many other settings that will affect this.

In addition to the vB settings, the allowed size of the attachments depends on the PHP and MySQL configuration. You may need to check and change the upload size for both PHP and for MySQL. Note, you'll need to have root access to the server to do this (or have your host do it.) Make these changes to php.ini:

upload_max_filesize = xM

..and my.cnf (or my.ini for Windows systems)

set-variable=max_allowed_packet=xM

Change it to the size ('x') you want in Megabytes. Restart the webserver and MySQL after making these changes.

Note: Do NOT use MB, just M for the megabytes setting.

You may also need to increase the memory_limit, max_execution_time and max_input_time variables in php.ini.

Also you might want to take a look at this for other settings that affect file uploads:

http://www.vbulletin.com/forum/showpost.php?p=594570&postcount=12

http://www.vbulletin.com/forum/showthread.php?p=748319#post748319

[AnotherJacob]

ok, I've copy/pasted this and mailed it to my host, hopefully it is doable from their side as I have done everything i can from my side.

[AnotherJacob]

All they claim is that 32Mb is not eneough and upgrading to 128Mb would solve this issue.

Now all I want to know is a simple yes or no, can I upload "Mega Huge" files of say 10Mb with "only" 32Mb ram in the database with only changing options that doesn't require root admin access to the database server?

[Steve Machol]

Probably not. As per post #8 there are many other settings that can affect this.

[AnotherJacob]

hmm ok thx.

Does that mean my host is outdated when it comes to the functionality of private accounts? I mean ... this must be a pretty common problem if they use the same standard setup as other hosts? I've looked at HostMonster.com, as far as i can see they do have a feature where i can edit the php.ini file from the control panel, so maybe it's also possible to edit the mysql ini file as well? ... Anyone got any expirience with this host?

[Steve Machol]

No it means that uploading large files with PHO/MySQL is generally not supported by default on more servers.

[AnotherJacob]

generally not supported by default on more servers.

so the feature for attachments in vBulletin is outdated? I mean ... this is year 2009 and if i take a photo with my digital camera it easily goes way over 3Mb in size ... so that i can't even upload? Any plans of redoing the attachments features in a future release?

[Steve Machol]

No, this is not a vB limitation. It's a server one. Please read my post again.