August 2019 - Xymon - Xymon mailman web

Xymon ssl question
by zak.beck＠accenture.com 05 Aug '19

05 Aug '19

Hi David Thanks ? This sounds like a query about the sslcert test? This is part of the built-in server functionality and you?ll get way better answers from the mailing list than you?ll get from me. If the IPs are externally accessible you could try the Qualys SSL checker (https://www.ssllabs.com/ssltest/) to check for any SSL issues. Zak From: David Hickenbottom <david.hickenbottom at Ingeniousmed.com> Sent: Tuesday, 30 July 2019 19:40 To: Beck, Zak <zak.beck at accenture.com> Subject: [External] Xymon ssl question This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. ________________________________ Hi Zak, You did a fantastic job of putting together the script to build the xymon client data for windows. Thank you. I had a question that you may be able to give me a bit of direction. I have about 20 webservers. Half of them report the SSL certificate issue properly, the other half do not. They just say SSL error. They do not show any evidence that they even see the SSL certificate. I was wondering if you have ever seen this and if there is a way to turn on logging so I can see it? Thank you for your time. Best regards, David Hickenbottom Technical Operations Manager Ingenious Med (o) 678-486-4241 | (m) 770.335.2596 www.ingeniousmed.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ingeniousmed.com_&d…> ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com

2 1

xymond_rrd program crashed
by andreas.kunberger＠ditf.de 05 Aug '19

05 Aug '19

Since we have updated to Xymon 4.3.29-1.el7.terabithia We get the xymond status: xymond_rrd program crashed Fatal signal caught! In the /var/log/messages we have: Aug 4 06:59:33 suse abrt-hook-ccpp[9966]: Process 8736 (xymond_rrd) of user 1000 killed by SIGABRT - dumping core Aug 4 06:59:34 suse abrt-server[9968]: Package 'xymon' isn't signed with proper key Aug 4 06:59:34 suse abrt-server[9968]: 'post-create' on '/var/spool/abrt/ccpp-2019-08-04-06:59:33-8736' exited with 1 Aug 4 06:59:34 suse abrt-server[9968]: Deleting problem directory '/var/spool/abrt/ccpp-2019-08-04-06:59:33-8736' and in /var/log/xymon/rrd-status 2019-08-04 06:58:43.164318 net-janus/ntpd.rrd: Bug - duplicate RRD data with same timestamp 1564894723, different data 2019-08-04 06:59:33.750946 Host 'rackstation' reports netstat for an unknown OS 2019-08-04 06:59:34.621163 xymond_channel: Child process 8736 died: Signal 6 2019-08-04 06:59:34.739280 xymond_channel: Peer at 0.0.0.0:0 failed: Broken pipe 2019-08-04 06:59:34.986178 xymond_channel: Peer not up, flushing message queue 2019-08-04 06:59:56.727302 Host 'rackstation3' reports netstat for an unknown OS 2019-08-04 06:59:57.603455 xymond_channel: Child process 9971 died: Signal 6 2019-08-04 06:59:58.136009 xymond_channel: Peer at 0.0.0.0:0 failed: Broken pipe 2019-08-04 06:59:58.136109 xymond_channel: Peer not up, flushing message queue 2019-08-04 06:59:58.136150 xymond_channel: Peer not up, flushing message queue 2019-08-04 06:59:58.136192 xymond_channel: Peer not up, flushing message queue 2019-08-04 06:59:58.136316 xymond_channel: Peer not up, flushing message queue 2019-08-04 06:59:58.136374 xymond_channel: Peer not up, flushing message queue .... The Server runs on CentOS Linux release 7.6.1810 (Core) Thanks in advance! i.A. Andreas Kunberger -- Andreas Kunberger ZD/IT

1 0

Removing user from alerts
by chrisp＠lightstoneauto.co.za 03 Aug '19

03 Aug '19

Good morning One of our exemployees that left the company keeps on receiving sms alerts from xymon, I already removed all traces of his number / email address from the alerts configs but he still received sms's. Where can look why alerts are still being sent to this user? Regards [cid:image001.png at 01D5490C.EACE1FF0] Chris Pretorius Senior Linux Administrator [Lightstone] chrisp at lightstone.co.za<mailto:chrisp at lightstone.co.za> www.lightstone.co.za<https://www.lightstone.co.za/> 0108228687 Centurion Square, 3rd Floor, cnr Heuwel and Gordon Hood rd, Centurion [cid:image003.png at 01D5490C.EACE1FF0]<https://www.linkedin.com/company/lightstone-pty-ltd/> [cid:image004.png at 01D5490C.EACE1FF0] <https://twitter.com/lightstonetweet> [cid:image005.png at 01D5490C.EACE1FF0] <https://www.facebook.com/lightstone.sa> This communication is subject to Lightstone's email disclaimer<http://www.lightstone.co.za/portal/content/email-disclaimer.aspx>

2 1

rrd data capture and multiple tests with missing data
by mtpins＠nndev.org 03 Aug '19

03 Aug '19

Boldt, David writes: >In a test defined to store 4 values for graphing I am unable to >arrange for the storage of the available information if >information for any variable is missing. >In many runs of the test not all of the variables will have data. >I've tried: > * omitting the variables where there are no values > * listing the variable without data > * setting the value to NaN for missing data > * setting the value to a number below the rrd "--minimum" for the variable >In all of these cases no data is stored for the interval if any of the >variables has no data. (Am using NCV parsing of the status.) >I am able to store and graph the data for all 4 variables if I set missing >values to zero, but this provides unsatisfactory looking graphs and >incorrect averages. >xymon version 4.3.28 on CentOS 7. Use SPLITNCV rather than NCV, then use FNPATTERN in graphs.cfg.

1 0

[EXT] Re: Xymon 4.3.29 Released - Important Security Update
by tschmidt＠micron.com 02 Aug '19

02 Aug '19

Japheth and Xymon 4.3.29 users, Attached is a context diff patch file for the Xymon 4.3.29 release to address the following issues: Bug Fixes: - build/Makefile.Linux Use tirpc replacement only on glibc 2.26 and later. This fixes compiling and RPC issues on RHEL6 and RHEL7 platforms. - lib/*.c files and xymonnet/xymonnet.c: Only use the "#pragma GCC diagnostic" options on gcc 4.5 and later. This fixes compiling on RHEL6. Enhancements: - web/showgraph.c: Change underscore to space as this is a common mangling on temperature and lic backends - xymond/etcfiles/graphs.cfg and xymond/rrd/do_disk.c: Change disk sizes from KB to auto-scaling (i.e. GB, TB) Add FlexLM license graph for lic backend. - xymond/rrd/do_temperature.c: - Strip off any bold and italic HTML tags on temperature sensor name Thank you again for maintaining Xymon once again. Please include my recommend patches so the it compiles on RHEL6/7 platforms without issue. Tom Schmidt Sr Manager, IT, Product Engineering IT ETD Eng Sites US Micron Technology, Inc. Office:?+1 (208) 368-4058 ?Fax:?(208)368-2807 Email:?tschmidt at micron.com? Website:?micron.com Micron Technology, Inc., Confidential and Proprietary. -----Original Message----- From: Xymon <xymon-bounces at xymon.com> On Behalf Of Japheth Cleaver Sent: Wednesday, July 24, 2019 7:40 PM To: Stephen Carville (xymon list) <scarville at lereta.com>; xymon at xymon.com Subject: [EXT] Re: [Xymon] Xymon 4.3.29 Released - Important Security Update On 7/24/2019 7:01 AM, Stephen Carville (xymon list) wrote: > On 7/23/19 9:08 AM, Japheth Cleaver wrote: >> Lereta Email Checkpoint: External email. Please make sure you trust >> this source before clicking links or opening attachments. >> >> ********************************************************************* >> * >> > Just an FYI. When I updated my CentOS 7 xymon server by building from > source, it refused to include the openssl libraries until I installed > the libtirpc-devel package. Not sure why it is necessary. > Thanks, I'll make a note of that on the RPM site. The underlying reason here is that GCC's rpc interface was removed after a long deprecation, in favor of libtirpc. It was easier to simply test for that and move forward on use. This will also be necessary for 4.4 (IPv6) and was the main cause of the recent Fedora FTBFS's. https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedorapro… Regards, -jc _______________________________________________ Xymon mailing list Xymon at xymon.com https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.xymo…

2 3

Frequent purple alerts
by tlwilliams4＠vcu.edu 01 Aug '19

01 Aug '19

I don't know about the DNS switching around, unless it is due to some DC synchronizing stuff, and one has a manual entry the other doesn't? Two ways to circumvent that is to use the IP in the Xymon Settings file <servers> tag ( I think that is what you said you did), or add the internal IP to the server HOSTS file; both of which requires future editing if the IP of the hostname gets changed. I should have mentioned that I use the tag <clientlogretain>4</clientlogretain> in my xymonclient_config.xml file to save multiple versions of the logs to give me some time to look at them and track changes from one file to another when I make a change. Glad you are able to get it stable. Tim Williams VCU Computer Center On Wed, Jul 31, 2019 at 4:33 PM Jaime Kikpole <jkikpole at cairodurham.org> wrote: > Sorry to resurrect this old thread, but I finally was able to grab the > logs from the Xymon client during a purple alert. Usually, it would go > back to green before I would notice, could switch gears, and began working > on it. > > Thanks, Timoth Williams, for pointing out the file uploading parts of the > logs. Based on that, I found these lines in the xymonclient.log file: > 2019-07-31 15:25:38 Connecting to host 163.153.163.90 > 2019-07-31 15:25:59 ERROR: Cannot connect to host > monitor1.cairodurham.org (163.153.163.90) : > System.Management.Automation.MethodInvocationException: Exception calling > "Connect" with "2" argument(s): "A connection attempt failed because the > connected party did not properly respond after a period of time, or > established connection failed because connected host has failed to respond > 163.153.163.90:1984" ---> System.Net.Sockets.SocketException: A > connection attempt failed because the connected party did not properly > respond after a period of time, or established connection failed because > connected host has failed to respond 163.153.163.90:1984 > > It looks like it was somehow resolving the FQDN (monitor1.cairodurham.org) > to its external IP address instead of its internal IP address. I'm not > sure why. I just checked the DNS settings and they're the same as another > Windows 2012R2 server that isn't having this issue. > > I changed the FQDN to the internal IP address and restarted the service. > Everything went green almost immediately. > > Any idea how it could resolve to the public IP address 2 - 4 each day but > only for a few hours total each day? > > > > > Jaime Kikpole > > Director of Technology & Innovations > Cairo-Durham Central School District > (518) 622-8543, x59500 > cairodurham.org <http://www.cairodurham.org> > > Technical Support: > help at cairodurham.org > go.cairodurham.org/techtips > > [image: Google Certified Educator, Level 1][image: Google Certified > Educator, Level 2] <https://www.credential.net/d24m9rrp> > > > This electronic message and any attachment(s) may contain confidential or > legally privileged information protected by law from further disclosure and > is intended only for the individual or entity identified above as the > addressee. If you are not the addressee (or the employee or agency > responsible to deliver it to the addressee), or if this message has been > addressed to you in error, you are hereby notified that you may not copy, > forward, disclose or use any part of this message or any attachment(s). > Please notify the sender immediately by return email or telephone and > permanently delete this message and attachment(s) from your system.

2 1