Most perfSONAR related services keep log files under the directory /var/log/perfsonar. Some external tools store them in other areas under /var/log/ or elsewhere. There are many log files on the system but some of the most important ones (organized by the service that populates them) can be found below:

Service

Log File(s)

When to Use

pScheduler

/var/log/pscheduler/pscheduler.log

Contains logs related to the scheduling, running, and storage of measurements. This is often a good starting point if you are trying to debug a missing or failed measurement.

If your measurement archive is not running or your graphs are not returning data you may want to look in one of these logs. esmond.log has information from the archive itself (e.g. improperly formatted requests). The HTTPD error log has information such as if esmond was able to connect to it’s underlying databases. Speaking of databases, esmond connects to both Cassandra and PostgreSQL so it may be worth checking those logs as well.

perfSONAR Mesh Configuration Agent

/var/log/perfsonar/meshconfig-agent.log

In addition to the pScheduler logs, this is a good place to debug information regarding missing measurements. The MeshConfig agent handles the submission of tasks to pScheduler, so failure to do so is a common cause of missing tests.

BWCTL and OWAMP

/var/log/perfsonar/owamp_bwctl.log

Every BWCTL and OWAMP test (both on the client and server side) is logged in this file. It should be used when a BWCTL or OWAMP test is not completing. It contains information about denied or failed tests. It may also contain information when an owamp-server or bwctl-server process crashes unexpectedly. Please note that BWCTL is deprecated as of version 4.0, so you may be better served looking at the pScheduler logs.

perfSONAR Configuration Daemon

/var/log/perfsonar/configdaemon.log

If you are unable to save changes to the configuration made through the web interface, this is a good place to look.

perfSONAR Lookup Service Cache Daemon

/var/log/perfsonar/lscachedaemon.log

If you get a message saying that your communities or lookup service cache are out of date, this log file may contain more information.

perfSONAR Lookup Service Registration Daemon

/var/log/perfsonar/lsregistrationdaemon.log

Look here if your toolkit web page says that your host is not registered with the lookup service or you cannot find your host in the global services directory.

The table above is not an exhaustive list of every log file on the system. It’s intended to point at some important log files that are commonly used to debug issues with perfSONAR tools. Depending on the exact issue you may need to view other log files on the system to diagnose a problem.

Users with administrative rights may look at log files under /var/log/perfsonar/ through the web interface. This obviously does not include all logs on the system, but does allow easy access for some of the major perfSONAR logs. To access this interface perform the following steps:

From your toolkit main web interface, look at the right side of Services section, under SERVICE LOGS. This place provides links to web interface access to selected toolkit logs.

Login using the web administrator username and password.

See also

See Managing Users for more details on creating a web administrator account.

This could likely be derived from the a combination pScheduler and OWAMP logs, but the best place to collect is information is likely not from the logs at all. See Viewing the Schedule for information on viewing tests initiated both by your host and others.