Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a System
Using Distributed Systems Administration Utilities
Chapter 3 229
If consolidating this cluster’s package logs, add:
CLOG_PACKAGE=1
otherwise, add:
CLOG_PACKAGE=0
Step 4. All the files edited thus far need to be distributed cluster-wide:
# ccp /etc/syslog-ng.conf.client /etc/
# ccp /etc/rc.config.d/syslog-ng /etc/rc.config.d/
Create the following symbolic link on each cluster member:
# ln -sf /etc/syslog-ng.conf.client /etc/syslog-ng.conf
Step 5. When using TCP with ssh port forwarding, record the ssh port number
you chose above in the /etc/services file. For example, add the line:
clog_ssh 1776/tcp # Consolidated logging with ssh port forwarding
Add this line to the /etc/services file of each cluster member.
Step 6. To consolidate this cluster’s package logs, additional manual steps are
needed on the log consolidation server. Each time a package is created or
deleted on this cluster, these steps need to be done. Refer to
“Consolidating Package Logs on the Log Consolidation Server” on
page 230.
Step 7. Test the configuration by performing the following steps:
a. Run /opt/dsau/sbin/syslog-ng with the -s or --syntax-only
option to verify the syntax of the /etc/syslog-ng.conf file. This
should be a symbolic link to /etc/syslog-ng.conf.client as
described above.
b. Start syslog-ng on all cluster members using
# cexec “/sbin/init.d/syslog-ng start”
c. If consolidating the local syslogs, use “logger <test message> ” and
make sure this message is in the consolidated syslog.log on the log
consolidation server. Note that the logger messages are first sent to
the local syslog which forwards them to syslog-ng. By default, syslogd
suppresses duplicate messages. If you issue multiple logger test
messages, make sure each is unique.