Hi Got a customer running on an ISPConfig server who has a large amount of traffic constantly. This of course causes a huge log buildup that will take time to process. Is there any chance that cron_daily.sh will be threaded in the future or can handle the traffic differently in smaller chunks? I'll try with a "nice" value to the crontab but I would appreciate some input on methods to handle this and maintain ISPconfigs functions.
The apache traffic accounting and log handling is not done by cron_daily.sh. The traffic is accounted by vlogger and the log splitting and handling is also done by vlogger, vlogger is a process run by apache and not a cronjob. The only thing that cron_daily starts is the webalizer or awstats scripts. So I guess that your load is produced by either awstats or webalizer and not cron_daily.
Is there a safe and good method to disable apache logging for a site in ispconfig 3? 10GB daily log files for this apache site isnt good. + 15min processing time that eats user experience at night.
Looging is handled by one central perl script (vlogger) for all sites, so you can only disable logging for all sites by disabling the log line in the apache ispconfig.conf file but not for a single site.
Do I just need to comment out "CustomLog "| /usr/local/ispconfig/server/scripts/vlogger -s access.log -t \"%Y%m%d-access.log\" -d \"/etc/vlogger-dbi.conf\" /var/log/ispconfig/httpd" combined_ispconfig" ? Thanks once more
