- Xymon - Xymon mailman web

Add page name to alert
by arjunp＠qualcomm.com 01 Aug '11

01 Aug '11

Hi , A newbie question: I have hosts categorized in pages (in hosts.cfg) and want the email alerts to show the page name in the subject. Can this be done? Thanks, Arjun

2 1

disk reporting issue on xymon 4.3.0-beta2
by tlewick＠tradebotsystems.com 31 Jul '11

31 Jul '11

Has anyone seen similar issues as below? Very rarely, we get false positives due to disk and process data coming from hosts being somewhat garbled. However, across several hundred hosts, it happens just often enough to be annoying. Below is an example of the disk issue from one of our xymon clients. As you can see, the disks were actually not above 30% utilized, and the alert cleared the next cycle. Just wondering if this has been resolved in later xymon versions? We are running xymon 4.3.0-0.beta2 Wed Jul 6 08:0]:30 CDT 2011 - Filesystems NOT ok 22% / (102738628% used) has reached the PANIC level (97%) 29% /boot (351664% used) has reached the PANIC level (97%) Filesystem ] 1]24-blocks Used Available Capacity Mounted on /dev/sda7 137886784 28143896 102738628 22% / /dev/sda6 521064 142932 351664 29% /boot Next update cycle, everything is fine. Wed Jul 6 08:11:31 CDT 2011 - Filesystems OK Filesystem 1024-blocks Used Available Capacity Mounted on /dev/sda7 137886784 28144080 102738444 22% / /dev/sda6 521064 142932 351664 29% /boot

4 9

Payed support
by jef.jagers＠thomsonreuters.com 31 Jul '11

31 Jul '11

Hi Hendrik, Jeff, Although my google search probably provided me with an answer to my question I wanted to ask you just to make sure. Is there any payed support available for xymon? Regards, Jef Jagers

2 1

Patch: rrd disk fix
by malcolm.hunter＠gmx.com 30 Jul '11

30 Jul '11

Hi, This is a patch to fix a bug with parsing of disk data for RRD graphing. The original code assumed that if the drive letter was longer than one character, the system was actually a UNIX system. In fact, this column also holds the directory where volumes can be mounted - just like with UNIX systems. The patch removes this restriction - so it now only checks if there's a '/' at the start of the first column. Regards, Malcolm Index: xymond/rrd/do_disk.c =================================================================== --- xymond/rrd/do_disk.c (revision 6701) +++ xymond/rrd/do_disk.c (working copy) @@ -103,8 +103,7 @@ * So check if there's a slash in the NT filesystem letter - if yes, * then it's really a Unix system after all. */ - if ( (dsystype == DT_NT) && (*(columns[5])) && - ((strchr(columns[0], '/')) || (strlen(columns[0]) > 1)) ) + if ( (dsystype == DT_NT) && (*(columns[5])) && (strchr(columns[0], '/')) ) dsystype = DT_UNIX; switch (dsystype) {

2 1

upgrading to 4.3.3 on proxy, having issues.
by Paul.Root＠qwest.com 29 Jul '11

29 Jul '11

I have a proxy server that was running 4.2.3, and I upgraded to 4.3.3 The proxy came up and is updating the primary server. However, the proxy is also running the server on port 1985, and it's not updating. I've been changing the environment variables from BB... to XYMON... (BBSERVERLOGS becomes XYMONSERVERLOGS) and the commands from hobbit... and bb... to xymon... (bbgen becomes xymongen, etc). I'm seeing in the following error in xymon-display.log: xymon-display.log:2011-07-29 16:02:02 Failed to load current Xymon status, aborting page-update xymon-display.log:2011-07-29 16:03:03 Failed to load current Xymon status, aborting page-update xymon-display.log:2011-07-29 16:04:03 Failed to load current Xymon status, aborting page-update xymon-display.log:2011-07-29 16:05:03 Failed to load current Xymon status, aborting page-update xymon-display.log:2011-07-29 16:08:21 Failed to load current Xymon status, aborting page-update xymon-display.log:2011-07-29 16:09:23 Failed to load current Xymon status, aborting page-update It's got to be some communication between xymond and xymongen right? Any ideas? Thanks, Paul. $ ps -ef |grep xymon xymon 25002 1 0 16:08 ? 00:00:00 /usr/lib64/xymon/server/bin/xymonlaunch --config=/usr/lib64/xymon/server/etc/tasks.cfg --env=/usr/lib64/xymon/server/etc/xymonserver.cfg --log=/var/log/xymon/xymonlaunch.log --pidfile=/var/log/xymon/xymonlaunch.pid xymon 25003 25002 0 16:08 ? 00:00:00 xymond --listen=0.0.0.0:1985 --pidfile=/var/log/xymon/xymond.pid --restart=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-file=/usr/lib64/xymon/server/tmp/hobbitd.chk --checkpoint-interval=600 --log=/var/log/xymon/xymond.log --admin-senders=127.0.0.1 204.155.141.230 --store-clientlogs=!msgs xymon 25004 25002 0 16:08 ? 00:00:00 /usr/lib64/xymon/server/bin/bbproxy --hobbitd --bbdisplay=127.0.0.1:1985,207.225.133.169,204.155.141.212 --listen=0.0.0.0 1984 --report=stnxymproxy.bbproxy --no-daemon --pidfile=/var/log/xymon/bbproxy.pid xymon 25107 1 0 16:08 ? 00:00:00 sh -c vmstat 300 2 1>/usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.25013 2>&1; mv /usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy.25013 /usr/lib64/xymon/server/tmp/xymon_vmstat.stnxymproxy xymon 25108 25107 0 16:08 ? 00:00:00 vmstat 300 2 xymon 25110 25002 0 16:08 ? 00:00:00 xymond_channel --channel=stachg --log=/var/log/xymon/history.log xymond_history xymon 25111 25002 0 16:08 ? 00:00:00 xymond_channel --channel=page --log=/var/log/xymon/page.log xymond_alert --checkpoint-file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-interval=600 xymon 25112 25002 0 16:08 ? 00:00:00 xymond_channel --channel=client --log=/var/log/xymon/clientdata.log xymond_client xymon 25113 25002 37 16:08 ? 00:00:42 xymond_channel --channel=status --log=/var/log/xymon/rrd-status.log xymond_rrd --rrddir=/var/lib/xymon/rrd xymon 25114 25002 42 16:08 ? 00:00:48 xymond_channel --channel=data --log=/var/log/xymon/rrd-data.log xymond_rrd --rrddir=/var/lib/xymon/rrd xymon 25115 25002 0 16:08 ? 00:00:00 xymond_channel --channel=clichg --log=/var/log/xymon/hostdata.log xymond_hostdata xymon 25124 25112 0 16:08 ? 00:00:00 xymond_client xymon 25125 25110 0 16:08 ? 00:00:00 xymond_history xymon 25139 25111 0 16:09 ? 00:00:00 xymond_alert --checkpoint-file=/usr/lib64/xymon/server/tmp/alert.chk --checkpoint-interval=600 Paul Root - Engineer III - Qwest is becoming CenturyLink This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

1 0

Analysis.cfg CLASS syntax?
by betsy.schwartz＠gmail.com 29 Jul '11

29 Jul '11

Figured out my include problem issues but still stuck on using CLASS in analysis.cfg should this work? > also, I'm failing utterly to get the CLASS syntax to work in analysis.cfg. > > I've got some classes set up and they works fine in client-local.cfg > but analysis.cfg does not see to see anything with CLASS > For example I have in hosts.cfg > > 10.100.1.60 db3.example.com # CLASS:db ntp > 10.100.1.61 db4.example.com # CLASS:db ntp > > I'm using the db CLASS in client-local.cfg and it's fine, does the > right thing. But If I start a section in analysis.cfg with > HOST=%^db[2|3|4|5|6|8].example.com everything works fine. > > But if I change the section to > CLASS=db > > nothing happens. Is that the right syntax? Thanks for any clues

2 2

post xymon 4.3.3 upgrade issue
by tlewick＠tradebotsystems.com 29 Jul '11

29 Jul '11

I recently updated from xymon-4.3.0-beta2 to 4.3.3. So far everything is looking/acting good. There is one minor issue that I'm not sure how to resolve. The menu, the one saying Views, Reports, Administration, & Help, shows on all pages except if you drill down to a specific host/test page, i.e. hostabc:disk. I made sure to add FollowSymLinks to the $BBSERVERROOT/cgi-bin and $BBSERVERROOT/cgi-secure statements in the correct apache configuration file. Any ideas what else I need to modify to get the menu to display on the host test pages? Thanks, Taylor

3 4

bbwin test results not showing up in xymon
by utadavidb＠yahoo.com 29 Jul '11

29 Jul '11

I've been debugging an issue and have had no success in resolving it. I'm using a custom test with BBWin 0.12 installed on Windows 2008 R2 server. My test leaves it's results in the designated tmp directory and BBWin picks up the results and deletes them from the folder but the results never get to the xymon server. The results do not show up as a column for the host nor do I get a ghost report. I find nothing in the server logs or the client logs to give my any help. The server is xymon 4.2.0 but I've also tried it against a xymon 4.2.3 instance that I have running. The usual client side tests (cpu, disk, etc) are reporting as expected so that indicates that the client is talking to the server. These tests are currently working properly on a Windows 2003 server (that is about to be taken out of service) with an older xymon client. Here's my bbwin configuration file: <?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="timer" value="300" /> <setting name="bbdisplay" value="xymonserve.mydomain.com:1984" />  <setting name="usepager" value="true" /> <setting name="bbpager" value="xymonserve.mydomain.com:1984" /> <setting name="pagerlevels" value="red purple" />    <setting name="mode" value="local" /> <setting name="configclass" value="win32" /> <setting name="autoreload" value="true" /> <setting name="timer" value="1m" /> <load name="cpu" value="cpu.dll" /> <load name="disk" value="disk.dll" /> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.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="4" /> <setting name="logpath" value="C:\Progra~2\BBWin\logs\BBWin.log" />  <setting name="logreportfailure" value="true" /> </bbwin> <cpu>  <setting name="alwaysgreen" value="false" /> <setting name="default" warnlevel="80%" paniclevel="95%" /> </cpu> <disk>  <setting name="alwaysgreen" value="false" />  <setting name="default" warnlevel="90%" paniclevel="95%" /> <setting name="E" warnlevel="90%" paniclevel="95%" /> <setting name="C" warnlevel="90%" paniclevel="95%" />   <setting name="remote" value="false" />  <setting name="cdrom" value="false" /> </disk> <externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load value="C:\Progra~2\PillarWatch\PillarMSGS.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarTSK.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarNFS.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarSAN.exe" timer="2m" /> <load value="C:\Progra~2\PillarWatch\PillarHDWR.exe" timer="2m" /> </externals> <memory>  <setting name="alwaysgreen" value="false" /> <setting name="physical" warnlevel="95%" paniclevel="98%" /> <setting name="page" warnlevel="80%" paniclevel="90%" /> </memory> <msgs> <setting name="delay" value="30m" /> <match logfile="sys" type="err" alarmcolor="green" /> <match logfile="sys" type="warn" alarmcolor="green" /> <match logfile="app" type="err" alarmcolor="green" /> <match logfile="app" type="warn" alarmcolor="green" />  </msgs> <procs>  </procs> <svcs> <setting name="alwaysgreen" value="false" /> <setting name="alarmcolor" value="yellow" /> <setting name="autoreset" value="false" /> <setting name="Microsoft Forefront Client Security State Assessment Service" value="=started" autoreset="false" alarmcolor="red" />  <setting name="Big Brother Hobbit Client" value="=started" autoreset="false" alarmcolor="red" /> </svcs> <uptime> <setting name="delay" value="60m" /> <setting name="alarmcolor" value="yellow" /> </uptime> </configuration> here's what my registry entries look like: binpath REG_SZ C:\ProgramFiles(x86)\BBWin\bin etcpath REG_SZ C:\Program Files(x86)\BBWin\etc hostname REG_SZ server1.mydomain.com tmppath REG_SZ C:\Program Files(x86)\BBWin\ext Note: I changed the tmppath from the default "tmp" - the test results are written to the ext directory Here's a sample output of a test: server50.mydomain.com:green Wed 20 9:45:22 2011 [server50.mydomain.com] <center><br>No current messages.</center> Note: The test is being run on server1 but it is testing some functionality on server50 (which is an appliance that can't run xymon client) and reporting it as server50. If anyone can shed any light on this issue I would appreciate it. David B

2 1

Green status during a total blackout
by linuxmasterjedi＠free.fr 29 Jul '11

29 Jul '11

Hi, My Xymon server (running Hobbit 4.2.2) has been shut down during 6 hours. When the power came back, Xymon came back too. I've checked all monitored equipment, everything was green during the past 6h. I was expecting purple or white color because no data has been reported during the time. Is that a bug or a setting I could adjust ? Thanks.

8 10

post xymon 4.3.3 upgrade issue
by tlewick＠tradebotsystems.com 29 Jul '11

29 Jul '11

Shoot, would the menu fail to display on those pages if the rewrite rules aren't working? From: Taylor Lewick Sent: Friday, July 29, 2011 9:18 AM To: xymon at xymon.com Subject: post xymon 4.3.3 upgrade issue I recently updated from xymon-4.3.0-beta2 to 4.3.3. So far everything is looking/acting good. There is one minor issue that I'm not sure how to resolve. The menu, the one saying Views, Reports, Administration, & Help, shows on all pages except if you drill down to a specific host/test page, i.e. hostabc:disk. I made sure to add FollowSymLinks to the $BBSERVERROOT/cgi-bin and $BBSERVERROOT/cgi-secure statements in the correct apache configuration file. Any ideas what else I need to modify to get the menu to display on the host test pages? Thanks, Taylor

1 0