January 2009 - Xymon - Xymon mailman web

libpcre.so.0 missing
by sup_op＠hotmail.fr 27 Jan '09

27 Jan '09

Hi everybody i have these in in my bb-dispblay.log bbgen: error while loading shared libraries: libpcre.so.0: cannot open shared object file: No such file or directory but when i do these ashley:/var/log/xymon# locate libpcre.so.0 /usr/local/lib/libpcre.so.0 anyone have any ideas ? Thank you _________________________________________________________________ Découvrez Windows Live Spaces et créez votre site Web perso en quelques clics ! http://spaces.live.com/signup.aspx

2 1

Task bbdisplay terminated, status 127
by sup_op＠hotmail.fr 27 Jan '09

27 Jan '09

Hi sorry for all the questions, but i can't make my xymon server start, i look in the log hobbitlaunch i saw these: Task bbdisplay terminated, status 127 I reading the post in the archive but without results i really need help. please _________________________________________________________________ Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live ? Lancez-vous ! http://www.microsoft.com/windows/windowslive/default.aspx

1 0

SMTP - connection refused
by URMM＠VM.MARIST.EDU 26 Jan '09

26 Jan '09

I'm monitoring some very busy SMTP servers that handle all our incoming email. Because they are so busy, at times, Xymon will get a connection refused condition when testing SMTP, which generates a red alert. Its fine at the next test cycle, but the false alerts concern me. (People get used to seeing false alerts, they ignore the real ones.) Does anyone have any suggestions? Is there I way I can alter the SMTP test to not generate this condition as an alert, or perhaps an alert script that won't send out an email? Martha McConaghy Marist College

3 3

Hobbit and Windows Server 2008
by dwdaniel＠vcu.edu 23 Jan '09

23 Jan '09

I would like to know if there is a current or forthcoming hobbit client for Windows Server 2008 (32bit & 64 bit).

7 10

Xymon 4.2.2 (a.k.a. Hobbit) has been released
by henrik＠hswn.dk 23 Jan '09

23 Jan '09

I am pleased to announce that Xymon version 4.2.2 is now available from Sourceforge. Xymon is the new name for the Hobbit monitor - the name was changed for legal reasons. The new version fixes a lot of bugs in the previous release, including all of the bugs that were handled by the "all-in-one" patch for Hobbit 4.2.0. Version 4.2.2 also merges server-side support required by several of the popular Xymon add-ons: Devmon, BBWin and the hobbit-perl-client. It is available at the Sourceforge project site, https://sourceforge.net/project/showfiles.php?group_id=128058&package_id=14… Regards, Henrik

14 21

meta.sh fails to alert without the following changes to latest meta 2.2
by vadud3＠gmail.com 23 Jan '09

23 Jan '09

diff meta.sh meta.sh.orig 241c241 < if [ "$COLOR" != "red" ]; then --- > if [ COLOR != "red" ]; then 279c279 < if [ "$COLOR" != "red" ]; then --- > if [ COLOR != "red" ]; then -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu

1 0

bbproxy
by oyvind.bjorge＠telenor.com 23 Jan '09

23 Jan '09

I have seen some information about the bbproxy on the net, but I have not been able to find it. Does someone know where it is available? Øyvind

2 1

Generating custom client data file
by Vernon.Everett＠woodside.com.au 23 Jan '09

23 Jan '09

Greetings all I have an interesting question/problem, and I am hoping somebody can help me. (I think this might be one for Henrik though) We have a Windoze database cluster, with bbwin on each, which works OK. Those who know the Microsoft cluster software, will know that the "active" disks could be resident on any server. As a result, you may have a disk appear on one server, then "disappear", and suddenly "reappear" on another server in the cluster. This makes consistent monitoring and trending difficult. We decided to try and write a test which created a consistent view of the cluster. To do this, we created a script which runs on all the members of the cluster, but only the "active" member would send results, pretending to be a server called $CLUSTER_NAME To make this happen, we decided to send a new data file to the hobbit server, as if it was a new client altogether. (Data file like the one you see when you click on "Client Data" link in the disk view) Of course, there is no physical server with this name, it's just a "place-holder" and an entry in bb-hosts. We ended up sending just the basics - at least to start with. It looked like this. client DBS_CLUSTER.bbwin win32 [date] 19/01/2009 2:55:51 PM [disk] Filesystem 1K-blocks Used Avail Capacity Mounted Summary(Total\Avail) I 314568732 23992884 290575848 7.% /FIXED/I 300.00gb\277.11gb J 26210012 6593428 19616584 25% /FIXED/J 25.00gb\18.71gb Then something really strange happened. (see attached image) It graphed the 2 drives OK, but these 2 red entries appeared. They are not related to any disk, and we have no idea where they are coming from. Any ideas or suggestions welcome Regards Vernon NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.

1 1

[hobbit] Is there any equivalent to BB's notifications exclusions?
by henrik＠hswn.dk 22 Jan '09

22 Jan '09

In <1232649955 at mknews.sslug.dk> "SebA" <spa at syntec.co.uk> writes: >>> # You can also write rules to exclude recipients based on the >>> # previous syntax. Just prefix with ! and any recipient >>> # specified in the rule line will be removed from the >>> # list of recipients that matches the regular rules # >>> # for all hosts don't send any notifications from=3D20 # 12AM to 6AM >>> and 8PM to 12AM # >>> # !*;;*;;*;0000-0600 2000-2359;* >>=20 >> If you only want to send alerts between 6AM and 8PM, then =20 >> TIME=3D*:0600:2000 will do that. Alternatively, an = >"EXTIME=3D*:2000:0600" >> has the same effect (a more direct conversion of this rule). >That's not quite the same thing (see below), but I think if I put EXTIME >rules in with the e-mail addresses in macros (for convenience), I will >be able to do what I need to. >>> # !host*;;*;;0 6;*;robert at localhost >>=20 >> HOST=3D* EXHOST=3D%^host >> MAIL robert at localhost >Not really: the BB rule says: for _all_ alerts that were due to be >raised for host*, at the weekend, to robert at localhost (based on higher >up rules with no ! prefix), don't send them out. In other words, >cancel all previous _matching_ MAIL commands for this exclusion. In that case I misunderstood the BB config semantics - which is not surprising, since they never made much sense to me, and I haven't used them for more than 5 years :-) >I still think Xymon may benefit from a notifications exclusions system >though. (Especially for easier migration for BB users! ;)) On the other >hand, it does add complication that is perhaps unnecessary. I currently >use these exclusions extensively. From when someone goes on holiday >(turn off all their alerts no matter what service or host they refer to), >or maybe your e-mail to SMS gateway or provider has a problem and you >want to stop all those e-mails (but not all the internal e-mails) being >generated, queueing up and then coming through in a rather unnecessarrily >expensive flood when the SMS provider starts working again. I realize that you have a working set of configuration rules, but I think it would be a lot easier to work out a functionally identical set of rules for Hobbit/Xymon if you could describe what it is you want to achieve with the configuration, instead of focusing on how it was done in BB. The closest to what you want to do might be to use the "IGNORE" setting in hobbit-alerts.cfg. E.g. your example: !host*;;*;;0 6;*;robert at localhost could be accomplished with something like HOST=%^host TIME=06:0000:2359 IGNORE although this would kill alerts for all recipients, not just those destined for "robert at localhost". And note that this must go BEFORE any of the other rules for this host. I can see that the BB exclusion mechanism might be useful in some circumstances, but it would (obviously) make the alerting mechanism more complicated. And I'm not convinced that there's enough gained to warrant this. Regards, Henrik

1 0

[hobbit] Is there any equivalent to BB's notifications exclusions?
by henrik＠hswn.dk 22 Jan '09

22 Jan '09

In <1232560301 at mknews.sslug.dk> "SebA" <spa at syntec.co.uk> writes: >I would like to migrate my notifications rules from BB Server to >Hobbit / Xymon Server. I use the following BB syntax extensively: ># You can also write rules to exclude recipients based on the ># previous syntax. Just prefix with ! and any recipient ># specified in the rule line will be removed from the ># list of recipients that matches the regular rules ># ># for all hosts don't send any notifications from=20 ># 12AM to 6AM and 8PM to 12AM ># ># !*;;*;;*;0000-0600 2000-2359;* If you only want to send alerts between 6AM and 8PM, then TIME=*:0600:2000 will do that. Alternatively, an "EXTIME=*:2000:0600" has the same effect (a more direct conversion of this rule). ># !host*;;*;;0 6;*;robert at localhost HOST=* EXHOST=%^host MAIL robert at localhost ># !host1;;*;;*;*;* HOST=* EXHOST=host1 The latter two don't really need the "HOST=*" since that is the default. But some (myself included) find it easier to read when you explicitly write "ALL hosts, EXCEPT ..." Regards, Henrik

2 1