On Thu, 17 Dec 2009, Peter Tribble wrote:
>>> I've just installed a bunch of T5240s with S10U8. I can ssh between some
>>> of
>>> the systems just fine, but ssh between some systems takes *ages* to
>>> connect,
>>> and one of them is reporting:
>>>
>>> sshd[766]: [ID 800047 auth.crit] fatal: Monitor not responding
>>>
>>> any hints where to look?
>>>
>>> (All systems identically built with jumpstart; I've done similar
>>> deployments
>>> in other datacenters without encountering this issue elsewhere.)
>>
>> Hi Peter -
>>
>> Are there any other errors? Sounds like all of the hardware is the
>> same, so that shouldn't be a difference (like if some had hardware
>> crypto acceleration and others ?didn't)
>>
>> I saw a similar bug filed internally and the problem seems to be
>> aggravated by problems with nameservices (if it's the same thing,
>> unfortunately, it looks like a few things can trip this message)
>
>Thanks.
>
>It's not the most helpful message, but I think that it was a nameservice
>(DNS) issue. At least, I made it go away by adding entries to /etc/inet/hosts.
hi Peter, the child has no idea why its daddy (the monitor)
decided to pass away :-) But yes, the message does not help much. The
problem is also that we issue the same message from more than one place
which makes it harder to deduce what is going on.
>It is somewhat of a concern, though, that sshd fails if DNS gets flaky.
if that's the case then yes, it's a problem we should definitely
fix. We track it by the CR below. If no one else gets to it before me I
hope(TM) I could fix it during the first quarter of 2010.
6895375 sshd issuing Monitor not responding message.
cheers, J.
--
Jan Pechanec
