On 9/14/12 11:25 AM, Justin T Pryzby wrote:
> This may be unrelated to the question of why it's exiting with a
> nonstandard, out of range exit status, but is port 83 really HTTP over
> SSL? It seems as if the plugin sent an ssl initiation, and the remote
> side closed the connection (perhaps beca
On 09/14/2012 08:09 PM, Mike Lindsey wrote:
> 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
This may be unrelated to the question of why it's exiting with a
nonstandard, out of range exit status, but is port 83 really HTTP over
SSL? It seems as if the plugin sent an ssl initiation, and the remote
side closed the connection (perhaps because it wasn't ssl?).
Later, the plugin tried to gra
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)
"""
Whe