Log Service Installation Instructions
EPiServer CMS 4.62
Document creation date:
Document last saved:
The purpose of the Log Service is to centrally handle log messages in one place for the entire Web site. This document describes how to install the Log Service and includes information on how to troubleshoot the Log Service.
Table of Contents
- System Requirements
- EPiServer Modules
Installing Log Service
- Installation with EPiServer CMS Manager
- Manual Installation
From EPiServer CMS 4.50, the Log Service is a part of the base installation. The purpose of the Log Service is to centrally handle log messages in one place for the entire Web site.
There are three logical parts in the Log Service
- Web server or an application that generates the log messages
- Log Service to collect the log messages
- Analyzers to handle and present the log messages.
For the full installation with the base example analyzers, the Log Service has the same requirements as EPiServer CMS. Refer to the document "EPiServer CMS Installation Instructions" for further information.
The Log Service in the base form does not require a database, Web service or an EPiServer CMS installation.
Log Service also requires:
- EPiServer CMS 4.50 or later. This is needed to present the analyzer values.
- EPiServer CMS Manager. This is used for a quick and easy installation.
Log Service can be installed in one of two ways, either with EPiServer CMS Manager or manually. Instructions for how to install in both ways are described in this chapter.
Follow the instructions below to install the Log Service with EPiServer CMS Manager.
1. Select the Capabilities node under the Web site for which you want to generate log messages.
2. In the Logging/Statistics group box, click Enable.
Note The historical data saved in the database is based upon the web.config value EPsSiteName. If this value is changed, historic information cannot be presented on the Web site. (Refer to the technical note "web.config Settings" for further information about the settings in web.config.)
Configure the Log Service to Use a Database
To configure the Log Service with a database, the connection string in the configuration file (%programFiles%/EPiServer.LogService/EPiServer.LogService.exe.config) must be changed. Change the value for the parameter connectionString to a connection string to an EPiServer database.
<add type="EPiServer.Implementation.SqlObjectStore, EPiServer.Implementation" id="default">
<parameter name="connectionString" value="Data Source=(local);Database=dbEPiServerDemo450RC3;User Id=usrEPiServerDemo450RC3;Password=password;Network Library=DBMSSOCN;" />
<add type="EPiServer.Implementation.OracleObjectStore, EPiServer.Implementation" id="default">
<parameter name="connectionString" value="Data Source=<TNS name>;User Id=<user>;Password=<password>" />
If an older installation of the Log Service exists, uninstall this service according to the "Removing Log Service" chapter.
Follow the instructions below to install the Log Service manually.
1. Run the program installUtil.exe located in the .NET framework current version directory, e.g. "c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\InstallUtil.exe" with the Log Service binary as argument.
2. Rename the default configuration file named EPiServer.LogService.exe.config.default (located in the installation directory under %programFiles%) to EPiServer.LogService.exe.config.
3. Configure the LogService database, see Configure the Log Service to Use a Database
4. Start the service at the command prompt with the command
net start EPiServer.LogService.
5. Enable statisics logging for the Web site by renaming/copying EPiServerLog.config.Default to EPiServerLog.config from an EPiServer sample site Web root.
Logging in EPiServer is based on the log4net product and must have the following properties:
- One appender with the following values
- type="EPiServer.Diagnostics.EPiServerUdpAppender, EPiServer"
- remoteAddress=<IP address to the log service>
- remotePort=<port defined for the log service, must be the same value as the udpClientPort property in the log service configuration file>
- encoding=Unicode (automatically added by the EPiServerUDPAppender)
- a layout that generates log messages on the form %d\t<siteid>\t%m
- One logger on DEBUG level for the class EPiServer.DataAccess.PageSaveDB – to generate messages when a page is published.
- One logger on INFO level for the class EPiServer.Util.PixelImg – to generate messages for the statistics.
<EPiServer:LogGenerator runat="server" ID="PixelImg" />
In the sample project this component is implemented in the default framework, located in the file Templates\FrameWork\DefaultFrameWork.ascx
Only one log service is configured for all Web servers on a Web farm. For the sample analyzers, each Web server sends log messages to the log service over UDP and the log service publishes its results on a TCP/SOAP Web service that can be connected for all Web servers.
1. The Web servers are configured to send log messages to the log service in the EPiServerLog.config file located in the Web root for every Web server.
Example for sending log messages to a remote log service:
<appender name="UdpAppender" type="EPiServer.Diagnostics.EPiServerUdpAppender, EPiServer">
<remoteAddress value="192.168.150.237" />
<remotePort value="7070" />
2. The example analyzers are configured to publish their information on a TCP/SOAP Web service. To publish this to a remote host, add the via attribute to the configuration in EPiServer.LogService.exe.config located in your EPiServer.LogService directory (normally %programFiles%\EPiServer.LogService)
Example configuration to publish the sample analyzer Time Span Analyzer over TCP/SOAP remote:
<view type="EPiServer.Log.Analyzer.TimeSpanAnalyzerView, EPiServer.Log.Analyzers"
3. Change the SOAP proxy so that it connects to the remote server. In the example code before EPiServer CMS 4.60, this is implemented as a web.config setting EPsLogServiceHost. In your own analyzers you must change it yourself by adding a via attribute to the endpoint.
Example to add a via attribute to the time span analyzer's endpoint:
TimeSpanAnalyzerView client =new TimeSpanAnalyzerView();
Uri address = new Uri("soap.tcp://localhost/TimeSpanAnalyzerView");
Uri via = new Uri("soap.tcp://" + EPiServer.Global.EPConfig["EPsLogServiceHost"] + "/TimeSpanAnalyzerView");
client.Destination = new Microsoft.Web.Services2.Addressing.EndpointReference(address, via);
Follow the instructions below to remove the Log Service.
1. Stop the service at the command prompt with the command net stop EPiServer.LogService.
2. Run the program installUtil.exe located in the .NET framework current version directory (e.g. c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\InstallUtil.exe ) with the arguments /u for uninstall and the binary for the Log Service
c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\InstallUtil.exe /u c:\inetpub\wwwroot\bin\EPiServer.LogService.exe
3. Remove the directory %ProgramFiles%\EPiServer.LogService.
4. Remove the configuration file for logging on the Web server EPiServerLog.Config, which exists in the Web server root directory.
- To remove all logging sent to the Log Service, remove the appender that sends UDP messages (default is EPiServerUDPAppender).
- To remove the logging for published pages, remove the logger for the class EPiServer.DataAccess.PageSaveDB.
- To remove the logging for statistics, remove the logger for the class EPiServer.Util.PixelImg.
The first page of the sample site reads “The log service could not be connected.”
The Statistics tab in Edit mode reads “Cannot connect to the log service.”
Cause: The Log Service cannot be connected by the Web service over TCP/SOAP.
Solution: Verify that the Log Service is started according to the "Validate that the Log Service is Functional" chapter.
The statistical values are not changing.
Cause: No log messages are generated/come over the UDP channel.
Solution: See the "Check the Log Configuration on the Web Server" chapter.
The Statistics tab in Edit mode reads “The log service is not configured with a database. Saved history will not be shown.”
Cause: The Log Service is not able to save data into the database.
Solution: See the "Check if the Log Service is Configured" chapter.
Check if the Log Service is Installed
The installation directory (%Program files%/EPiServer.LogService) should contain the executables and the configuration files for the Log Service. If it is empty, install the service according to the "Manual Installation" chapter.
Check the Log Configuration on the Web Server
Verify that the configuration file EPiServer.Config exists in the Web server's root directory. In the sample project the file is named EPiServerLog.Config.Default so it not will start logging automatically.
The configuration file must contain
- A UDPappender whose remoteAdress property is the Log Service IP address. remotePort must be set to the same value as the Log Service configuration property udpClientPort and encoding must be set to Unicode.
- A logger called TEPiServer.DataAccess.PageSaveDBT on DEBUG level, if the component for showing last published pages is to be used.
- A logger called EPiServer.Util.PixelImg on INFO level, if you want statistics generation with transparent gif to work
- A root logger, if you want a centralized logging for the whole Web site.
The configuration file for the Log Service must be called EPiServer.LogService.exe.config and be located in the Log Service home directory (%Program files%\EPiServer.LogService.exe.config).
The Log Service is, by default, not started automatically when EPiServer is installed the file is called EPiServer.LogService.exe.config.Default.
Important configuration for the Log Service:
UDP port for log messages
<add key="udpClientPort" value="7070" />
udpClientPort has to be the same value as the Web service log configuration remotePort for the UDPappender located in the file EPiServer.Log.Config.
Check if the Logging is Done with Transparent GIF
If there is a reference to the transparent .gif file, there must also be a HTML tag on the page to be included in the statistics. This page should start with:
<img width='1' height='1' alt=''...
This tag generates a transparent .gif file that sends log messages to the Log Service if it is present on the Web site.
The log message that is sent by the transparent .gif has the following looks like this:
2005-04-12 10:52:05,444 |mySite|Page|...
Log4net will not write to the log file if EPiServerLog.Config is corrupt. Test if the configuration is correct by creating a file appender that writes log messages directly to a file and changes the log level for the root logger to DEBUG. If no file is created, the EPiServerLog.Config is corrupt and has to be rewritten.
In the installation directory for the Log Service, the log server's own log file is located in %Program files%\Logs\. If this file is not present, the initial error message is written to the Windows Event Handler on the local machine.
The Log Service log should look like below if the Log Service is started.
Starting Udp Server, listen to port 7070
Start up the Log Service in DEBUG Mode
- Open a command prompt and navigate to the root directory of the log service, normally %PROGRAMFILES%\EPiServer.LogService\
- Shout down the normal log service by entering the following command
net stop EPiServer.LogService
- Start up EPiServer.LogService in DEBUG mode by entering the following command
- This start ups the log service and outputs debug messages to the console in DEBUG mode.
- To quit the log service, press ‘q’ followed by ENTER.