|
||||||||||
|
|
Awstats “update now” button shows blank page and cpanel error log shows “Out of Memory”February 27, 2010 on 5:24 am | In Cpanel | No CommentsThe cPanel error logs shows Out of Memory! when you click the “update now” button in Awstats. This usually happens when cPanel’s php is set with low memory. But in most of the cases this is not the issue. Go to WHM > Tweak Settings > “The maximum memory a cPanel process can use before it is killed off (in megabytes). Values less than 128 megabytes can not be specified. A value of “0″ will disable the memory limits.” Set this to 0 or a higher value.. In the Awstats case, the cPanel processes memory is getting exhausted. This can be done also by editing the file /var/cpanel/cpanel.config
Custom php.ini for PHP CGI in cPanel.February 26, 2010 on 3:36 am | In Cpanel, PHP | No CommentsHi guys, When PHP is compiled as CGI, you won’t be able to provide custom php flags in .htaccess or just simply add a php.ini if your home directory. To enable a custom php.ini for your domain running PHP as cgi, perform the following steps. Please note that I am considering that the server has PHP4 and PHP5 where PHP4 is default (dso)-not relevant and PHP5 (cgi) My username is “presoon” so my home directory will be “/home/presoon” (replace with yours) create a custom cgi script in your cgi-bin directory.
add the following contents.
You should have the custom php.ini at “/home/presoon/public_html/”
Now to the .htaccess file at “/home/presoon/public_html/”
Please note that AddHandler given above is to change default php to PHP5. If you have only PHP5 which is compiled as CGI, you can remove the directive AddHandler from .htaccess. Now the values given in your php.ini at /home/presoon/public_html/ should reflect you info page. /sbin/hotplug: no runnable /etc/hotplug/aaaa.agent is installed in /var/log/messagesFebruary 21, 2010 on 11:32 am | In Centos, Linux, Ubuntu | No CommentsHi guys, You might have been facing the error getting logged in /var/log/messages. Deeper research in Google gave the result that it is the issue with the loaded Kernel. Before going for and upgrade, just confirm the following. Check whether the following files are present.
Now try the following before kernel upgrade. The issue should have been fixed by now. If the message is still coming up in /var/log/messages, you will need to go for Kernel upgrade. Thank you guys.. |
![]() Powered and designed by Presoon.com. |