RHEL5 and xymon client monitoring log files
list Cathy Smith
Folks
With your help, the RHEL5 server is now showing up in the hobbit display correctly. This is the xymon client reporting to a hobbit server. Now I have a question about monitoring log files. I have included below, my localclient.cfg file. I want to check /var/log/messages for anything with the word ERROR. Hobbit displays a white smiley face in the msgs column with the message:
The client did not report any logfile data
I'm running all processes as root, so there shouldn't be any permissions issues.
Can you tell me what I've done wrong in the config file?
Thanks.
Cathy
---
Cathy L. Smith
IT Engineer
Pacific Northwest National Laboratory
Phone: XXX.XXX.XXXX
Fax: XXX.XXX.XXXX
Email: user-332e187d7d6d@xymon.invalid
-----Original Message-----
From: root [mailto:user-14fe4d96760c@xymon.invalid]
Sent: Tuesday, July 27, 2010 7:35 AM
To: Smith, Cathy
Subject: localclient.cfg
# localclient.cfg - configuration file for a LOCAL Hobbit client.
#
# By default, Hobbit clients send raw data to the Hobbit server,
# which in turn converts the data into status messages.
# In that case, THIS FILE IS NOT USED and you should IGNORE it.
#
# The special DEFAULT section can modify the built-in defaults - this must
# be placed at the end of the file.
HOST=foo.pnl.gov
MEMSWAP 70 90
PROC crond
PROC http
PROC sendmail
PROC sshd
PROC syslogd
LOG /var/log/messages ERROR COLOR=red
DEFAULT
# These are the built-in defaults.
UP 1h
LOAD 16.0 30.0
DISK * 95 99
MEMPHYS 100 101
MEMSWAP 50 80
MEMACT 90 97
list Tim McCloskey
Cathy,
Looks like you are running in client local mode. See the difference in the etc/clientlaunch.cfg: CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh --local
Try adding a $HOBBITCLIENTHOME/tmp/logfetch.`hostname`.cfg file, chown to the hobbit user and restart the client. Also, what does the server client-local.cfg look like for this host/OS/class?
(eg. [redhat]
log:/var/log/messages:10240
log:/var/log/kern:10240
ignore MARK
file:/bin/su:md5)
Server Mode.
# The main client task
[client]
ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh
LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
INTERVAL 5m
Client mode
# The main client task
[client]
ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh --local
LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
INTERVAL 5m
#LOG %/var/log/(kern|messages) "%(ext3_journal_start_sb|Detected aborted journal)" COLOR=yellow
Regards,
Tim
▸
From: Smith, Cathy [user-332e187d7d6d@xymon.invalid]
Sent: Tuesday, July 27, 2010 7:45 AM
To: xymon at xymon.com
Subject: [xymon] RHEL5 and xymon client monitoring log files
Folks
With your help, the RHEL5 server is now showing up in the hobbit display correctly. This is the xymon client reporting to a hobbit server. Now I have a question about monitoring log files. I have included below, my localclient.cfg file. I want to check /var/log/messages for anything with the word ERROR. Hobbit displays a white smiley face in the msgs column with the message:
The client did not report any logfile data
I'm running all processes as root, so there shouldn't be any permissions issues.
Can you tell me what I've done wrong in the config file?
Thanks.
Cathy
---
Cathy L. Smith
IT Engineer
Pacific Northwest National Laboratory
Phone: XXX.XXX.XXXX
Fax: XXX.XXX.XXXX
Email: user-332e187d7d6d@xymon.invalid
-----Original Message-----
From: root [mailto:user-14fe4d96760c@xymon.invalid]
Sent: Tuesday, July 27, 2010 7:35 AM
To: Smith, Cathy
Subject: localclient.cfg
# localclient.cfg - configuration file for a LOCAL Hobbit client.
#
# By default, Hobbit clients send raw data to the Hobbit server,
# which in turn converts the data into status messages.
# In that case, THIS FILE IS NOT USED and you should IGNORE it.
#
# The special DEFAULT section can modify the built-in defaults - this must
# be placed at the end of the file.
HOST=foo.pnl.gov
MEMSWAP 70 90
PROC crond
PROC http
PROC sendmail
PROC sshd
PROC syslogd
LOG /var/log/messages ERROR COLOR=red
DEFAULT
# These are the built-in defaults.
UP 1h
LOAD 16.0 30.0
DISK * 95 99
MEMPHYS 100 101
MEMSWAP 50 80
MEMACT 90 97
list Tim McCloskey
Minor clarification, add the logfetch.hostname.cfg file to the client tmp dir. Also, if the client does not report OS info to the server (check the info tab, look at the OS field) then you may want to define the host in the server client-local.cfg file. If the environment permits it I find storing / configuring stuff and parsing the data on the server works better, for me. Example below, cp the redhat stanza and change the name to the hostname. It would be better to not 'run everything as root' or make to many customizations if avoidable. I'm sure others on the list can shed more light on the topic.
▸
Try adding a $HOBBITCLIENTHOME/tmp/logfetch.`hostname`.cfg file, chown to the hobbit user and restart the client. Also, what does the server client-local.cfg look like for this host/OS/class?
(eg. [redhat]
log:/var/log/messages:10240
log:/var/log/kern:10240
ignore MARK
file:/bin/su:md5)
list Tim McCloskey
Clouseau said, 'and another thing....' -bash-3.00$ cat logfetch.yourhostnamehere.cfg log:/var/log/messages:10240 log:/var/log/kern:10240 file:/bin/su:md5 If you really are set on using $HOBBITCLIENTHOME/bin/hobbitclient.sh --local then you will need the contents above inside of the logfetch.$hostname.cfg file. Seems really a real cludge, but it works.
▸
From: Tim McCloskey
Sent: Tuesday, July 27, 2010 9:19 AM
To: xymon at xymon.com
Subject: RE: RHEL5 and xymon client monitoring log files
Cathy,
Looks like you are running in client local mode. See the difference in the etc/clientlaunch.cfg: CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh --local
Try adding a $HOBBITCLIENTHOME/tmp/logfetch.`hostname`.cfg file, chown to the hobbit user and restart the client. Also, what does the server client-local.cfg look like for this host/OS/class?
(eg. [redhat]
log:/var/log/messages:10240
log:/var/log/kern:10240
ignore MARK
file:/bin/su:md5)
Server Mode.
# The main client task
[client]
ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh
LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
INTERVAL 5m
Client mode
# The main client task
[client]
ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
CMD $HOBBITCLIENTHOME/bin/hobbitclient.sh --local
LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
INTERVAL 5m
#LOG %/var/log/(kern|messages) "%(ext3_journal_start_sb|Detected aborted journal)" COLOR=yellow
Regards,
Tim
From: Smith, Cathy [user-332e187d7d6d@xymon.invalid]
Sent: Tuesday, July 27, 2010 7:45 AM
To: xymon at xymon.com
Subject: [xymon] RHEL5 and xymon client monitoring log files
Folks
With your help, the RHEL5 server is now showing up in the hobbit display correctly. This is the xymon client reporting to a hobbit server. Now I have a question about monitoring log files. I have included below, my localclient.cfg file. I want to check /var/log/messages for anything with the word ERROR. Hobbit displays a white smiley face in the msgs column with the message:
The client did not report any logfile data
I'm running all processes as root, so there shouldn't be any permissions issues.
Can you tell me what I've done wrong in the config file?
Thanks.
Cathy
---
Cathy L. Smith
IT Engineer
Pacific Northwest National Laboratory
Phone: XXX.XXX.XXXX
Fax: XXX.XXX.XXXX
Email: user-332e187d7d6d@xymon.invalid
-----Original Message-----
From: root [mailto:user-14fe4d96760c@xymon.invalid]
Sent: Tuesday, July 27, 2010 7:35 AM
To: Smith, Cathy
Subject: localclient.cfg
# localclient.cfg - configuration file for a LOCAL Hobbit client.
#
# By default, Hobbit clients send raw data to the Hobbit server,
# which in turn converts the data into status messages.
# In that case, THIS FILE IS NOT USED and you should IGNORE it.
#
# The special DEFAULT section can modify the built-in defaults - this must
# be placed at the end of the file.
HOST=foo.pnl.gov
MEMSWAP 70 90
PROC crond
PROC http
PROC sendmail
PROC sshd
PROC syslogd
LOG /var/log/messages ERROR COLOR=red
DEFAULT
# These are the built-in defaults.
UP 1h
LOAD 16.0 30.0
DISK * 95 99
MEMPHYS 100 101
MEMSWAP 50 80
MEMACT 90 97