Anyone else having issues with sshd on current?
Dec 15 23:23:24 stuff sshd[843]: fatal: ssh_msg_send: write
debug1: next auth method to try is keyboard-interactive
Connection closed by 192.168.1.66
debug1: Calling cleanup 0x804bed0(0x0)
__
Do you
sshd: fatal: ssh_msg_send: write
Timeout before authentication for x.x.x.x
I just cvusped my dev box again to -current.
Someone else on groups.google.com has this problem.
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=aojom0%2414v4%241%40FreeBSD.csie.NCTU.ed
At 08:31 PM 12/15/2002 -0800, David Yeske wrote:
Anyone else having issues with sshd on current?
Dec 15 23:23:24 stuff sshd[843]: fatal: ssh_msg_send: write
Yup, on a userland I built today. I see a few sshd commits
yesterday, relating to pam. Probably broke thereabouts
David Yeske wrote:
> >Anyone else having issues with sshd on current?
> >
> >Dec 15 23:23:24 stuff sshd[843]: fatal: ssh_msg_send: write
>
> Yup, on a userland I built today. I see a few sshd commits
> yesterday, relating to pam. Probably broke thereabouts... ?
>
>
11:26:41PM -0600, Christopher Schulte wrote:
> > At 08:31 PM 12/15/2002 -0800, David Yeske wrote:
> > >Anyone else having issues with sshd on current?
> > >
> > >Dec 15 23:23:24 stuff sshd[843]: fatal: ssh_msg_send: write
> >
> > Yup, on a userland
e console, I am seeing these
messages when I try to login:
sshd[2168]: fatal: ssh_msg_send: write
sshd[2171]: fatal: ssh_msg_send: write
If I restart my server with:
sshd -d -d -d
I get the following output:
debug3: mm_pam_init_ctx
debug3: mm_request_send entering: type 42
debug3: monitor
