Hello,
We are running Xymon with xymonnet version 4.3.26-1.el6.terabithia and SSL library : OpenSSL 1.0.1e 11 Feb 2013 (CentOS release 6.8).
Sporadically we see errors testing a certain host with imaps and pop3s tests.
The errors are as follows:
TCPtest error 4 seen on open connection for $x.imaps
TCPtest error 4 seen on open connection for $x.pop3s
.. where $x is a few random extended ASCII characters
A commonality is that these are both SSL/TLS enabled services hosted on the same system. pop3s is configured as port 995 with SSL/TLS required and imaps is port 993 with SSL/TLS required.
My gut tells me this is probably related to SSL/TLS negotiation problems.
Any recommendations on where to start?
Thanks,
Kirk MacDonald System Administrator Internet Eastlink
On Thu, Aug 11, 2016 at 2:00 AM Kirk MacDonald < Kirk.MacDonald at corp.eastlink.ca> wrote:
The errors are as follows:
TCPtest error 4 seen on open connection for $x.imaps
TCPtest error 4 seen on open connection for $x.pop3s
.. where $x is a few random extended ASCII characters
If I'm not mistaken, the error codes are defined in contest.h. Error 4 is:
#define CONTEST_EIO 4
This means "I/O error". When trying to write to an apparently open socket, the number of bytes written was zero. It might indicate that the remote end closed the socket, and it's not until the write took place that the local socket layer saw the closure. If you run xymonnet with "--debug" enabled, you might see "write failed" in the log.
To confirm, perhaps do a packet trace on the communication. And/or look at the logs on the device being probed, to see if it's aborting the connection for policy reasons.
The weird $x values seem to be a bug in xymonnet.c, where the code treats "test->host" as the hostname, whereas it's actually a structure with lots of host details. This should be "test->host->ip". But it won't cause your "error 4" problem.
J
participants (2)
-
jlaidman＠rebel-it.com.au
-
Kirk.MacDonald＠corp.eastlink.ca