- Xymon - Xymon mailman web

Strange ghost reports
by ejacobs＠thomaspublishing.com 24 Apr '12

24 Apr '12

I have two xymon servers (4.3.7) running, one here in Pennsylvania and one in New York. Both have "summary" lines at the end of their hosts.cfg files pointing to the other. In PA, the xymond button shows most, if not all, of the NY clients as ghosts, with the reporting IP being the IP of the PA hobbit server. NY doesn't have this problem. Anyone know why this might be happening? -- Eric Jacobs Thomas Publishing Company Infrastructure and operations Information Technology Group Phone: 215-494-7312 Email: ejacobs at thomaspublishing.com

2 2

Windows service monitoring
by Neil.Simmonds＠express-gifts.co.uk 24 Apr '12

24 Apr '12

Hi all, We are monitoring various Windows services using BBWin 0.12 in central mode reporting to a Xymon 4.3.4 server. In the analysis.cfg file for a number of servers we have the following type of entry, SVC SQLSERVERAGENT status=started startup=automatic As far as I can see from the analysis.cfg help that is exactly the correct format, however when this flags red, we get the following message, SQLSERVERAGENT is started/automatic - want started/automatic When I look down the list of processes SQLSERVERAGENT is clearly shown as stopped, SQLSERVERAGENT automatic stopped SQLSERVERAGENT Does anyone have any idea why the message is incorrect and if there is a way to fix it? Regards, Neil Simmonds Operation Analyst (Operations Support Group) Express Gifts Limited Express House Clayton Business Park Accrington Lancashire BB5 5JY T: 01254 303092 | E: neil.simmonds at Express-Gifts.co.uk Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority -------------- NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030

1 0

vCenter monitoring
by gendalia＠iastate.edu 24 Apr '12

24 Apr '12

What do people use for vCenter monitoring? -Tracy

3 2

Occasional issue with process listings
by tlewick＠tradebotsystems.com 23 Apr '12

23 Apr '12

Background, we have a xymon server that is monitoring roughly 700 devices, mix of windows and linux with some network devices, etc. Running Xymon 4.3.3 for several months now with no issues. No recent config changes, but recently I've seen an issue where a few of the linux clients (haven't noticed it on Windows clients) will have their process checks go red, and when you click on the process page it appears the client data is being truncated, thus most or all of the process checks are red. This only lasts for one cycle, then everything is back to green. Its happened maybe 5-10 times today. However, there are no entries in xymond.log regarding Oversize status message from client W.X.Y.Z truncated, etc. Is this a known issue with xymon?

2 2

.default. not working?
by jdustin＠usm.maine.edu 21 Apr '12

21 Apr '12

Using testip was the whole point, because I wanted to apply that tag to a bunch of hosts. I decided to add tags to host entries instead. I do not use FQDN, and wondered if that might have something to do with testip. Thanks for the suggestion though! Please forgive typos - sent from a mobile device On Apr 21, 2012, at 11:30, "Mark Mulligan <MMulligan at llbean.com>" <MMulligan at llbean.com> wrote: > Have you tried changing testip to noconn so that it does not try to resolve the IP address? The example in hosts.cfg does not use a testip. > > Thanks, > Mark > > -----Original Message----- > From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Jon Dustin > Sent: Monday, April 16, 2012 3:23 PM > Cc: xymon at xymon.com > Subject: =?utf-8?B?UmU6IFtYeW1vbl0gLmRlZmF1bHQuIG5vdCB3b3JraW5nPw====?> > Can anyone think of a way I can debug the processing of hosts.cfg? For some reason my ".default." entry is not being read correctly, and no matter what I try Xymon complains. > > Thanks for reading. > > Sent from a mobile device, please excuse any typos. > > > -----Original Message----- > From: Jon Dustin [jdustin at usm.maine.edu] > Received: Monday, 16 Apr 2012, 8:27 > CC: xymon at xymon.com [xymon at xymon.com] > Subject: =?utf-8?B?UmU6IFtYeW1vbl0gLmRlZmF1bHQuIG5vdCB3b3JraW5nPw====?> > > >>>> "Jon Dustin" <jdustin at usm.maine.edu> 2012-04-16T08:27:57.783283 >>> > Nope, still not working: > > 0.0.0.0 .default. # testip NOPROPRED:+if_load NOPROPYELLOW:+if_load > > (note - there are TABS on both sides of .default. - in case that makes a difference) > > Thanks for reading. > >>>> On 4/16/2012 at 3:08 AM, in message > <CALMep04wRHCuimkWdDEN868C3-KPyJH5FcwyshAOW-dpQASGOw at mail.gmail.com>, Steven Carr <sjcarr at gmail.com> wrote: >> Try... >> >> NOPROPRED:+if_load NOPROPYELLOW:+if_load >> >> That's what I have in mine and it works. >> >> Steve >> >> >> >> On 16 April 2012 03:04, Jon Dustin <jdustin at usm.maine.edu> wrote: >> >>> No, my .default. is all on one line. Very perplexing! >>> >>> -- >>> Jon Dustin - Network Specialist >>> University of Southern Maine >>> Portland, ME 207-780-4152 >>> >>>>>> Steve Holmes 04/15/12 8:15 PM >>> >>> Is the .default. really on 3 lines? If so, that is your problem. Put >>> it all on one line. >>> >>> Steve >>> >>> Wherever you go, there you are. >>> >>> On Apr 15, 2012, at 7:06 PM, "Jon Dustin" wrote: >>> >>>> Greetings - >>>> >>>> I'm currently running Xymon v4.3.7, and having troubles getting the >>> ".default." entry to work properly. Here is what I have configured: >>>> >>>> page devs Network Devices >>>> 0.0.0.0 .default. # testip NOPROPRED:if_load >>> NOPROPYELLOW:if_load >>>> (then a bunch of hosts below) >>>> >>>> It seems the .default. entry is ignored (status IS propagated >>>> upward), >>> *and* I see the following error in xymonnet: >>>> >>>> dnsresolve - internal error, name '' not in cache >>>> xymonnet: Cannot resolve IP for host >>>> >>>> Am I misunderstanding the ".default." entry? Thanks for anything >>>> you can >>> pass along. >>>> > > > -- > > Jon Dustin - Network Specialist > University of Southern Maine > Portland, ME 207-780-4152 > > > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon

1 0

.default. not working?
by jdustin＠usm.maine.edu 21 Apr '12

21 Apr '12

Can anyone think of a way I can debug the processing of hosts.cfg? For some reason my ".default." entry is not being read correctly, and no matter what I try Xymon complains. Thanks for reading. Sent from a mobile device, please excuse any typos. -----Original Message----- From: Jon Dustin [jdustin at usm.maine.edu] Received: Monday, 16 Apr 2012, 8:27 CC: xymon at xymon.com [xymon at xymon.com] Subject: Re: [Xymon] .default. not working? >>> "Jon Dustin" <jdustin at usm.maine.edu> 2012-04-16T08:27:57.783283 >>> Nope, still not working: 0.0.0.0 .default. # testip NOPROPRED:+if_load NOPROPYELLOW:+if_load (note - there are TABS on both sides of .default. - in case that makes a difference) Thanks for reading. >>> On 4/16/2012 at 3:08 AM, in message <CALMep04wRHCuimkWdDEN868C3-KPyJH5FcwyshAOW-dpQASGOw at mail.gmail.com>, Steven Carr <sjcarr at gmail.com> wrote: > Try... > > NOPROPRED:+if_load NOPROPYELLOW:+if_load > > That's what I have in mine and it works. > > Steve > > > > On 16 April 2012 03:04, Jon Dustin <jdustin at usm.maine.edu> wrote: > >> No, my .default. is all on one line. Very perplexing! >> >> -- >> Jon Dustin - Network Specialist >> University of Southern Maine >> Portland, ME 207-780-4152 >> >> >>> Steve Holmes 04/15/12 8:15 PM >>> >> Is the .default. really on 3 lines? If so, that is your problem. Put it >> all on one line. >> >> Steve >> >> Wherever you go, there you are. >> >> On Apr 15, 2012, at 7:06 PM, "Jon Dustin" wrote: >> >> > Greetings - >> > >> > I'm currently running Xymon v4.3.7, and having troubles getting the >> ".default." entry to work properly. Here is what I have configured: >> > >> > page devs Network Devices >> > 0.0.0.0 .default. # testip NOPROPRED:if_load >> NOPROPYELLOW:if_load >> > (then a bunch of hosts below) >> > >> > It seems the .default. entry is ignored (status IS propagated upward), >> *and* I see the following error in xymonnet: >> > >> > dnsresolve - internal error, name '' not in cache >> > xymonnet: Cannot resolve IP for host >> > >> > Am I misunderstanding the ".default." entry? Thanks for anything you can >> pass along. >> > -- Jon Dustin - Network Specialist University of Southern Maine Portland, ME 207-780-4152

2 1

xymond_filestore - appending to files?
by john.horne＠plymouth.ac.uk 20 Apr '12

20 Apr '12

Hello, I would like to use the 'xymond_filestore' command to append to files when receiving information from a 'data' channel. As far as I can see it cannot do this, but the code in xymond/xymond_filestore.c shows that 'data' messages are appended to a temporary file (in Xymon 4.3.7, xymond_filestore line 59). The file mode is passed as 'a', whereas for other information types (status, notes etc) it is 'w'. Unfortunately the temporary file is later renamed as the live file (line 78). Since the temporary file no longer exists, it cannot be appended to next time (so is created as a new file). The overall effect is that the information in the data files is overwritten by any new message. I am not sure why the file mode is 'a' in this instance when the file is later just renamed. Should perhaps the temporary file be 'copied' to the live file instead if the mode is 'a'? This would then allow appending to work, but would also require some mechanism for removing the file otherwise it might get large. I'm also unsure how the expiry time is suppose to work. I can see that it gets set on the file, but what then? Is there some process that later checks the times and removes 'expired' files? Thanks, John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001

2 2

Bug - xymon man page shows data parameter incorrectly
by john.horne＠plymouth.ac.uk 20 Apr '12

20 Apr '12

Hello, In Xymon 4.3.7 the 'xymon(1)' man page shows for the 'data' message type the arguments as: data HOSTNAME.DATANAME<newline><additional text> As far as I can tell this should be 'HOSTNAME.TESTNAME'. Attached are two patches to fix this (one for the 'man' page, the other for the HTML version). Both are just one-line patches. John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001

2 2

Purple storm
by Phil.Crooker＠orix.com.au 20 Apr '12

20 Apr '12

So, can you do DNS queries from the xymon server when DC3 & 4 are down? >>> "Poppy, Ben" 03/20/12 11:50 AM >>> So they are pointing to 2 DC's that stay up this entire time, we'll call them DC1 and DC2. Then we shutdown DR-DC3 and DR-DC4. When those servers are down, we begin to have issues. -----Original Message----- From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au] Sent: Monday, March 19, 2012 7:46 PM To: Poppy, Ben Cc: xymon at xymon.com Subject: Re: [Xymon] Purple storm On Tue, Mar 20, 2012 at 5:15 AM, Poppy, Ben wrote: > I have an interesting problem that happened last night. We are working > on a DR test. Part of that test includes shutting down some DC's in > our DR datacenter. When that happened, most tests that are initiated > from the xymon servers (http, dns, ssh, ftp, etc) to the monitored server went purple. For network tests, Xymon resolves the IP address from the servername (typically using DNS), and then uses that IP address to perform the test. The IP address in the hosts.cfg file is not normally used for network tests. So if your DNS fails, Xymon's network tests fail also. You can prevent this, and use the IP address supplied in hosts.cfg, by adding "testip" to each hosts.cfg entry that requires it. You can add it to a ".default." entry so that it applies to all hosts. J ______________________________________________________________________ The contents of this message may contain private, protected and/or privileged information. If you received this message in error, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained within. Please contact the sender and advise of the erroneous delivery by return e-mail or telephone. Thank you for your cooperation. _______________________________________________ Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

8 18

Upgrade steps
by poppy.ben＠marshfieldclinic.org 20 Apr '12

20 Apr '12

I see that there are some pretty clear upgrade steps when moving from Hobbit 4.2.x to Xymon 4.3.x, but are there any upgrade steps when moving from Xymon 4.3.4 to 4.3.7 by chance? Or will the make install not overwrite the customized configuration files (hosts.cfg, analysys.cfg, etc)? Thanks, -Ben ______________________________________________________________________ The contents of this message may contain private, protected and/or privileged information. If you received this message in error, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained within. Please contact the sender and advise of the erroneous delivery by return e-mail or telephone. Thank you for your cooperation.

2 2