Have you updated glibc too?
netstat -tunp | grep 22
should tell which process is using port 22, also try:
netstat -tunl | grep 22
to see if someone is listening in port 22
After I updated to latest openssh, I got the same message in
/var/log/secure,
but none process was using port 22.
But, I still can login via ssh:
# tail /var/log/secure
Mar 23 04:05:53 mpl sshd[17969]: Server listening on :: port 22.
Mar 23 04:05:53 mpl sshd[17969]: error: Bind to port 22 on 0.0.0.0
failed: Address already in use.
# ssh localhost
root@localhost's password: ....
Will try rebooting the server ..
HTH
Oliver
Jerry Geis wrote:
> I had trouble with the update to 4.3.
>
> /usr/sbin/sshd -d -D is telling me some other process is
> using port 22 and cant bind to it.
>
> How do I tell what program that is and stop it?
>
> Thanks,
>
> Jerry
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
--
Oliver Schulze L.
<oliver@xxxxxxxxxxxxx>
