• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

How to successfully migrate old AWStats?

leonidasj

New Pleskian
Hello guys,

i have to move some customers from an older gentoo machine to a new server running Plesk 10.2 - basically a neat and easy task until now.

Only thing that troubles me are the AWStats. What i did was to copy the access log file from the old server to the new one and place it in /var/www/vhosts/<domain>/statistics/logs as filename "access_log" (after merging the old log with the newer one).

I then ran /usr/local/psa/admin/sbin/statistics --calculate-one --domain-name=<domain> and it took quite a while (the access_log was about 500 MB). The script generated txt files for each month in /var/www/vhosts/leers.com/statistics/webstat that look like this:

awstats012008.<domaine>-http.txt

So far, so good, but when logging in to the statistics, i still did not get any old statistics - only the new ones are selectable through the web interface.

I then ran /usr/share/awstats/tools/buildstatic.sh but to no avail. Still no statistics.

It is odd since i thought once the txt-files are generated, awstats would also generate its static html reports, but no.

So that is, basically, my question to you guys - how can i have those reports generated?

Please help me out if you can!

Thanks a lot!

Best cheers,
Leon
 
Back
Top