November 2009 - Xymon - Xymon mailman web

[hobbit] firefox 3.5 problem with graph zoom display - ymon 4.2.2-RC1-2008.12.01
by Craig.Cook＠carquest.com 05 Nov '09

05 Nov '09

>> Hi >> >> I am running Xymon 4.2.2-RC1-2008.12.01 and have a problem with some, >> but not all browsers. >> >> The problem occurs, then I go to Trends and selects the magnifying glass >> >> ican. The graph displayed for zooming is displayed and immediately >> coveret with a blue square. >> >> This occurs in: firefox 3.5 and Opera 9.64 >> >> This does not occur in: firefox 3.0, Crome 2.0.172.37 and IE 8.0.6001 >> >> >> All hints are appreciated. >> >> Best regards >> >> Harald Villemoes Could this be related? http://bugs.cacti.net/view.php?id=351 Craig

1 0

ack bug
by doctor＠makelofine.org 05 Nov '09

05 Nov '09

An HTML attachment was scrubbed... URL: <http://lists.xymon.com/pipermail/xymon/attachments/20091105/7263a5bb/attach…>

3 4

4.4.0
by lars.ebeling＠leopg9.no-ip.org 05 Nov '09

05 Nov '09

Because of some illness and lack of time I haven't tested Xymon for a while. Today I installed Xymon 4.4.0-1 from 2009-10-27. I get no Menu on the different servicepages and no bb-footer. You could have a look at the link below. -- Regards Lars Ebeling http://leopg9.no-ip.org Hobbithobbyist "I am not young enough to know everything." -- Oscar Wilde

2 5

Location of the Linux / Unix client software
by d.tom.schmitt＠L-3com.com 04 Nov '09

04 Nov '09

I know this is a trivial question, but I cannot find the Linux client code. Server is Xymon-4.3.0-0.beta2 on CentOS 5.3. I am running the Linux client on a test system currently. I cannot find the link to the location of the software on any site. Is there a different software for UNIX vs. Linux? Is it just source or is it compiled? I have the directories on the server but don't want to copy them over to another system. I could not find any links under Help on the web page nor on Sourceforge - must be looking for the wrong thing. I know that the Windows client BBWin has its own site. Thanks, Tom Schmitt Senior IT Staff - R&D D.Tom.Schmitt at L-3Com.com \\\\||//// \ ~ ~ / | @ @ | --oOo---(_)---oOo--

3 5

MEMPHYS vs MEMACT?
by dewey＠sasser.com 04 Nov '09

04 Nov '09

Hello all, I'm trying to understand the machine memory graphs -- specifically the differences between MEMPHYS and MEMACT (or "actual" and "real" on the graphs). Is this pretty much straight from vmstat? e.g. Is "actual" the "active" memory from vmstat and "real" the total - free? I recall seeing information on this weeks ago, but my GoogleFu (and Google Desktop) fails me today. Thanks, -- Dewey **

2 1

hobbitd_rrd crashing over and over.
by wgreen＠bridge2solutions.com 04 Nov '09

04 Nov '09

I am running xymon 4.3.0-0 beta 2 on a RHEL 5.4 x86_64 arch. Every 5mins or so, I get an alert that hobbit_rrd has crashed, and I get a ton of core files. # uname -a Linux xymon 2.6.18-164.el5xen #1 SMP Tue Aug 18 15:59:52 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa |grep rrd rrdtool-1.2.23-1.el5.rf rrdtool-devel-1.2.23-1.el5.rf perl-rrdtool-1.2.23-1.el5.rf [root at xymon server]# file tmp/core.11912 tmp/core.11912: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'hobbitd_rrd' Here is the backtrace: # gdb bin/hobbitd_rrd tmp/core.11912 GNU gdb Fedora (6.8-37.el5) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"... Reading symbols from /usr/lib64/librrd.so.2...done. Loaded symbols for /usr/lib64/librrd.so.2 Reading symbols from /lib64/libpcre.so.0...done. Loaded symbols for /lib64/libpcre.so.0 Reading symbols from /lib64/librt.so.1...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libc.so.6...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /usr/lib64/libfreetype.so.6...done. Loaded symbols for /usr/lib64/libfreetype.so.6 Reading symbols from /usr/lib64/libpng12.so.0...done. Loaded symbols for /usr/lib64/libpng12.so.0 Reading symbols from /usr/lib64/libz.so.1...done. Loaded symbols for /usr/lib64/libz.so.1 Reading symbols from /usr/lib64/libart_lgpl_2.so.2...done. Loaded symbols for /usr/lib64/libart_lgpl_2.so.2 Reading symbols from /lib64/libm.so.6...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /lib64/libpthread.so.0...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Core was generated by `hobbitd_rrd --rrddir=/opt/hobbit/data/rrd'. Program terminated with signal 6, Aborted. [New process 11912] #0 0x000000398ec30265 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x000000398ec30265 in raise () from /lib64/libc.so.6 #1 0x000000398ec31d10 in abort () from /lib64/libc.so.6 #2 0x00000000004201c3 in sigsegv_handler (signum=<value optimized out>) at sig.c:57 #3 <signal handler called> #4 0x000000385dc2a823 in write_RRA_row (rrd=0x7fffea126180, rra_idx=3, rra_current=0x7fffea126218, CDP_scratch_idx=<value optimized out>, rrd_file=0x1a3e84f0, pcdp_summary=0x0, rra_time=0x7fffea126208, rrd_mmaped_file=0x2b2a8173a000) at /usr/include/bits/string3.h:51 #5 0x000000385dc2c3e3 in _rrd_update ( filename=0x63b6c0 "/opt/hobbit/data/rrd/xymon/vmstat.rrd", tmplt=<value optimized out>, argc=9, argv=0x7fffea1262d0, pcdp_summary=0x0) at rrd_update.c:1230 #6 0x000000385dc2d207 in rrd_update (argc=13, argv=0x7fffea1262b0) at rrd_update.c:183 #7 0x000000000040497b in flush_cached_updates (cacheitem=0x1a3a3580, newdata=<value optimized out>) at do_rrd.c:223 #8 0x00000000004065b9 in create_and_update_rrd (hostname=0x2b2a8152bfb7 "xymon", testname=0x2b2a8152bfc8 "vmstat", classname=<value optimized out>, pagepaths=<value optimized out>, creparams=0x1a3da170, template=0x1a3a2bb0) at do_rrd.c:393 #9 0x000000000040d8b2 in do_vmstat_rrd (hostname=0x2b2a8152bfb7 "xymon", testname=0x2b2a8152bfc8 "vmstat", classname=0x2b2a8152bfcf "linux", pagepaths=0x426002 "", msg=<value optimized out>, tstamp=<value optimized out>) at rrd/do_vmstat.c:436 #10 0x0000000000410885 in update_rrd (hostname=0x2b2a8152bfb7 "xymon", testname=0x2b2a8152bfc8 "vmstat", msg=0x2b2a8152bfd6 "data xymon.vmstat\nlinux\n 0", tstamp=1257351440, sender=<value optimized out>, ldef=<value optimized out>, classname=0x2b2a8152bfcf "linux", pagepaths=0x426002 "") at do_rrd.c:591 #11 0x0000000000403017 in main (argc=<value optimized out>, argv=0x7fffea129908) at hobbitd_rrd.c:366 I have done fresh recompiles of multiple versions of xymon, used different versions of the rrd packages, and this error still constantly pops up. I get a ton of errors in rrd-data.log: 2009-11-04 11:17:24 Peer at 0.0.0.0:0 failed: Broken pipe 2009-11-04 11:17:24 Peer not up, flushing message queue 2009-11-04 11:27:26 Peer at 0.0.0.0:0 failed: Broken pipe 2009-11-04 11:27:26 Peer not up, flushing message queue 2009-11-04 11:42:33 Peer at 0.0.0.0:0 failed: Broken pipe 2009-11-04 11:42:33 Peer not up, flushing message queue 2009-11-04 11:46:08 Peer at 0.0.0.0:0 failed: Broken pipe 2009-11-04 11:46:08 Peer not up, flushing message queue I've honestly never had this problem before, and I'm pretty baffled.

1 0

New Big Brother interface
by josh＠imaginenetworksllc.com 04 Nov '09

04 Nov '09

Has anyone seen this? This is just crazy... http://www.bb4.com/bb4-screenshot-tour/index.html Please don't ever let Xymon go down this road. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 "When you have eliminated the impossible, that which remains, however improbable, must be the truth." --- Sir Arthur Conan Doyle

6 6

bb-histlog.sh : internal server error - SIGSEGV
by gianluca.rossi＠acantho.com 04 Nov '09

04 Nov '09

Hi, my xymon server (64 bit debian lenny) running Xymon 4.3.0-0.beta2 is sometimes reporting "Internal server error" executing history with bb-histolog.sh. example, this url: /hobbit-cgi/bb-histlog.sh?HOST=nb-ser&SERVICE=backup&TIMEBUF=Sun_Oct_25_14:39:38_2009 i have the gdb trace: Program received signal SIGSEGV, Segmentation fault. 0x00007fff7347e5a8 in ?? () from /lib/libc.so.6 (gdb) bt #0 0x00007fff7347e5a8 in ?? () from /lib/libc.so.6 #1 0x00007fff7347ea56 in free () from /lib/libc.so.6 #2 0x00000000004096cc in expand_env (s=0x424dea "4.3.0-0.beta2") at environ.c:295 #3 0x000000000040958a in xgetenv (name=0x424ddf "HOBBITDREL") at environ.c:167 #4 0x000000000040d76f in headfoot (output=0x7fff73756780, template=0x7fff735266f8 "double free or corruption (!prev)", pagepath=0x1 <Address 0x1 out of bounds>, head_or_foot=0x2d746962626f682f <Address 0x2d746962626f682f out of bounds>, bgcolor=7045168) at headfoot.c:1380 #5 0x0000000000410a9f in generate_html_log (hostname=0x6b9130 "nb-ser", displayname=0x6b9130 "nb-ser", service=0x6b9150 "backup", ip=0x76c1e0 "10.12.10.40", color=5, sender=0x6ba310 "10.12.10.40", flags=0x427c1e "", logtime=0, timesincechange=0x7fff7bda9460 "0.00 minutes", firstline=0x7aa490 "red Sun Oct 25 14:39:38 CET 2009 - Errors netbackup ", restofmsg=0x7a8145 " - - - ERRORS - - -\n10/25/2009 14:36:23 nb-ser mdoc1 cannot connect to mdoc1, Operation now in\n", ' ' <repeats 20 times>, "progress (150)\n10/25/2009 14:36:23 nb-ser mdoc1 backup of client mdoc1 exited with "..., acktime=0, ackmsg=0x0, acklist=0x0, disabletime=0, dismsg=0x0, is_history=1, wantserviceid=0, htmlfmt=0, locatorbased=0, multigraphs=0x422ad8 ",disk,inode,qtree,quotas,snapshot,TblSpace,if_load,", linktoclient=0x6b9040 "/hobbit-cgi/bb-histlog.sh?CLIENT=nb-ser&TIMEBUF=1256477685", nkprio=0x0, nkttgroup=0x0, nkttextra=0x0, graphtime=172800, output=0x7fff73756780) at htmllog.c:169 #6 0x0000000000402c03 in do_request () at hobbitsvc.c:571 #7 0x000000000040448f in main (argc=4, argv=<value optimized out>) at hobbitsvc.c:674 (gdb) quit there is a problem only for some request, usually the history program works fine. is 4.3.0-0.beta2 the last 4.3 branch? i see on http://www.xymon.com Xymon 4.3.0-1.3: is this an updated version? -- Gianluca

2 1

Help with hobbitd_channel and hobbitd_filestore
by tlewick＠tradebotsystems.com 04 Nov '09

04 Nov '09

More digging, this stems from the fact that I was passing channel=client, and hobbit_filestore doesn't support the client channel, at least in the version I have, i.e. 4.2.0 I just tried running: bbcmd hobbitd_channel --channel=data --log=/home/hobbit/data/logs/clientcpu.log hobbitd_filestore --data and that did work. So now it's a question of, how do I get hobbitd_filestore to work with hobbit_channel --channel=client? Modify hobbitd_filestore.c? -----Original Message----- From: Taylor Lewick Sent: Friday, October 30, 2009 10:58 AM To: 'hobbit at hswn.dk' Subject: RE: Help with hobbitd_channel and hobbitd_filestore I think this is a problem with hobbitd_filestore getting/reading the correct file I changed the hobbitd_channel command to: ./hobbitd_channel --channel=client --log=/home/hobbit/data/logs/logfile.txt get_channel_data.pl The get_channel_data.pl was a very simple perl script I wrote just to see if it was getting data from Standard Input. And it worked. The perl script is just: #!/usr/bin/pl $FH="/home/hobbit/data/logs/clientchannel.log": open (OUTFILE, ">$FH"); while ( <STDIN> ) { chomp $_; print OUTFILE "$_\n"; } close (OUTFILE); So clientchannel.log has the output I'd expect to see. And the logfile is no longer being populated with "Our child has failed and will not talk to us... Cause bad file descriptor" messages The only similar post I could find on this was the following thread, http://www.hswn.dk/hobbiton/2006/08/msg00326.html But that was back a few years and was for someone who was running on AIX, and it looked inconclusive. FYI, I'm running hobbit 4.2.0 on a Suse 10.2 server.

2 1

Alert mails with the Ack-Code
by Vernon.Everett＠woodside.com.au 04 Nov '09

04 Nov '09

Hi all Is there an easy way to send alerts without the ACK-CODE? By "easy", I mean not hacking the source code, and not redirecting all mails through a custom script. Cheers V 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.

3 5