How to find System Logs and Statmonitor Data

Finding GemStone system logs

The location of GemStone system logs is highly configurable. For more information, see System Administration Guide, Finding Log Files.

The GemStone gslist utility lists the running Stone and Netldi processes on that node.

Executing gslist prints lines that include, for example:
exists 3.7.5 lalmarod Mar 03 15:10 Stone gs64stone
exists 3.7.5 lalmarod Mar 03 15:10 Netldi gs64ldi

This tell you that the name of the stone is gs64stone and the name of the Netldi is gs64ldi.

To get the path to the stone log, use
os> gslist -x <stonename>

for example,
os> gslist -x gs64stone

the resulting report includes the path to the stone log. Look for a line such as:
logfile= /lark1/users/lalmarod/gemstone3.7.5/data/gs64stone.log

The other system log files, including the reclaim and admin gem logs, are normally located in the same directory as the stone log.

Finding Statmonitor data files

statmonitor is a GemStone utility that can be run to monitor a running GemStone system. It is strongly recommended to run statmonitor on production applications, to help diagnose problems such as repository performance or growth. The statmonitor executable is highly configurable; for more information, see System Administration Guide, statmonitor.

When statmonitor is started, it will write to a data file either in the directory from which it was started, or to specific path and file/names that are specified on the command line. The filename, by convention, start with statmon and end with .out, .out.gz or .out.lz4.

To find where these files are written, first determine what statmonitor executables are running, using ps.

os> ps -ef | grep statmonitor

for example:
lalmarod 2760958 2759601 0 12:44 pts/1 00:00:00 statmonitor gs64stone
lalmarod 2761122 2759601 0 12:47 pts/1 00:00:00 statmonitor -f /lark1/users/lalmarod/logs/statmon.test gs64stone
lalmarod 2761138 2759601 0 12:47 pts/1 00:00:00 grep -s statmonitor

If a filename has been specified on the command line, this will be displayed; note that this may be a pattern, so the actual file name may be different. In the example above, the actual file name will be statmon.test.out, or statmon.test-1.out if the file previously existed.

Otherwise, statmonitor will be writing files to the statmonitor executable’s working directory.
You can find this using pwdx on the pid that was reported by ps -ef. For example,

pwdx 2760958
2760958: /lark1/users/lalmarod/gemstone3.7.5/data

The statmonitor files are being written in this directory, using a default name.