August 2016 - Xymon - Xymon mailman web

RRD File for Graph not being created
by Foster.Patch＠accuweather.com 11 Aug '16

11 Aug '16

Hello, I have been troubleshooting this for a while. I have a script with a very simple output, example "cf-execd : 13.60". I have gone onto the local server that it will be run on, and added the appropriate lines to clientlaunch.cfg. I went on the server and modified xymonserver.cfg, adding "CFENGINE=ncv" to the end of the TEST2RRD line. (CFENGINE is the monitor name) I also added a new line on the file which states, "NCV_CFENGINE="cf-execd:GAUGE". I then restarted the xymon services. However, the RRD file is not created. What am I doing wrong? This monitor is much more elaborate, but I dumbed it down to a single line to troubleshoot this issue, and it still isn't working. Any ideas? Foster Patch Server Technician AccuWeather

3 3

not getting alerts on url checking.
by jlaidman＠rebel-it.com.au 11 Aug '16

11 Aug '16

On Wed, Jul 13, 2016 at 6:38 AM usa ims via Xymon <xymon at xymon.com> wrote: > Hi, > > I have these two tests in my hosts.cfg > > page development development > xx.202.xxx.xxx JIRA #https://xx.202.xxx.xxx:8443/login.jsp > NOCOLUMNS:info,trends,conn > xx.202.xxx.xxx Stash #https://xx.202.xxx.xxx:8444 > NOCOLUMNS:info,trends,conn > > So, for grins, I wanted to make sure I'll get alerted so I changed the > port to some port not being used, like below: > > xx.202.xxx.xxx JIRA #https://xx.202.xxx.xxx:4443/login.jsp > NOCOLUMNS:info,trends,conn > xx.202.xxx.xxx Stash #https://xx.202.xxx.xxx:4444 > NOCOLUMNS:info,trends,conn > > What is happening is that in the nongreen.html status window, the side bar > is not turning red but staying green but the little tiny faces went from > green to white and I did not get alerted. > It's as if you have "--ignorecolumns=http" or "--nopropred=http" for the xymongen command, or something like that. > Below is what is in my alerts.cfg > alerts.cfg is only used when generating emails. It doesn't affect the display. If you don't get a red/yellow then you won't get an alert. Nothing you can put into or take out of alers.cfg will affect the display. You could try running xymonnet manually with "--debug" and/or "--dump" arguments. I would extract one host for testing, put it into a different hosts.cfg file, and then point xymonnet to that file by setting HOSTSCFG=/tmp/hosts.cfg or simlar. Hmm. I notice you've suppressed conn messages from displaying (with NOCOLUMNS) but you haven't included "noconn" to stop the conn tests from taking place. I wonder if you removed "conn" from NOCOLUMNS, you might see it going red. When a ping (conn) test goes red, other network tests go clear. If this is the case, simply add "noconn" wherever you have NOCOLUMNS:conn. Cheers Jeremy

1 0

fatal error caught?
by Russell.Blumenthal＠stonybrookmedicine.edu 10 Aug '16

10 Aug '16

Hey guys, Ever since I ran a trimhistory command, my xymond_alert and xymond_history are coming up as purple with the message '-Program crashed Fatal signal caught!'. What happened and what should I look for to troubleshoot this? Thanks This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by e-mail and destroy all copies of the original.

2 2

analysis.cfg - LOG - keyword matching
by christian.becker＠rhein-zeitung.net 10 Aug '16

10 Aug '16

Hello out there, yesterday i recognized that one of our servers has error messages in /var/log/messages every day. The entries are: Aug 8 11:08:26 mrv-online-4 kernel: [3356791.776050] EXT4-fs (dm-8): error count since last fsck: 6 Aug 8 11:08:26 mrv-online-4 kernel: [3356791.776080] EXT4-fs (dm-8): initial error at time 1468716722: ext4_journal_check_start:56 Aug 8 11:08:26 mrv-online-4 kernel: [3356791.776085] EXT4-fs (dm-8): last error at time 1468743842: ext4_put_super:798 In the analysis.cfg of the Xymon server, there is a DEFAULT section with the following content: DEFAULT # These are the built-in defaults. UP 3 CLOCK 60 LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 80 90 MEMACT 90 97 FILE /var/log/ntp SIZE>0 FILE %/var/(adm|log)/messages LOG %/var/(adm|log)/messages WARNING IGNORE=%(smbd|STORVSC:*.WARNING\!|gdm-simple-greeter|GdmDisplay|GdmSession|GDM|packagekitd|parport) COLOR=yellow LOG %/var/(adm|log)/messages %(I/O|read).error IGNORE=%(fd0|smbd|read_fd_with_timeout|Connection.reset.by.peer|error\.txt) COLOR=red LOG %/var/(adm|log)/messages Remounting.filesystem.read-only COLOR=red LOG %/var/(adm|log)/messages ERROR IGNORE=%(fd0|smbd|read_fd_with_timeout|Connection.reset.by.peer|error\.txt|gdm-simple-greeter|GdmDisplay|GdmSession|GDM|packagekitd|parport) COLOR=red LOG %/var/(adm|log)/messages FAIL IGNORE=%(smbd|Connection.reset.by.peer|gdm-simple-greeter|GdmDisplay|GdmSession|GDM|packagekitd|parport|NT_STATUS_LOGON_FAILURE|LOGIN|STARTTLS) COLOR=red LOG %/var/(adm|log)/messages CRITICAL IGNORE=%(smbd|gdm-simple-greeter|GdmDisplay|GdmSession|GDM|packagekitd|parport) COLOR=red LOG %/var/(adm|log)/messages ALERT COLOR=red LOG %/var/(adm|log)/messages There.are.errors.in.the.filesystem COLOR=red PROC "syslog" I was thinking, that this directive LOG %/var/(adm|log)/messages ERROR IGNORE=%(fd0|smbd|read_fd_with_timeout|Connection.reset.by.peer|error\.txt|gdm-simple-greeter|GdmDisplay|GdmSession|GDM|packagekitd|parport) COLOR=red should msgs let go to red, since the message of the affected server contains the keyword "error", even in lowercase. But the history of the msgs test for the affected server doesn't show any red status. I do not have the statement (?-i) in the analysis.cfg as documented in the Xymon man-pages: Note that Xymon defaults to case-insensitive pattern matching; if that is not what you want, put "(?-i)" between the "%" and the regular expression to turn this off. E.g. "%(?-i)WARNING" will match the word WARNING only when it is upper-case. Is my thinking wrong? Regards Christian Christian Becker IT-Services _________________________________ Mittelrhein-Verlag GmbH August-Horch-Straße 28 D-56070 Koblenz Verleger und Geschäftsführer: Walterpeter Twer Reg.-Gericht Koblenz HRB 121 Finanzamt Koblenz Str.Nr. 22 65 10 285 2 www.rhein-zeitung.de<http://www.rhein-zeitung.de/>

2 2

Constant red condition
by jborissr＠gmail.com 09 Aug '16

09 Aug '16

I have a constant RED condition for the procs test. I checked all of my other servers and they all have just one instance of cron yet this one server has the one instance running but it come up red. These are all the same OS, Same client version. Some are stand alone servers and others are VM but this one machine just will not go Green. Any pointers on this? -- John J. Boris, Sr.

2 2

Service names from XymonPSClient
by jtrott＠dancrai.com 09 Aug '16

09 Aug '16

Hi all. I have a windows service "MSSQL$MICROSOFT##WID" that is being reported by the XymonPSClient. To monitor this service I need to add the following line in my analysis.cfg file: SVC MSSQL$MICROSOFT##WID status=started But, the # characters are seen as the start of a comment, so the result is this: MSSQL$MICROSOFT: No matching service - want started/Any I tried escaping the # characters with \ but that just resulted in: MSSQL$MICROSOFT\: No matching service - want started/Any Any ideas? Thanks, JT

4 6

Client uptime
by oskar＠campnorthernlight.com 08 Aug '16

08 Aug '16

Hey there, I noticed there isn't a prewritten check for graphing the uptime of clients?, or is that under connection instead? -- Kind Regards / Med Vänliga Hälsningar *Oskar Hammarström*

4 3

trim history
by Russell.Blumenthal＠stonybrookmedicine.edu 08 Aug '16

08 Aug '16

I want to use the trimhistory command but not sure exactly how to execute it. Anyone have an example? Thanks This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by e-mail and destroy all copies of the original.

2 1

SSL/HTTPS enabling on existing Xymon Server
by shekar.raaja＠gmail.com 08 Aug '16

08 Aug '16

Hello Xymon Team, I would like to enable SSL on XYMON Server to support https requests. As I am seeing connection time out errors for HTTPS URL's. Our configuration supports HTTP perfectly fine and for your information it is in production and live, so we don't want to do reinstall of Xymon servers. Rather than is there any configuration changes we can make on existing configs and do the server restart?? Xymon Version we are using Xymon version 4.3.7 I just installed Openssl OpenSSL 1.0.1e-fips 11 Feb 2013 Please let me know if any concerns. Thanks and Regards Raja Shekar

4 6

New Install
by Nick＠pettefar.com 06 Aug '16

06 Aug '16

I just downloaded the latest stable Xymon release (4.3.21 and configured and maked it but when I click on the items I just get a file to download or a blank screen with a No Such Host message. I looked in the server/cgi-bin directory and there are a load of files ending in .sh but they are binaries not scripts and all of an identical size. I checked in the same directory of a previous version and they are small shell scripts. Can anyone help? Regards, Nick Pettefar

2 3