Distributed Systems Administration Utilities V1.0 Release Notes for HP-UX 11i v2 December 2005
1 System Administration Release Notes
These Release Notes describe known issues when using the Distributed Systems Administration Utilities for
the HP-UX 11.23 December 2005 release.
Consolidated Logging
• When using consolidated logging, patch PHCO_32985 should be applied. This is a cumulative patch
for syslogd(1M) and it addresses critical log-forwarding issues. This patch is available from the HP's IT
Resource Center (www.itrc.hp.com) patch database. Without the patches, syslogd does not properly
forward log messages at system startup or after system reboots. Specifically, syslogd needs to be
manually restarted after the network has started before log forwarding functions properly.
• When consolidating package log files in a Serviceguard cluster, it is possible for the first message
written to a new package log file to not get forwarded to the consolidated package log.
The first message written is typically the standard package start line:
########### Node “nodename”: Starting package at date ###########
Subsequent lines are consolidated and cause the consolidated log to be created if it does not already
exist.
• When using the System Log Viewer, which is part of the System Management Home page, the user
can use the Filter tab to specify the number of lines to read from the end of the file. This can improve
performance when the log file is very large. If the user enters a number larger than the number of lines
in the log file, an incorrect number of lines will be displayed. The same is also true when using the
"clog -t lines” command.
• When using the Consolidated Logging Wizard in a Serviceguard cluster and choosing to have the
cluster be a log consolidation server, the wizard creates a Serviceguard package named "clog.” If you
then run the wizard and choose to re-configure the cluster to be a log forwarding client, the package
is not removed. To work around this, before re-configuring the cluster, manually delete the package
using the following commands:
# cmhaltpkg clog
# cmdeleteconf -p clog
Configuration Synchronization
• When using the csync_wizard(1M) to redistribute security keys to all the managed clients, cfservd is
not restarted properly on the remote clients and is still using the previous security keys. This causes cfrun
operations from the master server to fail. cfagent on the managed client will work properly and if cfagent
is being invoked from cron, cfservd will be restarted during the next scheduled synchronization run.
Otherwise, one workaround would be to use "cexec -n managed_clients /sbin/init.d/cfservd restart”
command to restart the client cfservd daemons.
• The csync_wizard(1M) saves the user's responses to each question in an answer file that can be used
when rerunning the wizard. In a Serviceguard environment, when setting cfengine as a highly available
service, an incorrect value is written to the answer file. Change the "master: " line in the file
/var/opt/dsau/cfengine/tmpdir/csync_wizard_input.txt to read "master: csync".
• When running the Configuration Synchronization Wizard in a Serviceguard cluster, make sure your
current directory is not on the filesystem associated with the shared storage for the package. When
creating the Serviceguard package, the filesystem will be forcibly dismounted and Serviceguard will
inadvertently kill the wizard process since it is preventing the filesystem from being dismounted.
• During each use, the Configuration Synchronization Wizard creates backups of the current cfengine
configuration in the directory /var/opt/dsau/cfengine/backups. The top level files in this directory are
the most recent backups. Any previous configurations are saved time-stamped subdirectories named
"v_timestamp”. These backup directories are never deleted and can accumulate if the wizard is used
many times.
Consolidated Logging 5