Date: Mon, 05 Aug 2002 14:32:30 +0900 (KST) From: CHOI Junho <cjh@kr.FreeBSD.org> To: spork@inch.com Cc: dan@langille.org, FreeBSD-stable@FreeBSD.ORG Subject: Re: remote upgrade stops ssh connections Message-ID: <20020805.143230.106797934.cjh@kr.FreeBSD.org> In-Reply-To: <Pine.BSF.4.44.0208050114030.22536-100000@shell.inch.com> References: <20020805.130519.124046267.cjh@kr.FreeBSD.org> <Pine.BSF.4.44.0208050114030.22536-100000@shell.inch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Charles Sprickman <spork@inch.com> Subject: Re: remote upgrade stops ssh connections Date: Mon, 5 Aug 2002 01:17:11 -0400 (EDT) > On Mon, 5 Aug 2002, CHOI Junho wrote: > > > There's another thread about this issue in -stable(Subject contains > > "PAM... HELP!!") may help you. I faced exact same problem at Saturday > > for 3 FreeBSD machines in the data center far from my office. Only > > solution to this is just rebooting. I had to reboot all these machines > > today morning, it works good without any work. > > You need not reboot. kill -HUP `cat /var/run/sshd.pid` will do just fine. > Some shared libs sshd uses (pam stuff I assume) gets pulled out from under > it and it (rightly) gets upset about this. HUP'ing it will restart it and > it will work fine. It will *not* kill you existing connection, only the > parent process. At first machine, I typed "killall -1 sshd". All my session disconnected and I couldn't login. At second machine, I typed "(killall -9 sshd; /usr/sbin/sshd)" and the same thing happened. At third machine I did it again but it doesn't help. Some people said just restarting sshd works, but for some people like me it doesn't work. I upgraded 4.6-RELEASE-p1 -> 4.6.1-RELEASE-p7. > Just did this 10 minutes ago. Saw this in the logs: > > ug 4 23:04:17 bigpoop sshd[36676]: unable to dlopen(/usr/lib/pam_skey.so) > Aug 4 23:04:17 bigpoop sshd[36676]: [dlerror: /usr/lib/pam_skey.so: > Undefined symbol "pam_set_option"] > Aug 4 23:04:17 bigpoop sshd[36676]: adding faulty module: > /usr/lib/pam_skey.so > Aug 4 23:04:17 bigpoop sshd[36676]: unable to > dlopen(/usr/lib/pam_unix.so) > Aug 4 23:04:17 bigpoop sshd[36676]: [dlerror: /usr/lib/pam_unix.so: > Undefined symbol "pam_test_option"] > Aug 4 23:04:17 bigpoop sshd[36676]: adding faulty module: > /usr/lib/pam_unix.s > > HUP'd and all was well. > > Charles > > > If someone wish to upgrade -stable or RELENG_4_6, I recommend to open > > telnet port(SRA login only...) for a moment for just safety. I had > > trouble for rebooting at the console because this machine has no > > keyboard and plugging keyboard doesn't help without some kernel > > option! :< > > > > From: "Dan Langille" <dan@langille.org> > > Subject: remote upgrade stops ssh connections > > Date: Sun, 4 Aug 2002 18:52:59 -0400 > > > > > I've lost ssh contact with a remote boxes which is halfway through an > > > upgrade. I think it has completed their "make install" but the ssh > > > connection was dropped[1]. But if I try to ssh to them, I get an > > > "S/Key Password:" prompt. After a few garbage, replies, I do get a > > > password prompt, but the correct password is being rejected. Here is > > > what is appearing in /var/log/messages[2]: > > > > > > Aug 5 08:40:25 reg sshd[23976]: unable to > > > dlopen(/usr/lib/pam_skey.so) > > > 08:40:26 reg sshd[23976]: Failed password for dvl from a.b.c.d port > > > 62763 > > > Aug 5 08:40:25 reg sshd[23976]: [dlerror: /usr/lib/pam_skey.so: > > > Undefined symbol "pam_set_option"] > > > Aug 5 08:40:25 reg sshd[23976]: adding faulty module: > > > /usr/lib/pam_skey.so > > > Aug 5 08:40:25 reg sshd[23976]: unable to > > > dlopen(/usr/lib/pam_unix.so) > > > Aug 5 08:40:25 reg sshd[23976]: [dlerror: /usr/lib/pam_unix.so: > > > Undefined symbol "pam_test_option"] > > > Aug 5 08:40:25 reg sshd[23976]: adding faulty module: > > > /usr/lib/pam_unix.so > > > Aug 5 08:40:26 reg sshd[23976]: Failed password for dvl from a.b.c.d > > > port 62763 > > > Aug 5 08:40:27 reg sshd[23976]: Received disconnect from a.b.c.d: > > > > > > Am I going to need to get to the console on this one? > > > > > > [1] - yes, thanks to those thinking serial connection. It's not an > > > answer here. > > > > > > [2] - thanks to security/logcheck which is mailing me these reports. > > > -- > > > Dan Langille > > > I'm looking for a computer job: > > > http://www.freebsddiary.org/dan_langille.php > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > > +++ Any opinions in this posting are my own and not those of my employers +++ > > CHOI Junho [sleeping now] <http://www.kr.FreeBSD.org/~cjh>; > > [while sleeping] <cjh @ kr.FreeBSD.ORG> <cjh @ FreeBSD.ORG> <cjh @ wdb.co.kr> > > Korea FreeBSD Users Group <www.kr.FreeBSD.org> Web Data Bank<www.wdb.co.kr> > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [sleeping now] <http://www.kr.FreeBSD.org/~cjh>; [while sleeping] <cjh @ kr.FreeBSD.ORG> <cjh @ FreeBSD.ORG> <cjh @ wdb.co.kr> Korea FreeBSD Users Group <www.kr.FreeBSD.org> Web Data Bank<www.wdb.co.kr> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020805.143230.106797934.cjh>