Plesk web statistics not updating Dirty chat rooms no signup
This explains why there aren’t any provisions for rotating individual access log files in the log rotate configs (found in /usr/local/psa/etc/logrotate.d//logs/.This mechanism allows end users to see the logs for their domain(s) and manage them, but prevents Apache from going disordered if a user deletes the /logs directory in their web space, which Apache will be unable to recreate, as the directory is owned by root:root.On Linux, the following cron job takes care of the task: Look for it in /etc/cron.daily/50plesk-daily.On Windows, it is the task with the details of “Daily script task” in the Task Scheduler. For every domain, the utility does the following, in turn: 1) Calculates disk usage and writes it to the Plesk database.
It will be written to the web statistics log, and so on.The duty of the statistics tool is not only to monitor the informative, statistics calculation, but also automatically suspend the subscriptions that exceed the configured resource usage limits.The statistics calculation is controlled by the statistics utility, which is being run by a script scheduled to run on a daily basis.5) Writes the obtained traffic data to the Plesk database (Domains Traffic and Clients Traffic tables).6) Calls the web statistics engine (either Webalizer or AWstats, depending on the domain’s settings).
Search for plesk web statistics not updating:
Log rotation on Windows is implemented by the standard IIS means, so there’s no dependency on the utility running. Unfortunately, in the unsound reality the statistics engine requires a fair large amount of memory to operate, and is a juicy target for the OOMkiller.