- Xymon - Xymon mailman web

custom script run interval
by deepakdeore2004＠gmail.com 24 Apr '13

24 Apr '13

I have a custom script setup on client side, which I want to run on every 24 hours and i don't want to change the default lifetime for other tests. Used below line but still after 30 mins it is going into purple. $BB $BBDISP "status+25h $MACHINE.$COLUMN $COLOR `date` `echo -e "Daily status: \ \n$(cat /tmp/status.log) "`"

5 8

xymon mail service
by minaqva＠hotmail.com 24 Apr '13

24 Apr '13

Hello, I installed xymon server and xymon clients and everything works fine. Now I want to get mail notification when something goes wrong. I've added the following lines to my /home/xymon/server/etc/alerts.cfg, but I don't get any mails. HOST=host1 at domain1.com SERVICE=cpu,disk,memory,conn MAIL minaqva at hotmail.com REPEAT=20 RECOVERED In the /var/log/xymon/notifications.log I found : Tue Apr 23 08:17:53 2013 host1 at domain1.com.cpu (173.254.244.156) minaqva at hotmail.com[23] 1366719473 200 Tue Apr 23 08:37:56 2013 host1. at domain1.com.cpu (173.254.244.156) minaqva at hotmail.com[23] 1366720676 200 4449 I've done some researching and I found out that I need to setup mail server on the same machine where is xymon server. I don't know how to do that to work well with xymon, or what mail address should I put in alerts.cfg. I also don't know what mail server is required for xymon. Please help me.

2 1

Xymon 4.3.11 released
by henrik＠hswn.dk 23 Apr '13

23 Apr '13

Hi Matt, absolutely correct - and an embarassingly silly bug. This patch should cure it - I'll have to do a 4.3.12 release for this, so you may want to wait for that. Thanks for reporting it. Regards, Henrik On 22-04-2013 23:03, Matt Goebel wrote: > > Hopefuly I have done this correctly. Let me know if I need to > do something else. > > This GDB was configured as "sparc-sun-solaris2.10". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /data/src/xymon/xymon-4.3.11/xymongen/xymongen...done. > [New LWP 1] > [Thread debugging using libthread_db enabled] > [New Thread 1 (LWP 1)] > Core was generated by `./xymongen'. > Program terminated with signal 6, Aborted. > #0 0xfeecebd4 in _lwp_kill () from /lib/libc.so.1 > (gdb) bt > #0 0xfeecebd4 in _lwp_kill () from /lib/libc.so.1 > #1 0xfee67bb8 in raise () from /lib/libc.so.1 > #2 0xfee429f8 in abort () from /lib/libc.so.1 > #3 0x00031cc0 in sigsegv_handler (signum=11) at sig.c:57 > #4 <signal handler called> > #5 0xfee32d50 in strlen () from /lib/libc.so.1 > #6 0xfee9f4a0 in _ndoprnt () from /lib/libc.so.1 > #7 0xfeea1870 in sprintf () from /lib/libc.so.1 > #8 0x0001b754 in load_state (sumhead=0x62a30 <dispsums>) at loaddata.c:512 > #9 0x00016228 in main (argc=1, argv=0xffbffccc) at xymongen.c:592 > > Thanks, > Matt > > And now a bit of polka music by "=?ISO-8859-1?Q?Henrik_St=F8rner?=" >> >> Hi Matt, >> >> if you could provide me with a trace of where it dumps core, then I >> would very much like to track it down. >> >> You need the 'gdb' tool to get the stacktrace, see >> http://www.xymon.com/xymon/help/known-issues.html#bugreport >> >> >> Thanks, >> Henrik >> >> >> On 22-04-2013 17:38, Matt Goebel wrote: >>> >>> Hi, >>> >>> Not sure where I should post this, but I upgraded to 4.3.11 today >>> on Solaris 10 sparc and everything works great except for xymongen >>> which coredumps. I ended up using the 4.3.10 binary for xymongen >>> to get everything working again. >>> >>> Thanks, >>> Matt >>> >>> And now a bit of polka music by "=?ISO-8859-1?Q?Henrik_St=F8rner?=" >>>> >>>> Hi, >>>> >>>> I have just released version 4.3.11 of Xymon. This release fixes a >>>> critical bug, which has caused crashes and other unwanted behaviour of >>>> the xymond daemon. >>>> >>>> Upgrading your Xymon server is recommended. >>>> >>>> >>>> Full list of changes: >>>> >>>> * Fix wrong file permissions when installing >>>> * Linux client: Fix handling of root filesystem when mounted on >>>> "/dev/root" >>>> * trends webpage: Fix case where hostname disappears after zoom. >>>> * FreeBSD client: Memory patch for FreeBSD 8.0+ >>>> * xymond_alert: Fix problem with UNMATCHED rules triggering when >>>> there are actual recipients, but their alerts are suppressed due >>>> to a REPEAT setting not having expired. >>>> * xymond_rrd: Dont crash if called with an empty status/data message >>>> * xymond_channel: Report cause when channel-child exits/crashes >>>> * xymongen: Geneate an overview page with only reds (like non-green) >>>> * xymongen: Optionally define env. variable BOARDFILTER to select >>>> hosts/tests included in the generated pages >>>> * links: Add pdf, docx and odt as known document formats >>>> * Fix potential crashes after an alert cookie expired >>>> * Fix potential crash after deleting/renaming a host >>>> * Speedup loading of the hosts.cfg file, noticeable with very >>>> large hosts.cfg files (100.000+ hosts) >>>> >>>> >>>> Currently only the source archive is available. Binary packages will >>>> show up in a couple of days. >>>> >>>> >>>> Regards, >>>> Henrik >>>> _______________________________________________ >>>> Xymon mailing list >>>> Xymon at xymon.com >>>> http://lists.xymon.com/mailman/listinfo/xymon >>>> >>> >>> >> > >

1 1

New monitoring script on Xmonton - db_cpu.ksh
by a.chervonets＠cominder.eu 23 Apr '13

23 Apr '13

Good news. Had reviewed the script. There may be one problem in that lines: -- for PROC in $(ps -efa | grep $DB | awk '{ print $2 }') -- You do just grep, but imagine there may be instances like: MYDB MYDB1 MYDB12 or NOMYDB So it will count MYDB numbers for MYDB1, MYDB12 and NOMYDB too We should make grepping more intelligent, because oracle processes may be listed like: ora_j000_MYDB oracleMYDB (LOCAL=NO) ora_ckpt_MYDB and so on Best regards, Andrey Chervonets ---------------------- CoMinder Ltd. http://www.cominder.eu/ Mobile: +371 26517848 Fax: +371 66066346 On 01.03.2013 13:00, xymon-request at xymon.com wrote: > Message: 10 > Date: Fri, 1 Mar 2013 14:40:58 +0800 > From: Vernon Everett<everett.vernon at gmail.com> > To: Xymon mailinglist<xymon at xymon.com> > Subject: [Xymon] New monitoring script on Xmonton > Message-ID: > <CAGo4kcYUaYJ8TSjrs4xf7pNzptsB3vk3B5omLAae_M-2jtWokg at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi all > > I have just put something together to monitor Oracle database CPU usage. > http://www.xymonton.org/monitors:db_cpu.ksh

4 5

Xymon Log Retrieval
by Nick＠Pettefar.com 23 Apr '13

23 Apr '13

Is there a doco anywhere explaining the log file retrieval mechanism? I want to use Xymon to fetch /etc/passwd files so that I can check for unwanted/unnoticed changes. Nick Dublin

8 11

wrong values in RRD
by p3yeung＠gmail.com 22 Apr '13

22 Apr '13

I am using xymon 4.3.10. My xymon client sends 2 values to the xymon server, disk_free = 10404175872 disk_free_limit = 1000000000 The values displayed on the dashboard are correct. But xymon server stores a negative value for disk_free and zero for disk_free_limit. How can I make xymon stores the proper value to RRD? <ds> <name> diskfree </name> <type> DERIVE </type> <minimal_heartbeat> 600 </minimal_heartbeat> <min> NaN </min> <max> NaN </max>  <last_ds> 10404155392 </last_ds> <value> -6.7819016393e+04 </value> <unknown_sec> 0 </unknown_sec> </ds> <ds> <name> diskfreelimit </name> <type> DERIVE </type> <minimal_heartbeat> 600 </minimal_heartbeat> <min> NaN </min> <max> NaN </max>  <last_ds> 1000000000 </last_ds> <value> 0.0000000000e+00 </value> <unknown_sec> 0 </unknown_sec> </ds> Thanks P3

2 1

Xymon 4.3.11 released
by henrik＠hswn.dk 21 Apr '13

21 Apr '13

Hi, I have just released version 4.3.11 of Xymon. This release fixes a critical bug, which has caused crashes and other unwanted behaviour of the xymond daemon. Upgrading your Xymon server is recommended. Full list of changes: * Fix wrong file permissions when installing * Linux client: Fix handling of root filesystem when mounted on "/dev/root" * trends webpage: Fix case where hostname disappears after zoom. * FreeBSD client: Memory patch for FreeBSD 8.0+ * xymond_alert: Fix problem with UNMATCHED rules triggering when there are actual recipients, but their alerts are suppressed due to a REPEAT setting not having expired. * xymond_rrd: Dont crash if called with an empty status/data message * xymond_channel: Report cause when channel-child exits/crashes * xymongen: Geneate an overview page with only reds (like non-green) * xymongen: Optionally define env. variable BOARDFILTER to select hosts/tests included in the generated pages * links: Add pdf, docx and odt as known document formats * Fix potential crashes after an alert cookie expired * Fix potential crash after deleting/renaming a host * Speedup loading of the hosts.cfg file, noticeable with very large hosts.cfg files (100.000+ hosts) Currently only the source archive is available. Binary packages will show up in a couple of days. Regards, Henrik

1 0

snmp data question devmon/xymon
by tlewick＠apsaranetworks.com 19 Apr '13

19 Apr '13

This post could also go to devmon, but I've noticed the devmon mailing list is basically just about inactive. I set up devmon for multinode, so that its using mysql as a backend database. Everything appears to be working, but I thought it would also store the actual polled snmp data in the table test_data. All of the tables are being populated but that one. Does anyone know how to get devmon to store not just the config (templates, hosts/devices, thresholds, etc) but also the polled snmp data into the mysql database? Thanks, Taylor

1 0

Trunkated data from procs (OPEN)
by oyvind.bjorge＠telenor.com 19 Apr '13

19 Apr '13

Thank you Chris! Øyvind From: Chris.Morris at rwe.com [mailto:Chris.Morris at rwe.com] Sent: 19. april 2013 13:46 To: Bjørge Øyvind; xymon at xymon.com Subject: RE: [Xymon] Trunkated data from procs (OPEN) You can stop the client sending that data (or any part of its output) by editing the ~/client/bin/xymonclient-<OS>.sh script and commenting out the relevant command section. ________________________________ From: xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com> [mailto:xymon-bounces at xymon.com] On Behalf Of oyvind.bjorge at telenor.com<mailto:oyvind.bjorge at telenor.com> Sent: 19 April 2013 12:40 To: xymon at xymon.com<mailto:xymon at xymon.com> Subject: [Xymon] Trunkated data from procs (OPEN) I have a proc-test that is failing for one node because proc-test data is truncated. The server is configured with the default limit of 512K for (MAXMSG_CLIENT). Looking at the client_data for the active test, this is showing a complete ps-list, but it also seems like the total of client_data is over the limit of 512K. Looking at a historical test, it seem like the client_data is truncated at 512K and it matches the same spot in the ps-list. An obvious solution for this might be to increase the global parameter MAXMSG_CLIENT, but will be valid for all clients. Another possible solution, but not wanted, might be to change the client behavior to local handling. A third solution could be to reduce the amount of data sent by the client. Ex stop the netstat output, which for this client is quite long and something we don't generate alarms for today. Does anyone know if this is possible, and if so how? Anyone that has an better suggestion on how to solve this? Br, Øyvind **************************************************************************** The information contained in this email is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination or copying of the message or associated attachments is strictly prohibited. If you have received this email in error, please contact the sender by return email or call 01793 877777 and ask for the sender and then delete it immediately from your system.Please note that neither the RWE Group of Companies nor the sender accepts any responsibility for viruses and it is your responsibility to scan attachments (if any). *****************************************************************************

1 0

Trunkated data from procs (OPEN)
by oyvind.bjorge＠telenor.com 19 Apr '13

19 Apr '13

I have a proc-test that is failing for one node because proc-test data is truncated. The server is configured with the default limit of 512K for (MAXMSG_CLIENT). Looking at the client_data for the active test, this is showing a complete ps-list, but it also seems like the total of client_data is over the limit of 512K. Looking at a historical test, it seem like the client_data is truncated at 512K and it matches the same spot in the ps-list. An obvious solution for this might be to increase the global parameter MAXMSG_CLIENT, but will be valid for all clients. Another possible solution, but not wanted, might be to change the client behavior to local handling. A third solution could be to reduce the amount of data sent by the client. Ex stop the netstat output, which for this client is quite long and something we don't generate alarms for today. Does anyone know if this is possible, and if so how? Anyone that has an better suggestion on how to solve this? Br, Øyvind

2 1