618 pointsLike some sort of WPMU DEV God"I'm new here
drdave
Member
—
18th December 2010 04:03
When I access pages I get these types of errors randomly
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 110 bytes) in /home2/mainsite/public_html/wp-includes/plugin.php on line 160
Bluehost had me raised the limit from 64MB to 128MB in php.ini but it did not fix the problem.
Only thing I know I did was upgraded to Wordpress 3.0.3 Not sure if that was the cause of the problem. The way I understand it it might be plugin related but my plugins were all working fine before.
When I access pages I get these types of errors randomly
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 110 bytes) in /home2/mainsite/public_html/wp-includes/plugin.php on line 160
Bluehost had me raised the limit from 64MB to 128MB in php.ini but it did not fix the problem.
Only thing I know I did was upgraded to Wordpress 3.0.3 Not sure if that was the cause of the problem. The way I understand it it might be plugin related but my plugins were all working fine before.
drmike since dronix suggestion yesterday I have not seen the error but I am still getting some hesitation before the pages load and this morning I got.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@mysite.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
The error log only say
[Sat Dec 18 07:56:03 2010] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
The 500 errors are not new though. Seen them before.
Responses (7)
Member — 18th December 2010 04:08 #
try adding the following to your wp-config.php
define('WP_MEMORY_LIMIT', '128M');Member — 18th December 2010 04:10 #
Heard about that too but do I first remove the php.ini entry? Put it back to 64MB?
Member — 18th December 2010 04:12 #
No leave the php.ini with 128M.
Member — 18th December 2010 04:14 #
Ok I will give it a go and see what happens.
Thanks dronix
Keeper of the Dark Chocolate — 18th December 2010 12:48 #
Give this a read please:
http://premium.wpmudev.org/forums/topic/antisplog-out-of-memory-allocated-27000832-tried-to-allocate-197540-bytes-in-homepublic_htmlwp-includesfunctionsphp-on-line-251
You have to change the memory limit in a couple of different places now.
Please also remember that bluehost is an overseller where they place hundreds of users on a single box. The box itself may be running out of memory.
Member — 18th December 2010 15:00 #
drmike since dronix suggestion yesterday I have not seen the error but I am still getting some hesitation before the pages load and this morning I got.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@mysite.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
The error log only say
[Sat Dec 18 07:56:03 2010] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
The 500 errors are not new though. Seen them before.
And thanks for the link I checked it out.
Member — 19th December 2010 01:02 #
Hopefully it is ok to move the 500 error to a new post
http://premium.wpmudev.org/forums/topic/internal-server-error-1?replies=1#post-69706
Become a member