You can use logs and trace to monitor and troubleshoot your environment. Logs are in different locations depending on your configuration. You might need to provide trace for a server when you work with IBM® support.
With stand-alone catalog and container servers, you set the location of logs and any trace specification. The catalog server logs are in the location where you ran the start server command.
Setting the log location for container servers
workingDirectory=<directory> traceSpec= systemStreamToFileEnabled=trueThe workingDirectory property is the root directory for the logs and optional trace file. WebSphere eXtreme Scale creates a directory with the name of the container server with a SystemOut.log file, a SystemErr.log file, and a trace file if trace was enabled with the traceSpec option. To use a properties file during container startup, use the -serverProps option and provide the server properties file location.
Common information messages to look for in the SystemOut.log file are start confirmation messages. For more information about a specific message, see Messages.
startOgServer.sh catalogServer -traceSpec ObjectGridPlacement=all=enabled -traceFile /home/user1/logs/trace.logIf you start the catalog service in the <eXtremeScale_home>/bin directory, the logs and trace files will be in a logs/<catalog_service_name> directory in the bin directory. See Starting the catalog service process in a stand-alone environment for more details on starting a catalog service.
startOgServer.sh c0 -objectGridFile ../xml/myObjectGrid.xml -deploymentPolicyFile ../xml/myDepPolicy.xml -catalogServiceEndpoints server1.rchland.ibm.com:2809 -traceSpec ObjectGridPlacement=all=enabled -traceFile /home/user1/logs/trace.logIf you start the server in the <eXtremeScale_home>/bin directory, the logs and trace files are in the logs/<server_name> directories in the bin directory
See Starting container processes for more information.
ObjectGridManager manager = ObjectGridManagerFactory.getObjectGridManager(); ... manager.setTraceEnabled(true); manager.setTraceFileName("logs/myClient.log"); manager.setTraceSpecification("ObjectGridReplication=all=enabled");
<eXtremeScale_home>/bin>xsadmin.bat -setTraceSpec "ObjectGridReplication=all=enabled"You can also disable trace by setting the trace specification to *=all=disabled. See Using the xsAdmin sample utility for more information.
server2_exception.log server2_20802080_07.03.05_10.52.18_0.txt