Facebook
Twitter
Michal Kurgan
New Pleskian
We have Plesk installation that manages host with big amount of traffic that generates daily access logs in gigabytes of size. While we do not have any serious problems to handle the traffic, daily statistics with webalizer are causing serious io havoc on the server to the point of locking it out.
I managed to find out that the cause is likely DNS cache file updates (>10GB of size). As a temporary solution we are now clearing this file once for a while.
Is there any way to adjust webalizer behaviour? We can setup conf files for domains, however Plesk statistics run of specifying DNS cache file manually (and number of children to process reverse DNS request). These command line option effectively prevent any configuration changes in that respect. Is there a way to change (per domain or globally) webalizer invocation during statistics analysis by Plesk?
Any way to disable webalizer DNS processing would be helpful.
Thanks in advance for your time.
I managed to find out that the cause is likely DNS cache file updates (>10GB of size). As a temporary solution we are now clearing this file once for a while.
Is there any way to adjust webalizer behaviour? We can setup conf files for domains, however Plesk statistics run of specifying DNS cache file manually (and number of children to process reverse DNS request). These command line option effectively prevent any configuration changes in that respect. Is there a way to change (per domain or globally) webalizer invocation during statistics analysis by Plesk?
Any way to disable webalizer DNS processing would be helpful.
Thanks in advance for your time.
