May 2008 - Xymon - Xymon mailman web

[hobbit] msgs on kern.log don't go away
by bewhite＠fellowes.com 19 May '08

19 May '08

Glad to be of help! -----Original Message----- From: Ricardo Alberto Schutz [mailto:ricardo at redix.com.br] Sent: Monday, May 19, 2008 3:40 PM To: hobbit at hswn.dk Subject: Re: [hobbit] msgs on kern.log don't go away Yeah! Thank you... I think I ran hobbit with root privileges at the first time. Maybe it changed the file permissions. Working fine now. Thanks. Ricardo Alberto Schütz - Consultor -------------------------------------------- Redix - Gestão em T.I. com Software Livre http://www.redix.com.br - contato at redix.com.br Tel. Coml.: +55 (47) 3323-7313 Tel. Cel.: +55 (47) 9186-9868 -------------------------------------------- White, Bruce wrote: > I have had this problem when one of the temp files on the client in > client/tmp was created by root when I tried starting the client with root. > The tmp file can not be removed by the hobbit user, so the status on the > messages file never changes and the messages continue to stay red. Once I > deleted this tmp file and allowed the hobbit user to create the temp files > it needs under its ID, the problem went away. > > .....Bruce > > > -----Original Message----- > From: Ricardo Alberto Schutz [mailto:ricardo at redix.com.br] > Sent: Monday, May 19, 2008 10:08 AM > To: hobbit at hswn.dk > Subject: [hobbit] msgs on kern.log don't go away > > Hi, > > When a host is restarted, I get messages on kern.log showing infos about > the disc arrays. Ok, nothing wrong with that. The thing is that the > messages don't go away. Right now the msgs column is red and the > information is from May 2. So it's red since then. > > What I could understand is that hobbit uses logfetch with a > configuration file to locate where in the log files it should look. I > tried to remove the file used by logfetch on the client and restarted > the client a few times. Hobbit recreated the file, but no success. > > It's running on a RHEL 4. Hobbit client installed from source. > > To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk ---------------------------------------------------- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc. ----------------------------------------------------

1 0

ghostlist
by philwild＠gmail.com 19 May '08

19 May '08

Hi, I asked this yesterday but without response so I'll try a different way. How does one remove a server from the ghostlist? I expected that all I would need to do is add it to the bb-hosts file but it continues to show up (using bb 127.0.0.1 ghostlist) A restart seems to work but there must be a better answer... Many thanks Phil -- Tel: 0400 466 952 Fax: 0433 123 226 email: philwild AT gmail.com

6 11

[hobbit] msgs on kern.log don't go away
by bewhite＠fellowes.com 19 May '08

19 May '08

I have had this problem when one of the temp files on the client in client/tmp was created by root when I tried starting the client with root. The tmp file can not be removed by the hobbit user, so the status on the messages file never changes and the messages continue to stay red. Once I deleted this tmp file and allowed the hobbit user to create the temp files it needs under its ID, the problem went away. .....Bruce -----Original Message----- From: Ricardo Alberto Schutz [mailto:ricardo at redix.com.br] Sent: Monday, May 19, 2008 10:08 AM To: hobbit at hswn.dk Subject: [hobbit] msgs on kern.log don't go away Hi, When a host is restarted, I get messages on kern.log showing infos about the disc arrays. Ok, nothing wrong with that. The thing is that the messages don't go away. Right now the msgs column is red and the information is from May 2. So it's red since then. What I could understand is that hobbit uses logfetch with a configuration file to locate where in the log files it should look. I tried to remove the file used by logfetch on the client and restarted the client a few times. Hobbit recreated the file, but no success. It's running on a RHEL 4. Hobbit client installed from source. -- Ricardo Alberto Schütz - Consultor -------------------------------------------- Redix - Gestão em T.I. com Software Livre http://www.redix.com.br - contato at redix.com.br Tel. Coml.: +55 (47) 3323-7313 Tel. Cel.: +55 (47) 9186-9868 -------------------------------------------- To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk ---------------------------------------------------- Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc. ----------------------------------------------------

2 1

/var/log/messages permission denied
by gleonard＠progrexion.com 19 May '08

19 May '08

When I look at my messages status on the Main BB page I only see this? Do I need to change the perms on the /var/log/messages folder? No entries in /var/log/messages<http://misery.pgx.local/hobbit-cgi/bb-hostsvc.sh?CLIENT=pbx-01&SECTION=msgs…> Full log /var/log/messages<http://misery.pgx.local/hobbit-cgi/bb-hostsvc.sh?CLIENT=pbx-01&SECTION=msgs…> Cannot open logfile /var/log/messages : Permission denied Gavin Leonard [cid:image001.gif at 01C8B6EF.046C8940] Director, Systems-Network Engineering T 801-828-1735 F 801-828-1704 E gleonard at progrexion.com<mailto:gleonard at progrexion.com> Research | Marketing | Sales Generation www.progrexion.com<http://www.progrexion.com/> This email and its contents are confidential. If you are not the intended recipient, delete this email and do not use or disclose the information within this email or its attachments. Thank you.

7 11

[hobbit] /var/log/messages permission denied Centos 4 and 5
by pkrash＠exegy.com 19 May '08

19 May '08

Must be something unique in our environment.. Thanks for looking at it... ----- Original Message ----- From: Josh Luthman <josh at imaginenetworksllc.com> To: hobbit at hswn.dk <hobbit at hswn.dk> Sent: Mon May 19 10:15:49 2008 Subject: Re: [hobbit] /var/log/messages permission denied Centos 4 and 5 For the record...on all of my CentOS 5 and 5.1 boxes it stuck with the modified group. On Sat, May 17, 2008 at 11:21 AM, Krash, Paul <pkrash at exegy.com> wrote: Mr. Luthman wrote: > Can you give us all some details on how do to that? Sure! Here is the default script from Centos5.1 with the chmod command: #/etc/cron.daily/logrotate #!/bin/sh /usr/sbin/logrotate /etc/logrotate.conf EXITVALUE=$? if [ $EXITVALUE != 0 ]; then /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]" fi /bin/chmod 755 /var/log/messages exit 0 Notice that this makes /var/log/messages world readable. :-O But I digress. :-) Best, PKrash, temporarily working off a Winserver, sorry for any Outlook mangling. This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others. To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others.

1 0

msgs on kern.log don't go away
by ricardo＠redix.com.br 19 May '08

19 May '08

Hi, When a host is restarted, I get messages on kern.log showing infos about the disc arrays. Ok, nothing wrong with that. The thing is that the messages don't go away. Right now the msgs column is red and the information is from May 2. So it's red since then. What I could understand is that hobbit uses logfetch with a configuration file to locate where in the log files it should look. I tried to remove the file used by logfetch on the client and restarted the client a few times. Hobbit recreated the file, but no success. It's running on a RHEL 4. Hobbit client installed from source. -- Ricardo Alberto Schütz - Consultor -------------------------------------------- Redix - Gestão em T.I. com Software Livre http://www.redix.com.br - contato at redix.com.br Tel. Coml.: +55 (47) 3323-7313 Tel. Cel.: +55 (47) 9186-9868 --------------------------------------------

1 0

Fedora 9 install
by James.Roberts＠hants.gov.uk 19 May '08

19 May '08

Has anyone installed hobbit server on Fedora 9 yet? I have installed the server via RPM before on Fedora 8 but now it is complaining about dependencies.

2 3

dr for hobbit
by philwild＠gmail.com 19 May '08

19 May '08

Hi all, I am redesigning the method we use for performing a failover to a disaster recovery installation of hobbit. I am interested in opinions on the approach and any shortcomings. Note: This is not HA/clustering, it is for DR purposes. We are aiming to have: a production hobbit deployment a DR hobbit deployment clients will be configured to send metrics to both servers. which will keep historical rrd data up to date etc. The production server will be configured to send out alerts. The dr server will not. At regular intervals, rsync will be used to synchronise data from the production server to the dr server, including the in memory checkpoint file. In the event of a dr, the dr hobbit server will be promoted to active by restarting hobbit, and loading the checkpoint and alert configurations. I am expecting that this will ensure that the dr server will be "up to date" with proudction as per the last checkpoint. This includes tests that have been disabled or acknowledged. Prior to failback to the production hobbit installation, the reverse of the above would be performed. An rsync of rrd data files would be performed to cover any windows where one of the servers was offline for a period of time. Is there anything wrong with this approach? Cheers Phil -- Tel: 0400 466 952 Fax: 0433 123 226 email: philwild AT gmail.com

6 7

removing a client from the ghostlist
by philwild＠gmail.com 18 May '08

18 May '08

Hi Hobbit users, If I run bb 127.0.0.1 ghostlist on my hobbit server, I get a list of hosts that are not defined in my bb-hosts file. If I then add a host into the bb-hosts file (actually, I first added it to an include file but adding it to the bb-hosts was the same), I would have expected the host to no longer show up un the ghostlist report. This does not seem to be the case, what am I doing wrong? If I restart hobbit, it goes away, but I don't want to have to do this if I don't need to. Many thanks Phil -- Tel: 0400 466 952 Fax: 0433 123 226 email: philwild AT gmail.com

1 0

BBWin 0.11 Centralised Config problems
by Matthew.Roberts＠nt.gov.au 18 May '08

18 May '08

Hi All, I need a bit of assistance in setting up BBWin0.11 with Hobbit 4.3 in Centralised config mode. My problem lies with the eventlog monitoring of my Windows hosts. When running BBWin in local config mode, I can setup filtering so that only specific event log types get sent to the hobbit server and displayed on the msgs page. However when I configure BBWin to use a central config, I cant filter which event logs get sent to the hobbit server and displayed on the msgs page. As a result my msgs page is full of eventlog entries which I dont need to know about. Below is a copy of my BBWin.cfg and the client-local.cfg on the hobbit server <?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="hobbit-server" />     <setting name="mode" value="central" /> <setting name="configclass" value="win32" /> <setting name="autoreload" value="true" /> <setting name="timer" value="5m" /> <load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/> <setting name="loglevel" value="3" /> <setting name="logpath" value="C:\Program Files\BBWin\logs\BBWin.log"/>  <setting name="logreportfailure" value="false" /> </bbwin> client-local.cfg: (dcstest2 is the name of one of my hosts I am having problems with) [dcstest2] eventlog:security ignore Success eventlog:application ignore information eventlog:system ignore information Also something else I noticed is that the msgs page for my hobbit server which I also monitor displays the eventlog entries of my Win32 hosts. The hobbit server is running on SUSE Server 10.1 and I have even tried a complete rebuild in case there was a problem during the install phase. Assistance would be greatly appreciated. Thanks

4 6