- Xymon - Xymon mailman web

Xymonlaunch Fatal Signal Caught
by dl1025＠att.com 17 Nov '17

17 Nov '17

I think I solved one of the issues with the xymonlaunch errors. I went through the core dump and found that for some reason a root file was created in tasks.d which storing all the mail that root sends out. My account that runs xymon does not have root access so it is no way it can create it. Once that file was deleted, the Task cid:image003.gif at 01D34FFA.21DA2880 terminated by signal 6 errors for xymonlaunch stopped. Very weird. From: LOZOVSKY, DANIEL L Sent: Thursday, November 16, 2017 6:02 PM To: 'xymon at xymon.com' <xymon at xymon.com> Subject: RE: Xymonlaunch Fatal Signal Caught I restarted xymon and now I am getting these messages: Latest error messages: Loading hostnames Loading saved state Too few fields in record - found 3, expected 17 Setting up network listener on 0.0.0.0:1984 Setting up signal handlers Setting up xymond channels Setting up logfiles Setup complete $ view xymonlaunch.log 2017-11-16 19:46:51.260267 Loading hostnames 2017-11-16 19:46:51.343047 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.343334 -> Could not connect to Xymon daemon at 130.5.118.147:1984<mailto:daemon at 130.5.118.147:1984> (Connection refused) 2017-11-16 19:46:51.343357 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.343385 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.352628 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.353029 -> Could not connect to Xymon daemon at 130.5.118.147:1984<mailto:daemon at 130.5.118.147:1984> (Connection refused) 2017-11-16 19:46:51.353071 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.353103 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.353218 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.353429 -> Could not connect to Xymon daemon at 130.5.118.147:1984<mailto:daemon at 130.5.118.147:1984> (Connection refused) 2017-11-16 19:46:51.353446 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.353458 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.356314 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.356610 -> Could not connect to Xymon daemon at 130.5.118.147:1984<mailto:daemon at 130.5.118.147:1984> (Connection refused) 2017-11-16 19:46:51.356640 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.356662 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.364578 Task cid:image006.gif at 01D34FFC.9E097850 terminated by signal 6 2017-11-16 19:46:51.364744 Task cid:image007.gif at 01D34FFC.9E097850 terminated by signal 6 From: LOZOVSKY, DANIEL L Sent: Thursday, November 16, 2017 5:22 PM To: xymon at xymon.com<mailto:xymon at xymon.com> Subject: Xymonlaunch Fatal Signal Caught I am not sure what happened. I started to receive Fatal Signal Caught for XymonLaunch. I checked the xymonlaunch log and started seeing the following messages: 2017-11-16 19:10:15.609314 Task cid:image002.gif at 01D34FFA.21DA2880 terminated by signal 6 2017-11-16 19:10:15.609489 Task cid:image001.gif at 01D34FFA.21DA2880 terminated by signal 6 2017-11-16 19:10:15.609533 Task cid:image004.png at 01D34FFC.9E097850 terminated by signal 6 2017-11-16 19:10:15.609845 Task cid:image003.gif at 01D34FFA.21DA2880 terminated by signal 6 There were also core dumps in tmp directory. Does anyone have any idea what is causing this?

1 0

Xymonlaunch Fatal Signal Caught
by dl1025＠att.com 17 Nov '17

17 Nov '17

I restarted xymon and now I am getting these messages: Latest error messages: Loading hostnames Loading saved state Too few fields in record - found 3, expected 17 Setting up network listener on 0.0.0.0:1984 Setting up signal handlers Setting up xymond channels Setting up logfiles Setup complete $ view xymonlaunch.log 2017-11-16 19:46:51.260267 Loading hostnames 2017-11-16 19:46:51.343047 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.343334 -> Could not connect to Xymon daemon at 130.5.118.147:1984 (Connection refused) 2017-11-16 19:46:51.343357 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.343385 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.352628 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.353029 -> Could not connect to Xymon daemon at 130.5.118.147:1984 (Connection refused) 2017-11-16 19:46:51.353071 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.353103 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.353218 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.353429 -> Could not connect to Xymon daemon at 130.5.118.147:1984 (Connection refused) 2017-11-16 19:46:51.353446 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.353458 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.356314 Whoops ! Failed to send message (Connection failed) 2017-11-16 19:46:51.356610 -> Could not connect to Xymon daemon at 130.5.118.147:1984 (Connection refused) 2017-11-16 19:46:51.356640 -> Recipient '130.5.118.147', timeout 15 2017-11-16 19:46:51.356662 -> 1st line: 'status blpv0379.xymonlaunch red - Program crashed' 2017-11-16 19:46:51.364578 Task cid:image006.gif at 01D34FFC.9E097850 terminated by signal 6 2017-11-16 19:46:51.364744 Task cid:image007.gif at 01D34FFC.9E097850 terminated by signal 6 From: LOZOVSKY, DANIEL L Sent: Thursday, November 16, 2017 5:22 PM To: xymon at xymon.com Subject: Xymonlaunch Fatal Signal Caught I am not sure what happened. I started to receive Fatal Signal Caught for XymonLaunch. I checked the xymonlaunch log and started seeing the following messages: 2017-11-16 19:10:15.609314 Task cid:image002.gif at 01D34FFA.21DA2880 terminated by signal 6 2017-11-16 19:10:15.609489 Task cid:image001.gif at 01D34FFA.21DA2880 terminated by signal 6 2017-11-16 19:10:15.609533 Task cid:image004.png at 01D34FFC.9E097850 terminated by signal 6 2017-11-16 19:10:15.609845 Task cid:image003.gif at 01D34FFA.21DA2880 terminated by signal 6 There were also core dumps in tmp directory. Does anyone have any idea what is causing this?

1 0

Xymonlaunch Fatal Signal Caught
by dl1025＠att.com 17 Nov '17

17 Nov '17

I am not sure what happened. I started to receive Fatal Signal Caught for XymonLaunch. I checked the xymonlaunch log and started seeing the following messages: 2017-11-16 19:10:15.609314 Task cid:image002.gif at 01D34FFA.21DA2880 terminated by signal 6 2017-11-16 19:10:15.609489 Task cid:image001.gif at 01D34FFA.21DA2880 terminated by signal 6 2017-11-16 19:10:15.609533 Task cid:image004.png at 01D34FFC.9E097850 terminated by signal 6 2017-11-16 19:10:15.609845 Task cid:image003.gif at 01D34FFA.21DA2880 terminated by signal 6 There were also core dumps in tmp directory. Does anyone have any idea what is causing this?

1 0

Request for server specs
by Donnell.Johnson＠fda.hhs.gov 16 Nov '17

16 Nov '17

Hello Xymon, I would like to get the physical/server specifications required to support Xymon. Thanks Donnell Johnson FDA/OIMT Scientific Computing Support 3WFN Room 10A40 11601 Landsdown Street North Bethesda, MD 20852 Office: 301-348-1997 Donnell.Johnson at fda.hhs.gov<mailto:Donnell.Johnson at fda.hhs.gov> | Donnell.Johnson at engilitycorp.com<mailto:Donnell.Johnson at engilitycorp.com> | www.EngilityCorp.com<http://www.engilitycorp.com/>

4 3

Clean up logs
by dirk.kastens＠uni-osnabrueck.de 15 Nov '17

15 Nov '17

Hi, I'm running a script from cron.daily that cleans up my data: /bin/su - xymon -c '/usr/libexec/xymon/trimhistory --cutoff=`date +%s --date="today -1 year"` --drop --droplogs --env=/etc/xymon/xymonserver.cfg' /bin/find /var/lib/xymon/hostdata -type f -mtime +7 -delete Regards, Dirk

3 2

month graps
by mailinglist＠tikklik.nl 15 Nov '17

15 Nov '17

Hello, I have my values in mysql the values are every 15 minutes generated. Im now using this /usr/bin/rrdtool graph '.$filename.' --step 900 --imgformat=PNG --title "'.$title.'" --slope-mode --vertical-label="Wh" --alt-autoscale-max --start='.$start.' --end=+1hours --width=600 --height=300 "DEF:min='.$DS_BASE.':min:AVERAGE" "AREA:min#00FF00:Opbrengst" GPRINT:min:LAST:" Current\:%8.2lf %sW" GPRINT:min:AVERAGE:"Average\:%8.2lf %sW" GPRINT:min:MAX:"Maximum\:%8.2lf %sW\n" The problem that I have is that the older values (month graph) has lower values ( I think average) Is there a way to prevent this is happening? Steffan

2 1

Graph patch
by stef.coene＠docum.org 15 Nov '17

15 Nov '17

Hi, I added option filter and filelist to showgraph.sh to enhance the graphing availabilities. The filter filters the rrd files and only graphs the matching files. With file filelist option, you can specify a list of rrd files. | is used between the files. Example, if you have file system /home and /home/users, you can add filter=,home to filter for filesystems containing /home at the end of the showgraph.sh url. Or you can add ,home|,home,users to only show /home and /home/users. I think this is a nice feature for Xymon. But I need some help.... The only issue I have is that for filter it works fine, but for filelist, the graphs are missing the filenames in the comments. Stef

1 0

Clean up logs
by manojbiswakarma＠yahoo.com 14 Nov '17

14 Nov '17

Hi Xymon Team, I have xymon running at my work place for quite a long time and was wondering ways I can cleanup the old logs. 1. Is there some tools or feature in xymon which I can use to remove old logs or do I use command such as find to remove them ? 2. And if suppose I remove the old files from under "histlogs and hostdata" manually using find command, will it impact my xymon afterward ? The area for cleanup which I am referring to is pasted below: 4.0K acks 4.0K data 4.0K disabled 991M hist 56 G histlogs 195 G hostdata 4.0K logs 2.0G rrd $ pwd /home/xymon/data $ ls -l drwxr-xr-x. 2 xymon xymon 2 Sep 24 2014 acks drwxr-xr-x. 2 xymon xymon 2 Sep 24 2014 data drwxr-xr-x. 2 xymon xymon 2 Sep 24 2014 disabled drwxr-xr-x. 2 xymon xymon 8954 Oct 11 22:18 hist drwxr-xr-x. 483 xymon xymon 483 May 31 13:15 histlogs drwxr-xr-x. 264 xymon xymon 264 Apr 20 2017 hostdata drwxr-xr-x. 2 xymon xymon 2 Sep 24 2014 logs drwxr-xr-x. 483 xymon xymon 483 May 31 13:15 rrd Thank you in advance. Regards Manoj Biswakarma (Manoj)

1 0

Custom plugin Interval/Crondate turning purple quickly
by rich＠corporationpop.co.uk 14 Nov '17

14 Nov '17

I have a custom plugin that is set to run every Tuesday at 10am on the server itself, that all runs fine and as expected, however it seems that shortly after the task has reported back to Xymon (20/30 mins) the task turns purple. I was expecting the status to stay green (or red etc) until the next run time. Any ideas why this is happening? Running Xymon 4.3.28 and the server side tasks.cfg looks like this: [sometask] ENVFILE /usr/local/xymon/server/etc/xymonserver.cfg CMD /usr/local/xymon/server/ext/sometask.sh LOGFILE $XYMONSERVERLOGS/sometask.log CRONDATE 0 10 * * 2 This did happen last week when I originally implemented the task, but I figured it was due to manually running xymoncmd... though that doesn't seem to be the case. Cheers

3 3

logfetch segfault using deltacount after a find command... and deltacount always returns 0 when no segfault
by spah＠syntec.co.uk 14 Nov '17

14 Nov '17

It seems that when using deltacount after a log statement with a 'find' in it like in the example below causes a seg fault in logfetch: log:`find /opt/tomcat/logs/myapp.$(date +%F).log`:10240 # deltacount after a find causes a seg fault. deltacount WarningDeltaCount "WARNING" It does not seem to matter if the find statement is actually in a different higher up log line that should not be affecting this deltacount. The workaround to that is to re-order the log statements such that your find is below the deltacount, but that still means they can not be used together, which means we can not use deltacount in the example above. This core backtrace does not look very helpful to me, but maybe because I am using a non-debug version of the 4.3.28 xymon-client RPM ( https://terabithia.org/rpms/xymon/el6/x86_64/xymon-client-4.3.28-1.el6.x86_… ): core_backtrace: :{ "signal": 11 :, "executable": "/usr/bin/logfetch" :, "stacktrace": : [ { "crash_thread": true : , "frames": : [ { "address": 4217378 : , "build_id": "40398b05a94e8227d573537651e7f595e5ef0d96" : , "build_id_offset": 23074 : , "file_name": "/usr/bin/logfetch" : } ] : } ] :} It was the same on 4.3.26-1 RPM. *Separately*, I believe that even when there is no segfault (because I hard code the filename), and the clientlog is all present and correct, that deltacount actually returns the wrong number of lines - it always seems to be 0 in my tests (with --debug, run from command line): 550 2017-11-14 13:12:38.042701 logfetch: -> logdata (/opt/tomcat/logs/myapp.2017-11-14.log) 550 2017-11-14 13:12:38.043112 - fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 0, loc 2558853 550 2017-11-14 13:12:38.043133 - fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 1, loc 2557130 550 2017-11-14 13:12:38.043149 - fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 2, loc 0 550 2017-11-14 13:12:38.043181 - fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 3, loc 0 550 2017-11-14 13:12:38.043199 - fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 4, loc 0 550 2017-11-14 13:12:38.043224 - fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 5, loc 0 550 2017-11-14 13:12:38.043240 - fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 6, loc 0 550 2017-11-14 13:12:38.043274 logfetch: Current size (ending): 2560538 bytes. Last end was 2558853. Looking 6 spots before that, which is 0. bytestocurrent: 2558853 550 2017-11-14 13:12:38.043322 - compiling DELTACOUNT regex: "WARNING" 550 2017-11-14 13:12:38.064073 - Last position was 2558853, found curpos location at 2558853 in current buffer. 550 2017-11-14 13:12:38.064121 - line forced as a trigger: <...CURRENT...> 14-Nov-2017 13:11:09.259 FINE [pool-1-thread-6923] [edited out] 550 2017-11-14 13:12:38.064135 - first trigger line encountered; preparing trigger START & END positioning store 550 2017-11-14 13:12:38.064146 - new trigger anchor START position set 550 2017-11-14 13:12:38.064164 - trigger END position set 550 2017-11-14 13:12:38.064194 Marked 1 pairs of START and END anchors for consideration. 550 2017-11-14 13:12:38.064206 Found 1674 bytes of trigger data, 8566 bytes available space for non-trigger data; last trigger ended 961 bytes from end. Max bytes allowed is 10240. 550 2017-11-14 13:12:38.064222 Staging replacement buffer, 10272 bytes. 550 2017-11-14 13:12:38.064233 Copying buffer content for trigger 1. 550 2017-11-14 13:12:38.064247 logfetch: More space was available than between last trigger and eof; reducing to 961 bytes 550 2017-11-14 13:12:38.064259 logfetch: Delta from end of final trigger to beginning of final section: 0 bytes 550 2017-11-14 13:12:38.064268 Copying 961 final bytes of non-trigger content 550 2017-11-14 13:12:38.064351 -- fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 0, loc 2560538 550 2017-11-14 13:12:38.064362 -- fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 1, loc 2558853 550 2017-11-14 13:12:38.064372 -- fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 2, loc 2557130 550 2017-11-14 13:12:38.064382 -- fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 3, loc 0 550 2017-11-14 13:12:38.064394 -- fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 4, loc 0 550 2017-11-14 13:12:38.064403 -- fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 5, loc 0 550 2017-11-14 13:12:38.064413 -- fn: /opt/tomcat/logs/myapp.2017-11-14.log, pos 6, loc 0 550 2017-11-14 13:12:38.064424 logfetch: <- logdata (/opt/tomcat/logs/myapp.2017-11-14.log) [msgs:/opt/tomcat/logs/myapp.2017-11-14.log] Can anyone help? Thanks, SebA

1 0