- Xymon - Xymon mailman web

Xymon Server on RHEL9
by colin.coe＠gmail.com 29 Nov '23

29 Nov '23

Hi all I'm getting ready to replace our venerable RHEL6 Xymon server with one running RHEL 9. We use the terabithia.org RPMs. NTP tests are all returning red. I've updated xymonserver.cfg (and restarted the xymon service) by changing NTPDATE="/usr/bin/chronyc" and adding NTPDATEOPTS="tracking". When I run "/usr/bin/chronyc tracking <IP HERE>" from the shell, it works fine however the Xymon page is red. Service ntp on <CENSORED> is not OK : Service unavailable Command: /usr/bin/chronyc tracking <CENSORED> 2>&1 Any ideas?

5 5

'Invalid timespec' in xymond.log
by john.thurston＠alaska.gov 27 Nov '23

27 Nov '23

I'm seeing messages like this > Invalid timespec - expected 4 digits, got: '*:*' > Invalid timespec - expected 4 digits, got: '*' > Invalid timespec - expected 4 digits, got: '*:*' > Invalid timespec - expected 4 digits, got: '*' pop up in my xymond.log. They've been there for ages, so this is nothing new. I've poked at them before, to no satisfaction. I think this came out of the 'minutes' function in lib/timefunc.c But what was the input which was passed through that function, to generate the error? I have 'DOWNTIME' specifications like > DOWNTIME=60:*:*;*:1630:0800 > But there are 21 of those in hosts.cfg, and I don't have that many complaints in the log. Does anyone else have a suggestion where to look? or how to interactively run some parsing commands to tease out the source? Maybe that function is used for more than parsing the configs? Could the source of the errors be from messages passed into the server from clients? -- -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Department of Administration State of Alaska

2 2

Acknowledgements and page color.
by cleaver＠terabithia.org 09 Nov '23

09 Nov '23

On Thu, November 9, 2023 11:35, Grant Taylor wrote: > On 11/8/23 11:46???AM, J.C. Cleaver wrote: >> This isn't something currently there, but I could see adding it in >> in the future as an option or toggle. > > That would be nice to have. :-) > >> For the moment, the distinction here between one Ack'd and one >> a page-viewer "doesn't need to care about" would be achieved by >> sending a "Disabled until OK" message, which sets the color to the >> non-alerting Blue. > > Yep, that's what we've been doing. > > But I figured I'd stop and ask instead of doing the same thing has > always been done out of ignorance. > > I should clarify that I was referring to the individual status pages for a host (pulled live via svcstatus.cgi, or a static HTML generation if enabled). If you want to prevent an entire *page* from reflecting the worst status if that status has been acked, you can pass the --nopropack=* option to xymongen in your tasks.cfg entry. See https://xymon.sourceforge.io/xymon/help/manpages/man1/xymongen.1.html -jc

1 0

Acknowledgements and page color.
by cleaver＠terabithia.org 09 Nov '23

09 Nov '23

On Wed, November 8, 2023 09:24, Grant Taylor wrote: > Hi, > > Is there any way to have the page color go back to green when a yellow / > red / purple is acknowledged? > > Or will the page color always and forever reflect the worst color > (purple -> yellow -> red) on the page? > > This isn't something currently there, but I could see adding it in in the future as an option or toggle. For the moment, the distinction here between one Ack'd and one a page-viewer "doesn't need to care about" would be achieved by sending a "Disabled until OK" message, which sets the color to the non-alerting Blue. -jc

2 1

Missing support for HTTP/2 ?
by jeremy＠laidman.org 08 Nov '23

08 Nov '23

On Wed, 8 Nov 2023 at 23:14, Ingeborg Hellemo via Xymon <xymon at xymon.com> wrote: > > ~/server/bin/xymonnet --debug --no-update <servername> > > 35422 2023-11-08 13:06:06.168385 1 status messages merged into 1 > transmissions > Address=[IP]:443, open=1, res=0, err=5, connecttime=0.000303, > totaltime=0.002631, > httpstatus = -5, open=1, errcode=5, parsestatus=0 > Response: > (no headers) > URL : https://<servername>/ > HTTP status : -5 > I'm surprised there isn't some kind of error message being displayed. err=5 is "CONTEST_ESSL" meaning something went wrong in the SSL comms, or setup. In most cases where the error code is set to CONTEST_ESSL, there's an "errprintf()" that describes the error. I'd have thought "--debug" would show these on STDERR. The missing error message is likely going to help narrow down the problem. These are all of the error messages in contest.c where err is set to CONTEST_ESSL: errprintf("SSL test, but xymonnet was built without SSL support\n"); errprintf("Failed to find enough entropy on your system"); errprintf("Cannot create SSL context - IP %s, service %s: %s\n", inet_ntoa(item->addr.sin_addr), item->svcinfo->svcname, sslerrmsg); errprintf("Cannot load SSL client certificate/key %s: %s\n", item->ssloptions->clientcert, sslerrmsg); errprintf("SSL_new failed - IP %s, service %s: %s\n", inet_ntoa(item->addr.sin_addr), item->svcinfo->svcname, sslerrmsg); errprintf("Private/public key mismatch for certificate %s\n", item->ssloptions->clientcert); errprintf("Could not initiate SSL on connection - IP %s, service %s: %s\n", inet_ntoa(item->addr.sin_addr), item->svcinfo->svcname, sslerrmsg); errprintf("IO error in SSL_connect to %s on host %s: %s\n", portinfo, inet_ntoa(item->addr.sin_addr), sslerrmsg); errprintf("Unspecified SSL error in SSL_connect to %s on host %s: %s\n", portinfo, inet_ntoa(item->addr.sin_addr), sslerrmsg); errprintf("Unknown error %d in SSL_connect to %s on host %s: %s\n", err, portinfo, inet_ntoa(item->addr.sin_addr), sslerrmsg); errprintf("Cannot get peer certificate for %s on host %s\n", portinfo, inet_ntoa(item->addr.sin_addr)); Perhaps these can give you some clues about what might be going wrong. I also suggest taking a look at the webserver logs for any errors, warnings or notice messages associated with the xymonnet connection. J

1 0

Acknowledgements and page color.
by gtaylor＠tnetconsulting.net 08 Nov '23

08 Nov '23

Hi, Is there any way to have the page color go back to green when a yellow / red / purple is acknowledged? Or will the page color always and forever reflect the worst color (purple -> yellow -> red) on the page? -- Grant. . . . unix || die

1 0

Missing support for HTTP/2 ?
by tom＠4schmidts.com 08 Nov '23

08 Nov '23

Ingeborg, HTTP/2 support is currently not in xymon, including in the 4.4alpha1 development tree. I did a little testing, and sites like google that support HTTP/2 still pass the xymonnet checks as seen below: $ curl --head https://www.google.com | head -1 HTTP/2 200 $ grep google ~/server/etc/hosts.cfg 0.0.0.0 www.google.com # conn https://www.google.com/ $ ~/server/bin/xymonnet --no-update www.google.com |grep -B2 HTTP &green https://www.google.com/ - OK HTTP/1.1 200 OK $ ~/server/bin/xymonnet --no-update www.google.com |grep -i ssl status+30 www,google,com.sslcert green Wed Nov 1 08:38:21 2023 &green SSL certificate for https://www.google.com/ expires in 2252 days Perhaps the website you are testing is configured to support HTTP/2 and not support HTTP/1? Try running the xymonnet command manually similar to what I did here. Tom Schmidt On Wed, Nov 1, 2023 at 7:28?AM Ingeborg Hellemo via Xymon <xymon at xymon.com> wrote: > > > > ---------- Forwarded message ---------- > From: Ingeborg Hellemo <ingeborg.hellemo at uit.no> > To: xymon at xymon.com > Cc: > Bcc: > Date: Wed, 01 Nov 2023 14:21:04 +0100 > Subject: Missing support for HTTP/2 ? > I have a webserver which works ok when you visit it in a browser or when > you > use curl, but Xymon http test shows "SSL error". Tests with "openssl > s_client" > from the command line works as expected. > > Could the culprit be that xymonnet does not support HTTP/2 ? > > > /#curl --head https://<servername>/ > HTTP/2 200 > cache-control: private > content-length: 4423 > content-type: text/html > strict-transport-security: max-age=31536000 > date: Wed, 01 Nov 2023 13:15:44 GMT > > > > > --Ingeborg > -- > Ingeborg ?strem Hellemo -- ingeborg.hellemo at uit.no > Dep. of Information Technology --- Univ. of Troms? > > > > > > ---------- Forwarded message ---------- > From: Ingeborg Hellemo via Xymon <xymon at xymon.com> > To: xymon at xymon.com > Cc: > Bcc: > Date: Wed, 01 Nov 2023 14:21:04 +0100 > Subject: [Xymon] Missing support for HTTP/2 ? > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon >

2 1

How capable is the `expect` & `send` in protocols.conf?
by cleaver＠terabithia.org 07 Nov '23

07 Nov '23

On Sun, November 5, 2023 19:40, Grant Taylor wrote: > Hi, > > How capable is the `expect` and `send` in protocols.conf? > > I'm wondering if I can have multiple instances of `expect` and / or > `send` for the same protocol definition. > > My current use case is for monitoring of an SMTP server that's using > multi-line SMTP greetings. > > 220-first line > 220 second line > > I want to use the following in protocols.conf but I'm not sure if it > will work as desired or not. > > expect "220-" > expect "220 " > send "QUIT" > > I'd like Xymon to send "QUIT" /after/ it receives the "220 " line (with > space). Grant, Unfortunately, xymonnet does not implement the full expect framework. Based on a re-examination of xymonnet.c and contest.c, I believe we're just sending the 'send' buffer once, and then collecting whatever is available in response. The actual comparison (to the "expect" line) looks to be done later on, when we're deciding colors and creating the status message results. IIRC, the lack of delay in waiting for results has caused problems in some tests before... possibly specifically with SMTP, actually. (HTTP requests aren't handled the same way, and will always return the full payload back if configured to retrieve the results.) -jc

2 1

How capable is the `expect` & `send` in protocols.conf?
by gtaylor＠tnetconsulting.net 06 Nov '23

06 Nov '23

Hi, How capable is the `expect` and `send` in protocols.conf? I'm wondering if I can have multiple instances of `expect` and / or `send` for the same protocol definition. My current use case is for monitoring of an SMTP server that's using multi-line SMTP greetings. 220-first line 220 second line I want to use the following in protocols.conf but I'm not sure if it will work as desired or not. expect "220-" expect "220 " send "QUIT" I'd like Xymon to send "QUIT" /after/ it receives the "220 " line (with space). -- Grant. . . . unix || die

1 0

Acknowledge alert for intermittent failure
by lolo＠troll.free.org 05 Nov '23

05 Nov '23

Hi, When acknowledging an alert for a specified delay , the acknowledge is cancelled when the service come back before the specified delay. If this is an intermittent failure (due to weather for example ) , we get a new alert before the specified delay and have to ack it again and again each time. How to make the ack valid for the specified delay even if the service come back before ? Regards, -- Laurent Frigault | Free.org - BookMyName.com - ONLINE SAS - Registar ID 74

2 1