November 2017 - Xymon - Xymon mailman web

Xymon to monitor HP OpenVMS
by Jose.LeusJr＠analog.com 26 Nov '17

26 Nov '17

Hi David, Below are the snapshot of the file attachment I’ve sent and I did not see 1_Warning.txt. Do you mean you only receive the .txt and not the error-log.? [cid:image003.jpg at 01D361C0.D091AF60] [cid:image004.jpg at 01D361C0.D091AF60] Sincerely, Leus From: David Boyer [mailto:davieb at gmail.com] Sent: Monday, November 20, 2017 2:54 AM To: Leus Jr, Jose <Jose.LeusJr at analog.com> Subject: Re: [Xymon] Xymon to monitor HP OpenVMS Looking at the 1_Warning.txt file, it appears that the McAfee software is removing the file before xymon has access. Dave On Sun, Nov 19, 2017 at 8:53 AM, Leus Jr, Jose <Jose.LeusJr at analog.com<mailto:Jose.LeusJr at analog.com>> wrote: Hi Jeremy, Apology I overlooked this mail. First, thank you very much for your response. There is no CPU graph in CPU Trends as checked. Attached herewith are the logs from /var/log/httpd Sincerely, Leus From: Jeremy Laidman [mailto:jlaidman at rebel-it.com.au<mailto:jlaidman at rebel-it.com.au>] Sent: Thursday, November 9, 2017 11:00 AM To: Leus Jr, Jose <Jose.LeusJr at analog.com<mailto:Jose.LeusJr at analog.com>> Cc: xymon at xymon.com<mailto:xymon at xymon.com> Subject: Re: [Xymon] Xymon to monitor HP OpenVMS Jose The broken graph appears to be an attempt to execute /xymon-cgi/svcstatus.sh as a CGI script. There are a few reasons this might fail. The first place I would look is the Apache server logfile. This may show the reason why svcstatus.sh failed to execute correctly. Do you see the CPU graph showing on the "trends" page? Cheers Jeremy On 15 September 2017 at 06:00, Leus Jr, Jose <Jose.LeusJr at analog.com<mailto:Jose.LeusJr at analog.com>> wrote: Hi Xymon Team, I am a big fan of your monitoring system. I started to use hobbit since 2007 and now using xymon to watch my systems being manage. OpenVMS is one of the system that I need to monitor closely. At this time I was able to monitor hdd, connection , procs and cpu only. But as you can see below, the graph for cpu utilization is not displayed. I still need to add other system resources but im having difficulties to integrate it. I would like to seek for your expert assistance to fully monitor our OpenVMS system. Please advise if we can set a conference call to discuss. Our team will allocate budget for development work needed. I am hoping for your positive response on this matter. Have a nice day to all! [cid:image005.jpg at 01D361C0.D091AF60][cid:image006.jpg at 01D361C0.D091AF60] Sincerely, Leus _______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon _______________________________________________ Xymon mailing list Xymon at xymon.com<mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

2 16

Xymon History Button stopped working in Chrome Version 62.0.3202.94
by mahesh1patil＠gmail.com 21 Nov '17

21 Nov '17

Hi All, I have observed that Xymon (version 4.3.26) History button on all pages stopped working in Chrome - Browser - Version 62.0.3202.94 (Official Build) (64-bit) Chrome - Developer tools - shows - following error Refused to send form data to ' https://xymon.mydomain.org/xymon-cgi/history.sh?HISTFILE=mynode.cpu&ENTRIES…' because it violates the following Content Security Policy directive: "form-action 'self'". Working fine in Firefox browser version 57.0 (64-bit). Is this a know issue? Is there any fix? -- -------------------------- “The Truly Educated never Graduate.” "The only constant is change." Linkedin Profile <http://www.linkedin.com/in/mahesh1patil>

2 2

Windows Powershell Client-local.cfg
by tlwilliams4＠vcu.edu 20 Nov '17

20 Nov '17

We are in the process of moving from the BBWin client to the Powershell client in a mixed Windows/Linux environment. I want to have a common set of parameters in the 'client-local.cfg' file on the Xymon server for the Windows PS clients, rather than listing each client system. I have a section [win32] where I list the same params as for a working single server; I have also tried [windows] and [win] but the test server does not indicate receiving data from Xymon server and settings are not applied. OS is 64-bit Windows 2016, should I try [win64]? On the Linux data file I get back an [osversion] section and a [uname] section, but on the PS data file only a [uname] section. Is that the problem? *Tim Williams*

2 1

Xymon to monitor HP OpenVMS
by Jose.LeusJr＠analog.com 19 Nov '17

19 Nov '17

Hi Xymon Team, I am a big fan of your monitoring system. I started to use hobbit since 2007 and now using xymon to watch my systems being manage. OpenVMS is one of the system that I need to monitor closely. At this time I was able to monitor hdd, connection , procs and cpu only. But as you can see below, the graph for cpu utilization is not displayed. I still need to add other system resources but im having difficulties to integrate it. I would like to seek for your expert assistance to fully monitor our OpenVMS system. Please advise if we can set a conference call to discuss. Our team will allocate budget for development work needed. I am hoping for your positive response on this matter. Have a nice day to all! [cid:image001.jpg at 01D32E15.9E17FF00][cid:image002.jpg at 01D32E15.9E17FF00] Sincerely, Leus

2 2

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