Question PHP Memory Limit's after isntalling DragonByte SEO

[motorman]

Hey Guys,

I have just purchased Dragonbyte SEO Pro.

When I enable it on my forum it gives me PHP errors on nearly every page.

The php.ini file on the server is set at 128mb.

I manage to add the line to solve some of the modules problems and generate some initial sitemaps:

ini_set('memory_limit', '512M');

I added this to class_core.php and it has made little difference and I'm getting errors everywhere.

I have done so much research and have yet to resolve this issue.

Thanks for you help.

 

[Fillip H.]

Can you post the error messages?

 

[motorman]

This is what I'm getting from numerous modules:

Error- Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /home/minis/public_html/dbtech/dbseo/includes/scripts/forumdisplay.php on line 21

 

[motorman]

Another one:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 316009 bytes) in /home/minis/public_html/dbtech/dbseo/includes/class_core.php on line 4505

 

[bzcomputers]

Yes, both those errors are most likely from the same issue - PHP running out of memory. It just happened to be different files running at the time the memory ran out.

Also, your choice to add a separate memory limit to the class_core.php is not really going to help since the issue doesn't actually lie within that file but with memory for PHP files overall.

Since I don't know your expertise in servers and PHP if you think I ask an obvious question just bare with me.

You say you have the PHP Memory within php.ini set now to 128mb, is this what is also being reported by vB (look in the main AdminCP page at the top)?

What type of server are you running on shared, VPS, dedicated?

 

[motorman]

This is the strange part.

In the php .ini file it's set to 512mb but in vbulletin it shows as only 32mb.

I don't know how to actually set it in vbulletin?

PHP 5.2.9 Attachment Usage 2.31 GB Posts to Moderate 0 [View]
PHP Max Post Size 64.00 MB Avatar Usage 12.28 MB Attachments to Moderate 0 [View]
PHP Maximum Upload Size 1.00 GB Profile Picture Usage 3.40 MB Events to Moderate 0 [View]
PHP Memory Limit 32.00 MB Unique Members Today 51 Messages to Moderate 0 [View]
MySQL Version 5.1.72-cll New Users Today 2 New Threads Today 4
MySQL Packet Size 1.00 MB

We are using a shared physical server. Have plenty of free resources on the box.

 

[bzcomputers]

That's what I thought was happening.

The error messages are all reporting only 32mb of memory being allocated to PHP, this is further backed up by vB reporting the same thing. There is no way to set this within vB. When vB reports the memory limit as 32mb it is reporting what the server php memory is currently limited to.

So, somewhere on the server there is a memory limit set which is blocking your php.ini setting of 512mb and currently you are actually only allocating 32mb to PHP.

Have you restarted Apache since you updated the memory limit in php.ini? New settings will not take place until Apache is restarted.

 

[motorman]

I'm pretty sure it was restarted but double checking with the hosting provider now.

What could be blocking it?

Where else can I check?

Basically at the moment Dragonbyte SEO will not run at all until I fix this making it a waste of $200. I wanted to purchase a couple of other products but this is starting to put me off.

 

[bzcomputers]

If I was a betting man, I would say it was that your server wasn't restarted.

Sometimes hosting companies will also place memory limits on shared servers. This is something you should ask them and they should be able to tell you pretty quickly.

Dragonbyte SEO does use some memory but the company will work with you to get any issue fixed quickly. You just need to keep in mind the possible timezone difference between you and them. That's why I stepped in tonight to try and help because I knew they wouldn't be around for a few hours.

 

[motorman]

You put me onto it when you said something was blocking the setting and you were right.

The config.php was limiting the total memory overwriting what was set in php.ini.

When changing PHP settings they take effect real time and a restart of apache or the server is not required.

Thanks for putting me on the right path.

 

[Fillip H.]

Glad to hear it's working for you now, and thanks bzcomputers for helping out with this

Sundays and Mondays are notoriously busy for me unfortunately