Control Web Panel
WebPanel => CentOS 6 Problems => Topic started by: siskacrew on November 03, 2016, 10:44:14 AM
-
How to disable apache error_log in cwp?
my server storage allways full in 1-2 weeks
-
you can disable error log from /usr/local/apache/conf/httpd.conf
ErrorLog "logs/error_log" add # before it :
#ErrorLog "logs/error_log"
restart apache
-
allready tested in 2 week ago,still not effect bro,my server storage full in 1-2 week becaus error_log
-
Hello,
did you think about fixing the errors instead disable the log?
-
/usr/local/apache/conf/httpd.conf
edit
#ErrorLog "logs/error_log"
ErrorLog /dev/null
-
In order to disable and turn off the Apache logging, just comment out the log lines in the Apache.
-
In order to disable and turn off the Apache logging, just comment out the log lines in the Apache. dissertation writer (https://dissertationwriter.org/)
Hi,
I've been searching the ways to fix the error, but failed - the changes I applied didn't work. I also tried to change http.conf and direct stuff to /dev/null.
Any solutions here? I can't access the tutorial How to Disable and Turn Off Apache (httpd) Access and Error Log on mydigitallife - the page goes blank.
Thanks.
-
Check the logs config in /usr/local/apache/conf.d/vhosts/domain.tld.conf
-
Check the logs config in /usr/local/apache/conf.d/vhosts/domain.tld.conf
Thank you!
But if you have Nginx+Apache then you need to disable logs in the Apache config files:
/usr/local/apache/conf.d/vhosts/domain.tld.conf
/usr/local/apache/conf.d/vhosts/domain.tld.ssl.conf (if you have SSL enabled)
and in the Nginx config files:
/etc/nginx/conf.d/vhosts/domain.tld.conf
/etc/nginx/conf.d/vhosts/domain.tld.ssl.conf (if you have SSL enabled)
Then restart Apache and Nginx
I don't use Varnish but I guess is the same as Nginx.
You should disable logs in the config files:
/etc/varnish/conf.d/vhosts/domain.tld.conf
/etc/varnish/conf.d/vhosts/domain.tld.ssl.conf
Then restart Varnish
-
did you think about fixing the errors instead disable the log?
This is sage advice!
But you can always truncate your error_log to zero bytes:
truncate -s0 /wherever/logs/error_log
Then consider implementing logrotate so as to keep say 4 weekly (compressed) log files that are turned over and won't grow into huge, out-of-control sizes.