Hi list, seems I have a little problem there. On a SuSE 6.4 system (kernel 2.2.19) that I am administering which is running mainly as a mailserver (smtp & pop3) I recently updated libz by fetching the sources from ftp.suse.com and doing a rpm -bb libz... and then rpm -Uhv libz... Anyway, for remote administration I use ssh (latest version available for 6.4) and access is restricted via /etc/hosts.deny. Also protocol version 1 is disabled. The next time (after I updated libz) I could not log in anymore, this is what I get when I try to connect from any of the allowed IP addresses: ssh_exchange_identification: Connection closed by remote host Could it be that the newly installed libz is the reason? I have checked with ldd /usr/sbin/sshd and it tells me on all my other systems that its linked against /usr/lib/libz.so.1 So now the big question: can the libz update really be the reason or is it more likely that I messed something else up that I can't remember? Or in other words: do I have to drive ~ 550 kilometers to fix that server or is there any other way to be able to log in again :-) Thanks in advance for all your help! Erwin -- Erwin Zierler | web- / host- / postmaster - stubainet.at | erwin.zierler@stubainet.at / webmaster@stubainet.at | Tel.: 0 5225 - 64325 Fax 99 Mobil: 0664 - 130 67 91
Yuppa, "Erwin Zierler - stubainet.at" wrote:
Hi list,
[...]
The next time (after I updated libz) I could not log in anymore, this is what I get when I try to connect from any of the allowed IP addresses:
ssh_exchange_identification: Connection closed by remote host
Could it be that the newly installed libz is the reason? I have checked with ldd /usr/sbin/sshd and it tells me on all my other systems that its linked against /usr/lib/libz.so.1
So now the big question: can the libz update really be the reason or is it more likely that I messed something else up that I can't remember? [...]
I think you're screwed! ;) Seriously, I once had a similar problem. It was caused by an improper tcpwrapper configuration. Take a look at O'Reilly's SSH FAQ (taken from "SSH: The definitive guide"): http://www.snailbook.com/faq/libwrap-oops.auto.html Now, get a tank full of gas...!
Erwin
Boris Lorenz <bolo@lupa.de> ---
Hi, did you restart the sshd (or reload the conf.) after updating the libz-package? Regards Ruediger
participants (3)
-
Boris Lorenz
-
Erwin Zierler - stubainet.at
-
ic_admin