Distributed Systems Administration Utilities User's Guide, Linux, March 2009

5. Validate that log forwarding is working properly. If consolidating the cluster’s local syslogs,
use “logger <test message>” and make sure this message is in the consolidated
syslog.log. If you are not consolidating local logs, use the logger command from a log
forwarding client.
Note that logger messages are first sent to the local syslogd, which forwards them to
syslog-ng. By default, syslogd suppresses duplicate messages. If you issue multiple
logger test messages, make sure each is unique. The logger message should appear in
the consolidated syslog.log located in the directory specified in the /etc/
syslog-ng.conf.server file on Red Hat or /etc/syslog-ng/
syslog-ng.conf.server file on SLES. For the examples above, that directory would be
/clog/syslog/syslog.log.
If consolidating package logs for this cluster, any package actions that generate package log
information, such as a package failover, should cause a consolidated package log to appear
in /clog/packages.
3.3.2.2.3 Using VxVM Instead of LVM
The default clog package script template assumes that you are using LVM based storage. To use
VxVM storage instead, you must edit the clog package script, $SGCONF/clog/clog. Comment
out the LVM Volume Group line “VG[0]=“xxx””, uncomment the line “VXVM_DG[0]=”, and
enter the VxVM Disk Group.
3.3.2.3 Manually Configuring Log Forwarding Clients
You can configure either a standalone system or a Serviceguard cluster as log forwarding clients.
You can also manually configure Serviceguard package logs as if they were syslog data. For
each case, you set up both syslogd and syslog-ng.
68 Consolidated Logging