check_http throwing 141 exit on ssl error

[Mike Lindsey]

I'm typically used to seeing this kind of error code for a missing 
plugin, but I've got a device that is accepting tcp connections and then 
due to a local misconfiguration, immediately closing them.

But rather than a normal critical I'm getting:
"""
(Return code of 141 is out of bounds)
"""

When run by hand I have:
"""
root at ops-mon-nagios3 /usr/local/nagios/libexec $ ./check_http -H 
device.domain.com -w "10" -c "20" -S -p "83" -f follow
CRITICAL - Cannot make SSL connection
root at ops-mon-nagios3 /usr/local/nagios/libexec $ echo $?
141
"""

Anyone seen this before?  Is this resolved in nagios-plugins > 1.4.15?

Here's some potentially useful, lightly filtered strace output, showing 
it exiting on a SIGPIPE:
"""
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(83), 
sin_addr=inet_addr("68.232.133.59")}, 16) = 0
write(3, "\200w\1\3\1\0N\0\0\0 
\0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 
ECONNRESET (Connection reset by peer)
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x2ab9e22dd000
write(1, "CRITICAL - Cannot make SSL conne"..., 39) = 39
write(3, "\200w\1\3\1\0N\0\0\0 
\0\0009\0\0008\0\0005\0\0\26\0\0\23\0\0\n\7\0\300"..., 121) = -1 EPIPE 
(Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
+++ killed by SIGPIPE +++



-- Mike Lindsey

-- 
Mike Lindsey


------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null