March 2014 - Xymon - Xymon mailman web

status reports from systems without xymon-client
by JAlexander＠feeneywireless.com 27 Mar '14

27 Mar '14

All, I have systems I wish to monitor but it will not be possible to place a xymon-client on them. I can create a script on these systems (in LUA) to collect and send the needed data though. Is there an API by which I can pass the information without having to use the xymon executable? Thanks. John Alexander Network Administrator John.Alexander at feeneywireless.com<mailto:John.Alexander at feeneywireless.com> Feeney Wireless, LLC - PO Box 2549, Eugene, Oregon 97402 (Free) 800-683-4818 (P) 541-685-9045 (F) 541-284-0030 www.feeneywireless.com<http://www.feeneywireless.com/> [FW_Acronym_email]<http://feeneywireless.com/> This email transmission is intended only for the addressee shown above. It may contain information that is privileged, confidential or otherwise protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons other than the addressee is strictly prohibited! If you have received this email transmission in error please notify us immediately.

3 2

Last apt update: 1.3 day(s) ago Yellow
by mumubash＠gmail.com 27 Mar '14

27 Mar '14

Hello gents, Anyone can point me into the right direction in order to disable the `apt` check for last update date count please? Can't find it anywhere. Cheers!

2 2

localclient and file monitoring
by dirk.kastens＠uni-osnabrueck.de 27 Mar '14

27 Mar '14

Hi, it seems that file monitoring is not working with clients that are running in localmode (xymon-server 4.3.16). The client-local.cfg doesn't exist in the client directory. Entries in the server's client-local.cfg are ignored if the client is running in localmode. So, if I want to monitor files on a localmode client, I have to create the file logfetch.<client>.cfg in the client's BBTMP directory and enter the file: or log: entries there. Then file monitoring works. Can you change the client code, so that a localmode client can use its own client-local.cfg file? Dirk

1 0

ackloledge or disable
by xymon＠elysiria.fr 26 Mar '14

26 Mar '14

Hi all. My monitoring shows me some alarms that I cannot correct just now. Should I "acknoledge" them (and still see a red light in my report), or "disable" them (and stop seeing something is wrong)? What differences do you see between those 2? In which cases do you use one or the other one? Thanks. -- Christian

3 2

Strange disk test condition
by novosirj＠ca.rutgers.edu 26 Mar '14

26 Mar '14

Hi all, I run Xymon 4.3.12. I see I had an alert from a server earlier tonight at 99% of / full. However, it is 66% now and no evidence that this ever happened on the graph of that filesystem. Is it possible for a disk to fill for a very short period and never hit the graph? I don't know what could have even done that. -- ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences* || \\UTGERS |---------------------*O*--------------------- ||_// Biomedical | Ryan Novosielski - Sr. Systems Programmer || \\ and Health | novosirj at rutgers.edu - 973/972.0922 (2x0922) || \\ Sciences | OIT/EI-Academic Svcs. - ADMC 450, Newark `'

2 1

Have network tests report yellow instead of red?
by john.thurston＠alaska.gov 26 Mar '14

26 Mar '14

I must be blind, but I am unable to find a way to have a xymonnet test result go yellow instead of red. If I have the following line in my hosts.cfg: 0.0.0.0 foo.bar.com # telnet I'd like the telnet test to report yellow instead of red when the port test is not responding. I see I can prefix it with "?" to have it return clear instead of red, but how can I make it return yellow instead of red? -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska

2 1

Service smtp on hostname is not OK : Unexpected service response
by tawilcox＠fs.fed.us 25 Mar '14

25 Mar '14

We are getting yellow alerts for all SMTP tests in Xymon. The error given is "Service smtp on hostname is not OK : Unexpected service response". This is a new installation and all of the SMTP servers have been yellow since Xymon was started. Telnet into the server gives the response: "220 sv62.r1.fs.fed.us ESMTP Service ready at Mon, 24 Mar 2014 12:23:42 -0600". The hosts file is from Big Brother. All SMTP tests are SMTP.S. We tried commenting out any line in the [SMTP] section that starts with "Send", but that didn't change anything. There is nothing recent in the archives about this. Any suggestions? Ted This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.

2 1

Xymon Digest, Vol 38, Issue 21
by s.watkins＠nhm.ac.uk 25 Mar '14

25 Mar '14

> Message: 1 > Date: Mon, 24 Mar 2014 18:43:26 +0000 > From: "Wilcox, Theodore A -FS" <tawilcox at fs.fed.us> > To: "Xymon at xymon.com" <Xymon at xymon.com> > Subject: [Xymon] Service smtp on hostname is not OK : Unexpected > service response > Message-ID: > <77942EE84FB4A845897BD3D18ED44CEA0105AA61 at 001FSN2MPN1- > 028.001f.mgd2.msft.net> > > Content-Type: text/plain; charset="us-ascii" > > We are getting yellow alerts for all SMTP tests in Xymon. The error given is > "Service smtp on hostname is not OK : Unexpected service response". This is > a new installation and all of the SMTP servers have been yellow since Xymon > was started. Telnet into the server gives the response: "220 > sv62.r1.fs.fed.us ESMTP Service ready at Mon, 24 Mar 2014 12:23:42 -0600". > The hosts file is from Big Brother. All SMTP tests are SMTP.S. We tried > commenting out any line in the [SMTP] section that starts with "Send", but > that didn't change anything. There is nothing recent in the archives about > this. Any suggestions? > > Ted Hello Ted, I suspect this is caused by the 'reply' that the Xymon server is getting when it "handshakes" the SMTP server on the tested system. To explain: I had a similar problem with solid yellow results for the sshd tests on some of my servers, not all even though the ssh daemons were available and reliable on the servers that were yellowing out. I took a look through documentation and newsgroups and found that it was most likely caused by the header line that was being returned by the ssh daemon when the xymon test was run against it. The expected response was set in the protocols.cfg file, in the following section: [ssh|ssh1|ssh2] send "SSH-2.0-OpenSSH_4.1\r\n" expect "SSH" options banner port 22 That line, expect "SSH", instructs the xymon server to "expect" the response to be (to start with?) the phrase "SSH". As I had a mix of different ssh server daemons, most Openssh, some Sun-specific, some linux-specific, this meant that the initial header response from the various ssh servers were different. Some returned the required "SSH" tag in their headers and others didn't. So, xymon seemed to be reporting that it could connect to the ssh daemon, but that it was not getting the expected response hence a "yellow" light. I commented out the 'expect "SSH"' line and ever since I have not seen the erroneous yellow light. Now, onto your issue in particular, if you look in the [$XYMONDIR]/server/etc/protocols.cfg file you will (most likely) find the default setup which is shown below: ----- [smtp] send "mail\r\nquit\r\n" expect "220" options banner port 25 ----- Unless you have a definite reason for checking the text that is returned in the header when connecting to your SMTP server[1] I would suggest that you comment out the 'expect "220"' line. Xymon would still just be checking that it could connect to your SMTP server just it would not be "expect"ing your SMTP server to return a specific header. I can't remember if I needed to restart the xymon server to pickup the changes to protocols.cfg so please be aware that you "may" have to restart the xymon server. Hope that helps. [1] this could be useful for checking which servers are in need of upgrading, are running unwanted versions of servers or have changed for some reason Regards, Steff Watkins ----- Steff Watkins Natural History Museum, Cromwell Road, London,SW75BD Systems programmer Email: s.watkins at nhm.ac.uk Systems Team Phone: +44 (0)20 7942 6000 opt 2 ======== "Many were increasingly of the opinion that they'd all made a big mistake in coming down from the trees in the first place. And some said that even the trees had been a bad move, and that no one should ever have left the oceans." - HHGTTG

1 0

What did the acronym NK stand for?
by abs＠shadymint.com 21 Mar '14

21 Mar '14

I know it's not used anymore, but it lives on in the minds of many but just what was it short for? Thanks -- Andy

2 2

Log file monitoring
by neilsimmonds1808＠gmail.com 20 Mar '14

20 Mar '14

Hi all, As far as I can see there is no built in way in Xymon to monitor a log for the number of times a string has occurred in a specified time period. Is this something that other people would find useful? (even if it was only a count of occurrences within the last 30 minutes and not a configurable time). Is there any chance something like this may be in a future release Henrik? Regards, Neil Simmonds Senior Operations Analyst (Operations Support Group) Express Gifts Limited Express House Clayton Business Park Accrington Lancashire BB5 5JY T: 01254 303092 | E: <mailto:neil.simmonds at Express-Gifts.co.uk> neil.simmonds at Express-Gifts.co.uk

5 5