SiteVision Onlinehelp

Logging

A SiteVision server uses Log4j for all logging purposes. You will find 5 types of logs in a SiteVision installation that might be useful:

All logs can be found in the log directory of your SiteVision installation. On Windows this directory typically is C:\sitevision\data\log and on Linux /var/log/sitevision/

A Tip! If the system account is active and you have access to it, you can use a web browser to read the logs. Go to <domain name>/editor/admin and click the Data link (in the upper Admin tools section) then click the log link in the directory listing (in the main frame, below Admin tools):
Below you will find information about the available logs and their content.

Application logging

SiteVision logs application events for instance user logins, and creation and publication of pages, to an application log. You can find these logs in the application directory. The current log is called application.log, it uses a daily rolling scheme.

Log categories


The events are logged with the following log categories:
  • application.lifecycle = created/removed an object
  • application.publish = published a page
  • application.unpublish = unpublished a page
  • application.authentication = user login or logout
All events for all websites that resides on the SiteVision server will be written to the same log file.

Server logging

SiteVision logs server events that are necessary to find and track problems any website on the SiteVision server might have. You can find these logs in the system directory. The current log is called server.log, and it uses a daily rolling scheme.

All events for all websites that resides on the SiteVision server will be written to the same log file.

The server logging can use different log granularity levels (DEBUG, INFO, WARNING, ERROR, FATAL). Each level logs all events for it's level and all levels above. If the level is set to DEBUG, SiteVision will do extensive logging (i.e. large log files) and if the level is set to FATAL SiteVision will do minimal logging (since only FATAL log events will be written, the server log file will be minimal).

What log level that should be used is configurable through the log4j.xml file in your custom/conf directory. On Windows this will typically be C:\sitevision\custom\conf and on Linux it will typically be /opt/sitevision/custom/conf

A Tip! If the system account is active and you have access to it, you can use a web browser to see the server log output live (there might be some seconds buffering delay). For performance reasons (the overhead of repeatedly sending log data as a response) the connection will be lost after an hour if you haven't closed your browser within this timespan.

Go to <domain name>/editor/admin and click the Log link (in the upper Admin tools section):

Wrapper logging

In the wrapper log you find essentially the same information as in the server log, but there are also additional Java/JVM information. I.e. if you find a problem in the server log, you might find additional information about the problem in the wrapper log.

The wrapper log uses a size-based rolling logging scheme. There are at most 10 wrapper logs (wrapper.log, wrapper-1.log ... wrapper-9.log) and the maximum size of each log is 20 MB. Previous wrapper logs will be overwritten (e.g. if you find a problem in a 15 day old server log, the wrapper log that also logged the problem might have been overwritten).

Wrapper logs resides in the same directory as the server logs.

Access logging

All requests to a website are logged. If it is a known search engine spider, the logging can be found in the spider log, else it will be found in the regular access log.

The access logs are used by SiteVision to generate statistics about page/image/file downloads. The logs uses the format 'Common Log Format' (CLF) so that they can be utilized by most log analytical programs. The Apache specification for the CLF can be found here.

Each website will have a separate access logging directory and the name of this directory will be the same as the id of the website. Here is an example:

1. The website 'Demowebb' has id '2.4fd02c4f11865610f9580000':

2. The access logs for 'Demowebb' can be found in the '2.4fd02c4f11865610f9580000' directory:
3. The access logs for known search engine spiders for 'Demowebb' will be found in the '2.4fd02c4f11865610f9580000_spider' directory:

Mail logging

Each mail sent from the SiteVision server is logged in a separate text file (the file extension is .dat though) in the mail directory.

Note! Mail and their content are also logged in the server log if the server log level is set to INFO or DEBUG.

Generating stack traces

If the system account is enabled and you have access to it, you can generate stack traces using a web browser. Go to <domain name>/editor/admin and click "Stacktraces". This will generate a stack trace for each running thread and is useful when troubleshooting a server or portlet that is running slow.

help-cluster-2.sitevision.net