- Xymon - Xymon mailman web

extcombo problem
by dave＠collegenet.com 12 Aug '16

12 Aug '16

I have a xymon server running 4.3.0~beta2.dfsg-9.1+deb7u1 receiving reports from a bbnet server running 4.3.17-6+deb8u1 and they are not compatible due to the new "extcombo" reporting. The changelog says that the "extcombo" thing was added in version 4.3.13. Even after disabling "combostatus" in tasks.cfg, xymonnet still uses "extcombo". Without a way to disable it, we're partially broken right now. Any suggestions? Dave Fogarty -- Senior System Administrator CollegeNET.com

2 1

Windows server folder size monitoring?
by david.baldwin＠ausport.gov.au 11 Aug '16

11 Aug '16

Over the course of a few years I've worked out a few folders on most Windows servers that need to be monitored for space usage, because the GBs can pile up remarkably quickly otherwise. I discovered another one today (Recycle Bin - because other users can leave stuff piled up in there that's still filling the disk) which causes me to wonder what else I'm missing. The process of actually deleting the offending files is a more complicated issue, but the first step is knowing they are there at all! I have the following folders defined, with thresholds of 200MB for yellow and 500MB for red: client-local.cfg: [win32] dir:C:\$Recycle.Bin dir:C:\ProgramData\Microsoft\Windows\WER dir:C:\Windows\Logs\CBS dir:C:\Windows\Temp analysis.cfg: CLASS=win32 DIR C:\$Recycle.Bin yellow SIZE<200000 TRACK=C-RCB DIR C:\$Recycle.Bin red SIZE<500000 DIR C:\Windows\Logs\CBS yellow SIZE<200000 TRACK=C-CBS DIR C:\Windows\Logs\CBS red SIZE<500000 DIR C:\ProgramData\Microsoft\Windows\WER yellow SIZE<200000 TRACK=C-WER DIR C:\ProgramData\Microsoft\Windows\WER red SIZE<500000 DIR C:\Windows\Temp yellow SIZE<200000 TRACK=C-Windows-Temp DIR C:\Windows\Temp red SIZE<500000 -- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Digital Information Management and Technology Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au 1 Leverrier Street Bruce ACT 2617 Our Values: RESPECT + INTEGRITY + TEAMWORK + EXCELLENCE ------------------------------------------------------------------------------------- Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender. -------------------------------------------------------------------------------------

1 0

xymonnet TCPtest error 4
by Kirk.MacDonald＠corp.eastlink.ca 11 Aug '16

11 Aug '16

Hello, We are running Xymon with xymonnet version 4.3.26-1.el6.terabithia and SSL library : OpenSSL 1.0.1e 11 Feb 2013 (CentOS release 6.8). Sporadically we see errors testing a certain host with imaps and pop3s tests. The errors are as follows: TCPtest error 4 seen on open connection for $x.imaps TCPtest error 4 seen on open connection for $x.pop3s .. where $x is a few random extended ASCII characters A commonality is that these are both SSL/TLS enabled services hosted on the same system. pop3s is configured as port 995 with SSL/TLS required and imaps is port 993 with SSL/TLS required. My gut tells me this is probably related to SSL/TLS negotiation problems. Any recommendations on where to start? Thanks, Kirk MacDonald System Administrator Internet Eastlink

2 1

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