- Xymon - Xymon mailman web

hobbitdxboard returns invalid xml when test is disabled
by jason.jones＠codelsoftware.com 23 Jul '14

23 Jul '14

Hi Henrick, Just to confirm this has fixed the issue. Sorry for the delay but unfortunately we had other problems with the server in question which meant the test in question was clear. Kind Regards, Jason. Jason Jones Analyst/Developer From: Henrik Størner <henrik at hswn.dk> To: Jason Jones <jason.jones at codelsoftware.com> Cc: Xymon mailinglist <xymon at xymon.com> Date: 17/07/2014 20:51 Subject: Re: [Xymon] hobbitdxboard returns invalid xml when test is disabled > I have applied the patch but the issue still seems to be the same. Yep, found out I could reproduce it here. This should fix it for good. Regards, Henrik ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________[attachment "xymond-xboard-v2.diff" deleted by Jason Jones/CODEL] Codel Software Ltd Unit 1C Charnwood Park Bridgend CF31 3PL +44 (0)1656 750 858 +44 (0)1656 648 649 info at codelsoftware.com http://www.codelsoftware.com Follow Us: @codel_software at activabsence Linkedin http://www.activabsence.co.uk Registered in Wales No. 5838660 DELIVERING QUALITY: At Codel Software we are committed to delivering quality software, services and client interactions. We have demonstrated this through quality audits and customer satisfaction. Codel Software is an ISO 9001:2008 certified company. CONFIDENTIALITY NOTICE: This message is confidential and for the use only of the intended recipient. If you receive the message in error you are not entitled to disseminate, copy or use the contents in any way. In such circumstances please forward the message back to the sender. WARNING :While Codel Software takes steps to prevent computer viruses from being transmitted via electronic mail attachments we cannot guarantee that attachments do not contain computer virus code. You are therefore strongly advised to undertake anti virus checks prior to accessing the attachment to this electronic mail. Codel Software grants no warranties regarding performance use or quality of any attachment and undertakes no liability for loss or damage howsoever caused. If you do not want to receive similar communications by e-mail from Codel Software, please reply to this e-mail with 'remove' in the subject line. Help the environment –please don't print this email unless you really need to! ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________

1 0

how to: 4.3.10 to 4.3.17
by bakgat8＠hotmail.com 22 Jul '14

22 Jul '14

I compiled and have been running 4.3.10 How to upgrade to 4.3.17 without doing any more work than necessary and without losing current data & config. Thanks much bakkies

2 2

Could not fork checkpoint child:Cannot allocate memory
by ragonlan＠gmail.com 22 Jul '14

22 Jul '14

After upgrading from xymon version 4.3.12 to 4.3.17 xymond daemon memory grow without any limit. After a 2 or 3 days this messages appear in logs: 2014-07-17 16:27:46 Setup complete 2014-07-18 04:16:49 Flapping detected for web.int:http - 10 changes in 868 seconds 2014-07-18 04:16:49 Flapping detected for web.int:tomcat - 10 changes in 868 seconds 2014-07-18 04:18:23 Flapping detected for web.int:http - 10 changes in 892 seconds 2014-07-18 04:18:23 Flapping detected for web.int:tomcat - 10 changes in 892 seconds 2014-07-18 18:25:44 Flapping detected for web.int:http - 10 changes in 808 seconds 2014-07-18 18:25:44 Flapping detected for web.int:tomcat - 10 changes in 808 seconds 2014-07-18 23:40:53 Could not fork checkpoint child:Cannot allocate memory 2014-07-18 23:50:54 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 00:00:55 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 00:10:56 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 00:20:57 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 00:30:58 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 00:40:59 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 00:51:00 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 01:01:01 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 01:11:02 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 01:21:03 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 01:31:04 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 01:41:05 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 01:51:06 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 02:01:07 Could not fork checkpoint child:Cannot allocate memory 2014-07-19 02:11:08 Could not fork checkpoint child:Cannot allocate memory ¿Anybody knows how to avoid this problem? If I don't reboot xymon it crash.

2 2

system reboot email alert
by Sue.Bauer-Lee＠Multiplan.com 12 Jul '14

12 Jul '14

Hello All! Times have changed a bit in the infrastructure environment such that many have a large contingent of virtual machines and blades. These hosts tend to reboot rather quickly, hence connectivity failures tend to not get noticed. I have a request on the table to send an email alert with a specific subject line to indicate that a host has rebooted. I've seen a few posts over the years regarding requests to alert for system reboots. I also saw a post or two about adding a dynamic column capability. Some responses suggested an external script to accomplish the task of emailing an alert. I'm asking the question again because as I peruse the analysis.cfg and review the rules, I know I can issue an email alert for PROC and DISK. That begs the question of 'why can't I issue an email alert for UP'? I'm fine with the 'yellow' on CPU test for recent reboot, but since it also includes load changes, I'm not interested in a generic email for either one when they occur. If I already can, how?? And if not, suggestions for a simple approach? I'm not exactly getting the desired results server-wide with an external script that should just send an email for a CPU status color=yellow without interfering with our other configured alerts. :( Is someone already successfully conquering this task? NOTICE OF CONFIDENTIALITY: This message and any attachments contains confidential information belonging to the sender intended only for the use of the individual or entity named above. If you are not the intended recipient, be advised that copying, disclosure or reliance upon the contents is strictly prohibited. If you have received this message in error please notify the sender immediately. ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________

5 8

Can client extension scripts use client-local.cfg data passed back to client?
by rlhamil2＠gmail.com 11 Jul '14

11 Jul '14

I'm gathering that said data ends up in $XYMONCLIENTHOME/tmp/logfetch.$MACHINEDOTS.cfg. Would it hurt anything to put (on the server) data in addition to the lines defined in the man page? Would it make it back to the above file? And if so, can a naming convention be recommended for user-defined lines that should avoid conflict with any future official lines? (maybe names that begin with site_ or something like that?) And if that's not all crazy...it would be cool if the library module to fetch the client-local.cfg for a host could check the timestamp on the file, and if changed, reload it (freeing all the old data structures first, so as not to leak memory, of course!) That way, without restarting the server, one could replace the client-local.cfg file on the server and have client log, file, and extension script behavior altered accordingly. Having used Big Brother for many years, the ability of Xymon to pass updates and _some_ client control information to the client, without one inventing one's own backchannel (using ssh or whatever), sounds like it could make life _much_ simpler in terms of centralizing the control of clients and server alike. So naturally I want to take that to its logical extreme. :-) But so far, I haven't read enough of the code to really have a good handle on just what might be possible, let alone normal enough not to be too fragile.

3 2

stop monitoring memory
by didds3＠yahoo.co.uk 10 Jul '14

10 Jul '14

Hobbit version 4.2.3 in both server and client. client has the MEMORY checks commented out of localclient.cfg - memory alerts/info was still showing on the server. Then a bit iof dgiiging showed that vmstat was still being run in hobbitclient-linux.sh, so the appropriate ;ines were commented out. vmstat is no longer being run on the client. But the server ( after "drop ,<client> memory" ) still report memory from this client. what else may be reporting this then? i am assuming some server side thing but I can;t see where from? didds

2 4

stop monitoring memory
by didds3＠yahoo.co.uk 10 Jul '14

10 Jul '14

thanks jeremy... server OS is CentOS release 5.5 client OS is CentOS release 6.4 I did find some gumf about uising a bb-hosts entry XXX.XXX.XXX.XXX client # NOCOLUMNS:memory to at least avoid showing the reports/monitor but that made absolutely zero difference so i have no idea what on earth that is about :-) cheers ian ________________________________ From: Jeremy Laidman <jlaidman at rebel-it.com.au> To: Ian Diddams <didds3 at yahoo.co.uk> Cc: "xymon at xymon.com" <xymon at xymon.com> Sent: Thursday, 10 July 2014, 4:48 Subject: Re: [Xymon] stop monitoring memory On 9 July 2014 20:43, Ian Diddams <didds3 at yahoo.co.uk> wrote: Oh - as I understand this is in local mode. > My understanding is that in local mode, the memory data is analysed and sent by xymond_client. Perhaps you could run this with the "--debug" switch to see what's going on. Also, you could use a xymond_channel command on the server to watch the memory status messages come in, to check whether they're coming from the client. Something like: xymond_channel --channel=status --filter='name-of-host.*\|memory\|' cat As far as I can tell from reviewing the code, the xymond_client program gets its memory numbers from the client data, but it uses different section names depending on the OS. For Linux, it looks only in [free], for FreeBSD it looks in [meminfo] and [swapinfo], and for Solaris it looks in [memory], [swap] and [swaplist]. What OS are you using? Cheers Jeremy

1 0

alerts
by NMaharaj＠tcta.co.za 10 Jul '14

10 Jul '14

<html><body>Hi, Im not receiving emails. This is the configuration in the alerts.cfg file. Please advise. HOST=* SERVICE=cpu,conn,disk,svcs,http,smtp,dns MAIL techsupport at xxxx.xx.xx DURATION>5 REPEAT=60 RECOVERED Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and automatically archived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service (SaaS) for business. Mimecast Unified Email Management (UEM) offers email continuity, security, archiving and compliance with all current legislation. To find out more, visit http://www.mimecast.co.za/uem.</body></html>

3 7

alert IGNORE
by sidiney＠redix.com.br 10 Jul '14

10 Jul '14

Hello, I need to ignore a message on xymon Critical entries in /var/log/secure red -> error='' On server log: Jun 25 09:21:14 mailserver saslauthd[28318]: zmpost: url=' https://mailserver.domain.com.br:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap=" http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><change token="30213"/></context></soap:Header><soap:Body><AuthResponse xmlns="urn:zimbraAccount"><authToken>0_b4e7e2ade952b00a8028cf4e80d489c2b0138b8e_69643d33363a36666134643163352d626664302d343239352d626234302d3837306532346138336662353b6578703d31333a313430333837313637343034363b76763d313a303b747970653d363a7a696d6272613b</authToken><lifetime>172800000</lifetime><skin>serenity</skin></AuthResponse></soap:Body></soap:Envelope>', hti->error='' Sentinela configuration: /usr/lib/xymon/server/etc/client-local.cfg log:/var/log/secure:10240 ignore saslauthd.*\[.*\]:.* ignore .*hti.*error.* ignore .*hti.* ignore ti->error.* But even so the messages are still appearing, there is something more that should be done?

2 2

custom graphs
by Paul.Root＠CenturyLink.com 09 Jul '14

09 Jul '14

Hi, This is one of my least favorite things of xymon. It really shouldn't be this hard. I've had a script that pulls the %mem of certain processes on various machines. Right now, I have 3 separate groups of machines with different processes being watched. The purpose is to track memory leaks. Previously, I had the script just put out a ps -eo 'pid,%mem,cmd' for the desired processes. Then others wanted a graph, so I've reformatted the output to be just a keyword (either the process name or a significant field of the arguments of the command). I get something that looks like this now: Process Memory Usage SA: 6.5 MBIM: 2.4 OI: 4.1 Process' alert levels are defined in /usr/local/etc/procmem.cfg When levels are exceeded, restarting of the process to free memory is recommended xymProcMem,v 1.7 2014/07/07 20:37:17 ptroot Exp ptroot $ My first iteration, I used <br> to separate the lines. That was a mistake, the source of the html showed them all on one line. I've changed to \n, and that to me should provide the proper output. However, looking at the rrd dump, I only get the first one: <rrd> <version> 0003 </version> <step> 300 </step>  <lastupdate> 1404828303 </lastupdate>  <ds> <name> SA </name> <type> GAUGE </type> <minimal_heartbeat> 600 </minimal_heartbeat> <min> NaN </min> <max> NaN </max>  <last_ds> 6.5 </last_ds> <value> NaN </value> <unknown_sec> 3 </unknown_sec> </ds> <ds> <name> xymProcMemv16201407 </name> <type> DERIVE </type> <minimal_heartbeat> 600 </minimal_heartbeat> <min> NaN </min> <max> NaN </max>  <last_ds> 50 </last_ds> <value> NaN </value> <unknown_sec> 3 </unknown_sec> </ds> My TEST2RRD looks like: TEST2RRD="cpu=la,disk,inode,...,nfmsgw=ncv,hpnasnapshot=ncv,ProcMemory=ncv" And the NCV definitions: NCV_hpnasnapshot="TotaldevicesinDB:GAUGE,Totalactivedevicesi:GAUGE,Totalinactivedevice:GAUGE,Totaldeviceswithout:GAUGE,Pctactive:GAUGE,Pctinactive:GAUGE,Pctnodriver:GAUGE,Activeattemptedsucc:GAUGE,Activeattemptedunsu:GAUGE,Activebutnotattempt:GAUGE,PctAttemptedsuccess:GAUGE,PctAttemptedunsucce:GAUGE,PctActivebutnotatte:GAUGE" NCV_ProcMemory="SA:GAUGE,MBIM:GAUGE,OI:GAUGE,MNS1:GAUGE,NMS1:GAUGE,NMS2:GAUGE,NMS11:GAUGE,NMS12:GAUGE,NMS13:GAUGE,NMS14:GAUGE,NMS15:GAUGE,TCMgmtEngine:GAUGE,TCTFTP:GAUGE,TCSyslog:GAUGE,SWIM:GAUGE" The hpnasnapshot graph works. I've been using it as an example. Obviously, without all the data in the rrd, there is no point in trying to get a graph to show. Any ideas from anyone? Thanks, Paul. Paul Root Lead Engineer CenturyLink Network Reliability Operations Center 600 Stinson Blvd, N.E. Flr 2N Minneapolis, MN 55413 Direct: (651)312-5207 Paul.Root at centurylink.com

3 3