This may indicate an SSL negotiation failure or timeout. Running tcpdump
may confirm a timeout.
Packets from an SSL session can be inspected in Wireshark and ssldump, if
you can get access to the private key.
If this happens only a few times a week, you may want to just use
"DELAYRED" (see hosts.cfg) to allow xymonnet to try again a minute later.
J
On 2 July 2018 at 20:53, Jonas Weber <mail at jonasw.de> wrote:
> Hello,
>
> in our Xymon installation we are experiencing red HTTP status 0 alerts
> repeatedly, about a few times per week. This phenomenon started appearing
> when we switched the backend from Apache to nginx. The monitored service is
> checked over an SSL connection, making tcpdump et al. difficult to use.
> Additionally, this only appears on our production monitoring; a secondary
> installation with only this check does not show this issue. So, debug
> logging isn't really feasible, either (although I've tried).
>
> At this point, we are quite certain that it is a monitoring artifact and
> not a problem of the service, as there are no errors on the nginx side of
> things, and no customers have complained, either.
>
> I've looked in the code of xymonnet. I think status code 0 might mean that
> no HTTP/1.x response has been received, or at least that Xymon was unable
> to parse it. Is that correct? Does/did anybody else face this problem?
>
> Best regards,
> Jonas
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
>
Looks like the Xymon SNMP code is only partially working. More details in
this thread:
http://lists.xymon.com/archive/2015-April/041585.html
On 4 July 2018 at 18:57, Nikolya <sitrix at camheds.net> wrote:
> Hello
>
> It seems that there are already exists much of
> the code for snmp polling and analysing in xymon.
>
> There are handle_snmpcollect_client func in
> xymond_client.c, that calling check_mibvals, which
> in turn call get_mibval_thresholds, wich in turn
> using data from load_client_config
>
> From quick reading of load_client_config function
> definition, i do not undestand how exactly i need
> to define MIB rules in analysis.cfg
>
> But what absent is a testing module for
> xymond_client, when running with --test.
> So there is no easy why to test SNMP rules.
>
> Because testmode function in xymond_client.c
> do not provide this testing.
>
> I will gladly beta test the code that close this
> gap, but i'm not that C pro developer to create
> it from scratch.
>
> Lets be clear, DevMon is good and ancient, but why not use
> what we already have in a code base
>
>
> --
> WBR Nikolay
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
>
Only English.
On 13 July 2018 at 19:34, Poorlupadi, Chethana <Chethana.Poorlupadi at colt.net
> wrote:
> Hi Team,
>
>
>
> Could any one of you let me know what are the different languages
> supported by Xymon?
>
>
>
> Thanks,
>
> Chethana
>
>
> [Colt Disclaimer] This email is from an entity of the Colt group of
> companies. Colt Group S.A., K2 Building, Forte 1, 2a rue Albert Borschette,
> L-1246 Luxembourg, R.C.S. B115679. Corporate and contact information for
> our entities can be found at http://colt.net/uk/en/Colt-
> Group-of-Companies/index.htm. Internet communications are not secure and
> Colt does not accept responsibility for the accurate transmission of this
> message. Content of this email or its attachments is not legally or
> contractually binding unless expressly previously agreed in writing by Colt
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
>
Dave
A strange problem indeed. I've scanned the relevant parts of the code, and
it all checks out, according to my amateur knowledge of C. What you're
trying to do should work just fine.
I wonder if it's just a coincidence that your group name starts with a
7-letter word. Probably.
Perhaps you could have xymond_client run in debug mode (adding "--debug" in
tasks.cfg), and see if it shows any clues in the log.
FYI, another check the process status, without using the web interface
(lynx/curl/wget) is to use the xymon command:
$ xymoncmd
$ XYMON $XYMONCMD "query balin2012.mydomain.testnet.procs"
yellow Wed Jul 11 13:29:40 2018 - Processes NOT ok
... (etc)
J
On 12 July 2018 at 06:42, Dave "doughnut" Fogarty <doughnut at doughnut.net>
wrote:
> I have a xymon server running "Debian GNU/Linux 9 (stretch)" with xymon
> 4.3.28-2. I'm having bad luck getting DISPLAYGROUP to work in
> analysis.cfg. It seems to only match on the first 7 characters.
>
> I also see this problem on "Debian GNU/Linux 8 (jessie)" with xymon
> 4.3.17-6+deb8u1.
>
> Below, I've shown that the display group is set, and that the analysis.cfg
> file is being parsed correctly by xymon, yet the the svcstatus page only
> shows the shortest of the DISPLAYGROUP enabled lines.
>
>
> root at misc-ten105-test:/etc/xymon# egrep -H Testnet.Database.Servers
> hosts.cfg hosts.cfg:group Testnet Database Servers
>
> root at misc-ten105-test:/etc/xymon# cat analysis.d/davetest.cfg HOST=*
> EXCLASS=linux
> PROC davetest-nonlinux 1 150 yellow
> PROC davetest-Testnet.Database.Servers 1 150 yellow
> DISPLAYGROUP=%(Testnet.Database.Servers)
> PROC davetest-Database 1 150 yellow DISPLAYGROUP=%(Database)
> PROC davetest-Databas 1 150 yellow DISPLAYGROUP=%(Databas)
> PROC davetest-Testnet.Database 1 150 yellow
> DISPLAYGROUP=%(Testnet.Database)
> PROC davetest-Testnet.Data 1 150 yellow
> DISPLAYGROUP=%(Testnet.Data)
> PROC davetest-Testnet.D 1 150 yellow DISPLAYGROUP=%(Testnet.D)
> PROC davetest-Testnet. 1 150 yellow DISPLAYGROUP=%(Testnet.)
> PROC davetest-Testnet 1 150 yellow DISPLAYGROUP=%(Testnet)
> PROC davetest-Testne 1 150 yellow DISPLAYGROUP=%(Testne)
>
>
> root at misc-ten105-test:/etc/xymon# sudo -u xymon xymoncmd xymond_client
> --dump-config | grep davetest
> [...]
> PROC davetest-nonlinux 1 150 yellow HOST=* EXCLASS=linux (line: 375)
> PROC davetest-Testnet.Database.Servers 1 150 yellow HOST=*
> DISPLAYGROUP=%(Testnet.Database.Servers) EXCLASS=linux (line: 377)
> PROC davetest-Database 1 150 yellow HOST=* DISPLAYGROUP=%(Database)
> EXCLASS=linux (line: 378)
> PROC davetest-Databas 1 150 yellow HOST=* DISPLAYGROUP=%(Databas)
> EXCLASS=linux (line: 379)
> PROC davetest-Testnet.Database 1 150 yellow HOST=*
> DISPLAYGROUP=%(Testnet.Database) EXCLASS=linux (line: 380)
> PROC davetest-Testnet.Data 1 150 yellow HOST=*
> DISPLAYGROUP=%(Testnet.Data) EXCLASS=linux (line: 381)
> PROC davetest-Testnet.D 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet.D)
> EXCLASS=linux (line: 382)
> PROC davetest-Testnet. 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet.)
> EXCLASS=linux (line: 383)
> PROC davetest-Testnet 1 150 yellow HOST=* DISPLAYGROUP=%(Testnet)
> EXCLASS=linux (line: 384)
> PROC davetest-Testne 1 150 yellow HOST=* DISPLAYGROUP=%(Testne)
> EXCLASS=linux (line: 385)
>
>
> root at misc-ten105-test:/etc/xymon# lynx -dump -nolist '
> http://localhost/xymon-cgi/svcstatus.sh?HOST=balin2012.coll
> egenet.testnet&SERVICE=procs'
> [...]
> Xymon
>
> balin2012.mydomain.testnet - procs
>
> Wed Jul 11 13:29:40 2018
> _______________________________________________________________________
>
>
> HISTORY
>
> Wed Jul 11 13:29:40 2018 - Processes NOT ok
>
> yellow davetest-nonlinux (found 0, req. between 1 and 150)
> yellow davetest-Testnet (found 0, req. between 1 and 150)
> yellow davetest-Testne (found 0, req. between 1 and 150)
>
>
>
> Status unchanged in 8 days, 21 hours, 22 minutes
> Status message received from 10.101.1.35
> Client data available
>
>
>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
On 31 July 2018 at 05:35, Gabo Suárez <jgsuareza1984 at gmail.com> wrote:
> Hi greetings from Ecuador,
>
Hello Gabo
> Please your help, I need that the XYMON monitoring mails include the IP of
> the host-client
>
> How do i do it?
>
The IP address of the client is in the variable $MACHIP. I think this
variable is only available to scripts, not the standard MAIL function. To
do this, you can create a script that sends an email.
For example, use this in alerts.cfg:
HOST=client.host.name
SCRIPT /usr/local/bin/mailscript placeholder FORMAT=TEXT
Then create a script that goes something like this:
#!/bin/sh
mail -s "$BBHOSTNAME $BBSVCNAME - $BBCOLORLEVEL $ACKCODE $RECOVERED
$DOWNSECMSG" $RCPT <<EOF
$BBALPHAMSG
IP is $MACHIP
EOF
For more information about the Xymon alert environment variables, check out
the Alerts documentation:
http://xymon.sourceforge.net/xymon/help/xymon-alerts.html
and the alerts.cfg man page:
http://xymon.sourceforge.net/xymon/help/manpages/man5/alerts.cfg.5.html
J