April 2009 - Xymon - Xymon mailman web

Still around - sort of - but a 4.3.0 beta 2 will be out tomorrow
by henrik＠hswn.dk 23 Apr '09

23 Apr '09

Hi everyone. I haven't quite dropped off the planet, but some work got seriously in the way of Xymon developments. As some of you have noticed a "4.4.0" tree appeared on the Sourceforge subversion archive - some of the features planned for 4.4.0 was needed immediately, and I didn't want that to mess up the 4.3.0 code, so I have been trying to balance both sets of releases at one time. The short version of that is "don't use the 4.4.0 tree yet, unless you can tolerate lock-ups and crashes". I'll be wrapping up the next beta version of 4.3.0 later tonight or early tomorrow and put a tar-file on Sourceforge. This has the bug- fixes which have been reported on the mailing list (and fixes quite a few bugs I found by myself). The documentation is still not quite up-to-date, but that is all that is missing. I then expect to be completely off-line until May 12, so you have two weeks to test it. And if anyone feel like submitting bugfixes or improving on the docs, you are very welcome. Regards, Henrik PS: It's a real joy to see how well the community support works on this mailing list. A big "thanks!" to all of you helping out.

2 1

Remote worker module?
by scochran＠univaud.com 23 Apr '09

23 Apr '09

(Sorry if these questions are already covered somewhere. I'm a newbie, and all of my searching didn't turn anything up.) I'm working on an integration with Hobbit for a client. They are using version 4.2.0. I need to be able to process incoming data on a server that is remote to the Hobbit server. I read in the hobbitd_channel man page that you can locate worker modules remotely by using the --net argument. Something like: bin/hobbitd_channel --channel=data --log=$BBSERVERLOGS/remote_data.log --net 10.10.4.67:12345 should (I believe) send "data" messages to host 10.10.4.67 on port 12345. However when I try this, I just get error messages in my log saying: Our child has failed and will not talk to us: Channel data, PID 3251, cause Bad file descriptor (My remote client is, for now, just a netcat listener on the port. I can telnet to it, so I know that it's there and listening.) So my questions are: 1) Does this remote capability exist in version 4.2? 2) Are there any special requirements of the client such that a generic listener (like netcat) would provoke this error message? 3) Is there a sample (or real) worker module I could look at, that is capable of being remoted in this way? Or what's the remote equivalent of the get_hobbitd_message() function call? any insight or examples would be appreciated. thanks, steve --------------------------------------------------------------------- Notice from Univa UD Postmaster: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This message has been content scanned by the Univa UD Tumbleweed MailGate. ---------------------------------------------------------------------

2 2

[hobbit] clients with different host name than uanme -n for xymon-4.2.2
by bgmilne＠staff.telkomsa.net 22 Apr '09

22 Apr '09

----- "pankaj dorlikar" <pankaj.dorlikar at gmail.com> wrote: > hello, > i am using different hostname for clients than uname -n.hence i run > runcklient.sh with --hostname=myhostname and it is running fine and > sending data to server.But now whenever in future if runclient.sh gets > stopped or client process gets killed,is ther any way to avoid running > runclient.sh with -hostname=myhostname mannually?where sholud i fix so > that my runclient.sh script always get"myhostname" and not the uname > -n.i dont want to change bb-hosts file CLIENT=hostname tag. > Any suggestions? If you are using an init script, such as the one supplied in debian/hobbit-client.init or rpm/hobbit-client.init, then you would be able to set: CLIENTHOSTNAME=myhostname in /etc/default/hobbit-client (or, /etc/sysconfig/hobbit-client in more Red Hat-like RPMs). Regards, Buchan

1 0

clients with different host name than uanme -n for xymon-4.2.2
by pankaj.dorlikar＠gmail.com 22 Apr '09

22 Apr '09

hello, i am using different hostname for clients than uname -n.hence i run runcklient.sh with --hostname=myhostname and it is running fine and sending data to server.But now whenever in future if runclient.sh gets stopped or client process gets killed,is ther any way to avoid running runclient.sh with -hostname=myhostname mannually?where sholud i fix so that my runclient.sh script always get"myhostname" and not the uname -n.i dont want to change bb-hosts file CLIENT=hostname tag. Any suggestions? -- Pankaj V. Dorlikar

1 0

Sys log (UNCLASSIFIED)
by mathew.t.rogers＠us.army.mil 22 Apr '09

22 Apr '09

Classification: UNCLASSIFIED Caveats: NONE I recently implemented Hobbit/xymon 4.2, and have a question. I looked through the archives, and didn't find what I was looking for, so if this question has been answered previously, I apologize. My supervisor wants all server logs to stay on the web page for approximately 90 days. The desire is to use Hobbit as a syslog server as well as a monitoring tool. It seems to me that when new information is sent to the Hobbit server, all the old information is removed from the web page and put in the data directory. The question is, Is there a way to make the logs visible on the webpage (when you click on msgs for each specific server) for 90 days, while still updating the logs hourly? Thanks in advance, Mathew Rogers Classification: UNCLASSIFIED Caveats: NONE

3 2

xymon-4.2.2 client shows no staus and no man pages opened
by pankaj.dorlikar＠gmail.com 21 Apr '09

21 Apr '09

hello, i am not getting client status on my dashboard for installed clients i.e. disk,cpu etc... Logs of bb-display.log says, 2009-04-20 22:50:02 Could not connect to bbd at 172.29.2.252:1984 - No route to host 2009-04-20 22:50:02 Whoops ! bb failed to send message - Connection failed 2009-04-20 22:51:03 Could not connect to bbd at 172.29.2.252:1984 - No route to host 2009-04-20 22:51:03 Whoops ! bb failed to send message - Connection failed 2009-04-20 22:51:03 hobbitd status-board not available 2009-04-20 22:51:06 Could not connect to bbd at 172.29.2.252:1984 - No route to host 2009-04-20 22:51:06 Whoops ! bb failed to send message - Connection failed 2009-04-20 22:52:07 Could not connect to bbd at 172.29.2.252:1984 - No route to host i can telnet to 172.29.2.252: at port 1984 from client. Also,i am not able to see man [pages though they are configured .when done man bb-hosts,it says no mannual entry found..help -- Pankaj V. Dorlikar

1 0

bbd:Service unavailable (Connection refused) for xymon client
by pankaj.dorlikar＠gmail.com 21 Apr '09

21 Apr '09

hello, i am getting Service unavailable (Connection refused) for bbd (red) and client data is also showing.klogs on clients say;: in logs it says hobbitclient.log 2009-04-20 22:54:00 Could not connect to bbd at 172.29.2.252:1984 - No route to host 2009-04-20 22:54:00 Whoops ! bb failed to send message - Connection failed but ping and telnet is fine from client and also bb-hosts entry is correct.. wt is wrong? help -- Pankaj V. Dorlikar

2 1

Xymon-4.3.0-beta1: incorrect value for "count" rrd
by dominique.frise＠unil.ch 20 Apr '09

20 Apr '09

Hi, We track "surgemail" processes using following rule in hobbit-clients.cfg: HOST=xyz PROC ./surgemail min=0 TRACK=surgemail The ps listing in msg.xyz.txt reports 315 "./surgemail" processes, while the rrd graph only shows ~30 processes. Here the last corresponding dataset of processes.surgemail.rrd file (after flushing the cache by stopping Xymon): <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE rrd SYSTEM "http://oss.oetiker.ch/rrdtool/rrdtool.dtd"> <rrd> <version> 0003 </version> <step> 300 </step>  <lastupdate> 1239775972 </lastupdate>  <ds> <name> count </name> <type> GAUGE </type> <minimal_heartbeat> 600 </minimal_heartbeat> <min> 0.0000000000e+00 </min> <max> NaN </max>  <last_ds> 30 </last_ds> <value> 5.1600000000e+03 </value> <unknown_sec> 0 </unknown_sec> </ds>  <rra> We tried to let Xymon recreate a fresh rrd without success. The same configuration was working with Hobbit-4.2.0/RRDtool 1.2.19 (same version) The rrd-code has pretty changed since 4.2.0 and I don't really see what code is involved to try debugging this. Any help appreciated! Dominique

1 2

bbtest Child process terminated with signal 15
by martin.flemming＠desy.de 19 Apr '09

19 Apr '09

Hi ! I've got besides warning-mail by xymon .. bbtest warning (YELLOW) Error output: Timeout waiting for data from child, killing it Timeout waiting for data from child, killing it Child process terminated with signal 15 Unfortunately i didn't found the host who makes this error ... Can somebody give me an hint how i detect this error-host ? .. in hobbitlaunch.cfg, i've added to the bbnet-test CMD bbtest-net --report --ping --checkresponse --dnslog=/usr/lib/hobbit/serverlogs/dns.log --debug nothing appears in dns.log and in bb-network.log appears to much .. :-( So, which things are important to detect the error-host apart error and/or failed in the logfile ? Is there another possiblity to debug this problem ? Thanks in advance & cheers martin ---------- Forwarded message ---------- Date: Fri, 10 Apr 2009 15:23:53 +0200 (CEST) From: Hobbit user <hobbit at mail.desy.de> To: hobbit-patrol at desy.de Subject: Hobbit [94627] it-wgs02:bbtest warning (YELLOW) yellow Fri Apr 10 15:21:13 2009 bbtest-net version 4.3.0-0.20071026 SSL library : OpenSSL 0.9.7a Feb 19 2003 LDAP library: OpenLDAP 20213 Statistics: Hosts total : 1791 Hosts with no tests : 730 Total test count : 1324 Status messages : 1327 Alert status msgs : 0 Transmissions : 14 DNS statistics: # hostnames resolved : 1063 # succesful : 1063 # failed : 0 # calls to dnsresolve : 1322 TCP test statistics: # TCP tests total : 150 # HTTP tests : 7 # Simple TCP tests : 143 # Connection attempts : 150 # bytes written : 1740 # bytes read : 23223 Error output: Timeout waiting for data from child, killing it Timeout waiting for data from child, killing it Child process terminated with signal 15 TIME SPENT Event Starttime Duration bbtest-net startup 1239369673.473591 - Service definitions loaded 1239369673.488615 0.015024 Tests loaded 1239369688.393655 14.905040 DNS lookups completed 1239369688.410264 0.016609 Test engine setup completed 1239369688.429766 0.019502 TCP tests completed 1239369699.001287 10.571521 PING test completed (1061 hosts) 1239369737.658479 38.657192 PING test results sent 1239369767.700406 30.041927 Test result collection completed 1239369767.703455 0.003049 LDAP test engine setup completed 1239369767.703457 0.000002 LDAP tests executed 1239369767.703459 0.000002 LDAP tests result collection completed 1239369767.703461 0.000002 NTP tests executed 1239369767.814258 0.110797 RPC tests executed 1239369769.447013 1.632755 Test results transmitted 1239369769.547149 0.100136 bbtest-net completed 1239369769.552037 0.004888 TIME TOTAL 96.078446

2 2

debugging for purple color for client status
by pankaj.dorlikar＠gmail.com 18 Apr '09

18 Apr '09

how and where to find or debug for purple status for clients -- Pankaj V. Dorlikar

3 2