Article ID: 115828, created on Mar 26, 2013, last review on Jul 14, 2016

  • Applies to:
  • Operations Automation

Windows logparser service


The main purpose of the POA Windows logparser service:

  • Calculate customers' websites' traffic usage and report it to POA
  • Upload logs of customers' IIS websites to a dedicated AWStats service for web statistics processing

The logparser service must be installed on every single POA-managed Windows Shared Hosting server as corresponding POA package.

On a Windows server with the logparser service installed POA creates scheduled task with the name pem_logparser to run the service on the specified schedule. The scheduled task executes the 'C:\Program Files (x86)\SWsoft\PEM\logparser.bat' script which in turn executes the 'C:\Program Files (x86)\SWsoft\PEM/bin/logparser.exe' binary that processes customers' websites log files, generates traffic usage statistics and reports it to POA. Also, logparser uploads IIS log files of customers' websites to the AWStats server for further processing.
 
The main configuration files of the logparser service are as follows:
C:\Program Files (x86)\SWsoft\PEM\etc\config.xml
C:\Program Files (x86)\SWsoft\PEM\etc\checkpoints.xml

For every single customer's website POA creates entries in the C:\Program Files (x86)\SWsoft\PEM\etc\config.xml file to process IIS log files located in the logs\W3SVC<ID> folders in a webspace, where <ID> is the ID of a particular IIS website.

Log files for system services such as IIS FTP service, File Manager service and the like are defined in the above mentioned configuration files as well, so they are being processed by the same way as logs of customers' websites.

The checkpoints.xml file is being updated with proper timestamp when every single log file was processed by the logparser service last time.
 
When the logparser.exe binary is invoked by the scheduled task it reads XML configuration files and processes IIS logs in customers' webspaces along with system log files - calculates traffic usage data stored in logs and reports it to POA.

The config.xml file also defines log format for every single IIS log file, this is necessary for logparser to be able to parse log files correctly, e.g.:
<format>%D %m %U %a %H %{User-agent}i %{Referer}i %h %s %z %b</format>
During logs processing the logparser also uploads IIS logs to AWStats server by FTP if a customer created corresponding profile in POA Control Panel for website, parameters of FTP access to AWStats server are defined in the config.xml file like in the example below - IP address, profile ID, user and password:
<options>ftp://10.39.94.66/profile30/incoming aws_f00000169:password</options>
The logparser saves own log in the C:\Program Files (x86)\SWsoft\PEM\logparser.bat.log file on a Windows Shared Hosting server by default, analyze the file to troubleshoot the problems with log parsing and traffic usage collecting in POA.

There is no logparser related resource types in POA, the service is available for all customers with Windows Shared Hosting service subscriptions.


See the main Knowledgebase article #115790 Website Hosting: General information, Best Practices and Troubleshooting for more information.

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF