Article ID: 4633, created on Apr 1, 2008, last review on Dec 4, 2015

  • Applies to:
  • Operations Automation


An AWStats profile needs to be updated and using the bulk-update script (awstats_updater.cmd) is not desired since it is a time-consuming process or due to performance-related issues.

Using awstats_updater.cmd is the recommended method. If you do not have reason to believe it will cause significant performance issues, use that method.


Before updating an AWStats profile, you should merge the uploaded logs to one file named awstats.log and reset the last update timestamp for a profile on the AWStats server.


  • The instructions below assume that AWStats is installed in the default folder C:\CustomerData\AWStats\. Use the correct folder if AWStats is installed into a different location.

  • The <profile_id> parameter in the following commands is the AWStats profile ID, which can be found in the Parallels Operations Automation (POA) Customer Control Panel at _Hosting > Configuration & Administration > Statistics & Analysis > AWStats Web Statistics.

1.To merge the log files, run the following command on the AWStats server:

C:\Perl\bin\perl.exe C:\CustomerData\AWStats\tools\ C:\CustomerData\AWStats\statdata\profile(profile\_id)\awstats.log C:\CustomerData\AWStats\statdata\profile(profile\_id)\incoming\_(file1)_.log C:\CustomerData\AWStats\statdata\profile(profile\_id)\incoming\_(file2)_.log C:\CustomerData\AWStats\statdata\profile(profile\_id)\incoming\_(fileN)_.log 2>&1 1>C:\CustomerData\AWStats\statdata\profile(profile\_id)\awstats.log.tmp

(Where <file1-N>.log are the original log files.)

NOTE: Log files are being uploaded into the incoming folder in the AWStats profile by the logparser POA service. If there are no files in the incoming folder for an AWStats profile for a long time, you should make sure that the logs are being written and troubleshoot logparser on the coresponding IIS host.

2.After the logs are merged, rename the log file:

move "C:\CustomerData\AWStats\statdata\profile<profile_id>\awstats.log.tmp" "C:\CustomerData\AWStats\statdata\profile<profile_id>\awstats.log"
  1. To reset the timestamp, open the C:\CustomerData\AWStats\ file using any text editor and remove the string starting with <profile_id>:, if any.

  2. To update the statistics for a particular AWStats profile, use the following command:

    C:\Perl\bin\perl.exe C:\CustomerData\AWStats\wwwroot\cgi-bin\ -update -config=

Alternative instructions:

  1. Access the webserver node which contains the customer's webspace,
  2. Locate the Logparser's config.xml and checkpoints.xml:

    Linux : /usr/local/pem/etc/logparser/config.xml, /usr/local/pem/etc/logparser/checkpoints.xml

    Windows: C:\Program Files (x86)\SWsoft\PEM\etc\checkpoints.xml, C:\Program Files (x86)\SWsoft\PEM\etc\config.xml

  3. Through config.xml, it is necessary to connect the Webspace ID with the necessary log. This can be done by searching through the file for the webspace ID until action "1024" is found. There, the log ID can be located.

  4. Go to the webspace directory, then the logs directory and merge all the files together starting from beginning.

    For Linux, this can be done using commands like:

    # for fn in `seq 0  89` ; do zcat access_log.processed.$[90-fn].gz >> access_log.processed.full ; echo $[90-fn] ; done
    # cat access_log.processed.full access_log.processed access_log >
    # cp -a access_log
    # cp -a access_log.processed
  5. In checkpoints.xml, locate the log ID obtained from step three and set the checkpoints (in Unix time) to 1. This will effectively tell the logparser to process the logs and upload them during the next run.

  6. Run logparser:

    Linux: Typically, you would use:

    # nice -n 16 /usr/local/pem/bin/logparser /usr/local/pem/etc/logparser/config.xml /usr/local/pem/etc/logparser/checkpoints.xml /usr/local/pem/etc/logparser/traffic /usr/local/pem/etc/logparser/updates

    The following command can be obtained through your crontab files.

    Windows: Run the scheduled logparser task through control panel

    This will upload the necessary files to the Awstats webserver.

  7. Use to process the uploaded logs:

    "C:\Perl64\bin\perl.exe" "C:\CustomerData\AWStats/tools/"  "C:\CustomerData\AWStats/statdata/profile<profile_id>/awstats.log" "C:\CustomerData\AWStats/statdata/profile<profile_id>/incoming/384843659.log" 2>&1 1>"C:\CustomerData\AWStats/statdata/profile<profile_id>/incoming/000000001392599396.log.tmp"
  8. Replace awstats.log with the temporary log,

    copy "C:\CustomerData\AWStats\statdata\profile<profile_id>\incoming\000000001392599396.log.tmp" "C:\CustomerData\AWStats\statdata\profile<profile_id>\awstats.log"
  9. Issue an update for awstats.

    "C:\Perl64\bin\perl.exe" "C:\CustomerData\AWStats/wwwroot/cgi-bin/" -update -config=<profile_id>

Search Words

AWStats not running

awstats stopped calculating

Updateing web awstats statistics manually

awstats web statistics don't get updated

iis access logs

awstats isn't calculated


AWStats not updated

awstats don't update


Web Statistics Malfunction


awstats not working

awstats issue

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF