7 event logging overview, 1 understanding the event logging structure, 2 the syslog-ng.conf rules file – HP Insight Control Software for Linux User Manual

Page 192

Advertising
background image

# cd /opt/hp/icelx/config/uninstall
# ./uninstall.sh

5.

Remove the following Insight Control for Linux monitoring directories. If you have any files in
these directories that you want to preserve, make sure you save a copy of the files before you
remove them.

# rm -Rf /opt/hptc
# rm -Rf /hptc_cluster
# rm -Rf /var/hptc
# rm -Rf /opt/repository/boot/pxelinux.cfg

NOTE:

System configuration files that Insight Control for Linux modifies (for example, /etc/

dhcpd.conf

, /etc/rsyncd.conf, and so on) are not removed during the uninstall process.

6.

Remove the following HP SIM directories. If you have any files in these directories that you
want to preserve, make sure you save a copy of the files before you remove them.

# rm -Rf /var/opt/hpsmdb
# rm -Rf /var/opt/mx
# rm -Rf /etc/opt/mx
# rm -Rf /opt/hpsmdb

7.

Verify that the HP SIM daemons are no longer running:

# ps -ef | grep mx

If any of the HP SIM daemons are running, record the process ID (PID) and use the PID to
terminate the process. In the following example, replace PID with the process ID of the daemon
(for example, kill -9 1234):

# kill -9 PID

8.

Reboot the CMS:

# reboot

23.6 Determining the installed Insight Control for Linux version

To determine the version of Insight Control for Linux that is installed on the CMS, look in the following
file:

# /opt/hp/icelx/etc/icelx-release

23.7 Event logging overview

This section describes how Insight Control for Linux uses the syslog and syslogng_forward
services to log managed system events and how these events are arranged according to the
syslog-ng.conf

rules file.

23.7.1 Understanding the event logging structure

Insight Control for Linux uses syslog-ng to log events. Each managed system is configured to
forward its syslog events to syslog-ng running on the CMS.

Each managed system runs the syslogd daemon and passes events of priority warning or higher
to the CMS.

The CMS runs the syslogng_forward service and writes the events it receives from its managed
systems to the /hptc_cluster/adm/logs/consolidated.log file.

23.7.2 The syslog-ng.conf rules file

The syslog-ng.conf rules file defines the order of importance by which the log files are arranged.

The /opt/hptc/syslog-ng/etc/syslog-ng/syslog-ng.conf file defines a series of rules
for the syslogng_forward service on how to handle messages from its clients. The
syslog-ng.conf

file contains five types of rules:

192 Miscellaneous topics

Advertising