[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wierd monit/sshd interaction

From: Martin Pala
Subject: Re: Wierd monit/sshd interaction
Date: Mon, 29 Jul 2002 00:10:23 +0200


tried to reproduce this failure, but on redhat 7.3 it works good.

I think that your problem could be in umask (maybe system-wide), while in
strace it seems all good. Agent socket is created under correct user with
correct mode and the only reason why bind() can fail is, that the parent
directory created by:

  mkdir("/tmp/ssh-XXJ6demX", 0700)

under which bind() tries to create named socket:

  bind(10, {sin_family=AF_UNIX, path="/tmp/ssh-XXJ6demX/agent.23332"}, 110)
= -1 EACCES (Permission denied)

 has other mode then requested => one or more of RWX rights are umasked when
started under monit. Maybe your root user has other (non-default) umask - it
can be the cause of this strange behavior.


----- Original Message -----
From: "Mark Ferlatte" <address@hidden>
To: <address@hidden>
Sent: Thursday, July 25, 2002 11:52 PM
Subject: Re: Wierd monit/sshd interaction

> On Thu, Jul 25, 2002 at 10:52:56PM +0200, Martin Pala wrote (1.00):
> > it is strange - maybe the problem could be in sshd. Can you attach
> > from monits strace as described in FAQ or strace of sshd in the time of
> > start as outlined bellow?
> I've narrowed the problem down even more... if the user has ForwardAgent
> no, then it works fine.  I've attached an strace of monit restarting
> sshd, and me attempting to connect (since strace appears to trace
> children, no need for the second trace).  sshd's PID is 23318, and you
> can see that it fails to bind to /tmp/ssh-XXJ6demX/agent.23332, which
> causes the (admittedly very poor) error message to be returned to the
> client.
> What it doesn't explain, however, is why this happens only when monit
> starts sshd...
> Trace attached.
> M

reply via email to

[Prev in Thread] Current Thread [Next in Thread]