Log Files
From UniCluster
Configuring Log Output
The main node in the UniCluster Express cluster runs a JSR168-compliant hosting environment, called a container. The container runs the WSRF-compliant web services, like GRAM. To log container and service activities, the container writes a container.log file, found in the UniCluster Express installation directory on the main node.
The container.log file may be configured to log additional information for debugging or troubleshooting purposes. The level of logging in container.log is controlled by parameters in the container.log4j.properties file, located in the UniCluster Express installation directory.
For example, to add WS-GRAM debugging information to the log file, open the container.log4j.properties file in a text editor and add the line:
log4j.category.org.globus.exec=DEBUG
Both the service and Java client API code contain special debugging statements which output certain timing data to help in determining performance bottlenecks. To turn on service timings logging, add the following lines to the container-log4j.properties file:
log4j.category.org.globus.exec.service.factory.ManagedJobFactoryService.performance=DEBUG log4j.category.org.globus.exec.service.exec.ManagedExecutableJobResource.performance=DEBUG log4j.category.org.globus.exec.service.exec.StateMachine.performance=DEBUG
Back to Administrative How Tos.
