Piped logging is extremely powerful when used correctly, and has far more flexibility. The way it is described here, we will be attempting to negate the memory hungry apache processes that creep up when a server is hosting very low traffic websites (less than 1 request per second) with traditional Apache log configurations.

cat  /usr/local/apache/logs/error_log | grep Graceful
[Sun Jul 14 16:01:10 2013] [notice] Graceful restart requested, doing restart
[Sun Jul 14 18:14:40 2013] [notice] Graceful restart requested, doing restart
[Sun Jul 14 20:11:31 2013] [notice] Graceful restart requested, doing restart
[Sun Jul 14 21:16:42 2013] [notice] Graceful restart requested, doing restart

This error is caused due to log processing and its fixed after enabling piped Apache logs. This can be done by either of the following methods

You can enable piped logs via WHM using the following steps.

Backup your Apache configuration file

cp -r /usr/local/apache/conf/httpd.conf /usr/local/apache/conf/httpd.conf_bak

WHM » Service Configuration » Apache Configuration » Piped Log Configuration

Check the box labeled Enable piped Apache logs.

 

Enable piped Apache logs via command line.

vi /var/cpanel/cpanel.config

Add the following

enable_piped_logs=1

Update modified changes.

/usr/local/cpanel/whostmgr/bin/whostmgr2 –updatetweaksettings

Rebuild the Apache config

/scripts/rebuildhttpdconf

Restart apache service

/etc/init.d/httpd restart

Thats all!!

0.00 avg. rating (0% score) - 0 votes
Website Pin Facebook Twitter Myspace Friendfeed Technorati del.icio.us Digg Google StumbleUpon Premium Responsive