I checked - the allinone patch has significant changes for logfetch.c, the client-side program that processes the log file.
Tom
-----Original Message----- From: L.M.J [mailto:linuxmasterjedi at free.fr] Sent: Saturday, September 13, 2008 1:58 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Problem to check logs with Hobbit
Le Wed, 10 Sep 2008 13:34:46 -0400, "Kauffman, Tom" <KauffmanT at nibco.com> a écrit :
On your hobbit server -
set up etc/client-local.cfg to reference the logs you want AND any exclusions. For AIX, I have: [aix] log:/var/log/syslog:10240 ignore 3004-004 ignore 3004-035 ignore 3004 log:/var/log/console.log:10240 log:/var/log/dsmsched.log:10240
set up etc/hobbit-clients.cfg to create your alerting criteria. For AIX, I've got these set: HOST=%.* LOG /var/log/syslog %.*crit.su.*to.root red LOG /var/log/syslog %.*crit.su yellow LOG %/var/(adm|log)/console.log %.*not.responding.still.trying yellow
Change client-local.cfg first. Allow 15 to 20 minutes for this to propagate to the client; look for a file called logfetch.<hostname>.cfg in client/tmp. This should match your entries in client-local.cfg.
Once the logs sart coming in, play with the client-local.cfg and a test system, to track what you're interested in.
Hi & thanks once again for you tutorial but that's crazy, I still can't see any log reported to the server! I'm monitoring oracle & mysql databases, Netapp filers, DNS, DHCP, smtp, imap, firewall via devmons, SAP via CheckMySAP plugin, a lot processes on 4 different OS, etc... but I'm incapable to monitor a nasty log file :-/ Is there some well-know bugs about this issue? I'm using Hobbit 4.2.0 without allinonepatch.
Thanks for any help
Best regards,
LMJ