My website has been running more or less well for 3 months, today I began getting a number of Temporary Overload - 503 errors... Before these started the entire site was down for about 15 minutes with the following error on all PHP pages:
Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 311296 bytes) in /home/juot/public_html/forums/index.php on line 468
Obviously the exact numbers and line numbers were different on various php pages but I couldn't access anything, including the admin menu.
I contacted the hosting company and they gave me this reponse and closed the trouble ticket:
OK, the only scripts I'm running is Vbulletin 3.7.2 and a few popular add ons that have been running more or less fine for 3 months now- this issue started today... the database size (per the .sql file I download as a backup) is about ~80 MB...
I find it hard to believe that vbulletin hard-codes a maximum memory limit somehwere- am I wrong? If so how would I change it?
Thanks.
Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 311296 bytes) in /home/juot/public_html/forums/index.php on line 468
Obviously the exact numbers and line numbers were different on various php pages but I couldn't access anything, including the admin menu.
I contacted the hosting company and they gave me this reponse and closed the trouble ticket:
Hello,
It seems that the issue with your website is caused because the memory_limit set for the execution of a component includes on your front page is exhausted. However this limit is lower than the memory_limit set globally on the server which is 96MB. You may check the global memory limit via the following URL:
<Link to phpinfo confirming 96 MB limit>
The error should be caused because you have different memory_limit set in one of the your components scripts. I have tried to find which is the exact scripts but unfortunately to no avail. You should review your scripts and remove or change any lines which has the memory_limit set to a different value than the global one on the server and the issue should be resolved.
In order to complete the above you may also contact an expert local web developer. S/He should be able to set the memory_limit hardcoded in your scripts to 96MB or to remove the lines which are settings this limit. This way you will use the global memory_limit setup on the server.
Unfortunately we do not offer such development services at this time.
If you have any other questions or comments please do not hesitate to contact us.
...
It seems that the issue with your website is caused because the memory_limit set for the execution of a component includes on your front page is exhausted. However this limit is lower than the memory_limit set globally on the server which is 96MB. You may check the global memory limit via the following URL:
<Link to phpinfo confirming 96 MB limit>
The error should be caused because you have different memory_limit set in one of the your components scripts. I have tried to find which is the exact scripts but unfortunately to no avail. You should review your scripts and remove or change any lines which has the memory_limit set to a different value than the global one on the server and the issue should be resolved.
In order to complete the above you may also contact an expert local web developer. S/He should be able to set the memory_limit hardcoded in your scripts to 96MB or to remove the lines which are settings this limit. This way you will use the global memory_limit setup on the server.
Unfortunately we do not offer such development services at this time.
If you have any other questions or comments please do not hesitate to contact us.
...
I find it hard to believe that vbulletin hard-codes a maximum memory limit somehwere- am I wrong? If so how would I change it?
Thanks.
Comment