Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
What can I do to resolve the following? This is in /var/log/messages
Aug 25 18:18:14 NAS auth.info sshd[1766]: Server listening on 0.0.0.0 port 22. Aug 25 18:18:14 NAS auth.err sshd[1766]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Aug 25 18:18:14 NAS daemon.err inetd[1804]: ssh/tcp: bind: Address already in use Aug 25 18:19:14 NAS daemon.err inetd[1804]: ssh/tcp: bind: Address already in use
Thanks
Offline
Hi
It seems that the IP address that you DNS-323 has, is already in use and that why it can't set the ip address (that's why you have the 0.0.0.0)
Do you have a DHCP server? If you do, then a simple restart should do the trick. If you put the IP manually, then someone might have the same IP address.
Let me know if that helps.
Offline
the ip above is literally 0.0.0.0. I didnt change it. And im still able to ssh in. I should have added that im trying to get denyhosts working.
Offline
I am curious how you get the IP 0.0.0.0. Usually it means that it doesn't have an IP.
Let me read the denyhosts installation.
Can you actually ping 0.0.0.0 from another machine??What's the result of an ifconfig? Do you have nmap in any machine?
Offline
Interesting. When I ping 0.0.0.0 it resolves to 127.0.0.1
Offline
Ok. So thats localhost. Can you try to put a static IP in the range of your subnet?
Did your DNS always work like this or this was something you did to install denyhosts?
Let me be honest, I haven't install it. From what I saw, it seems it replaces the ssh server. It might be a limitation, which it can't bind to a 0.0.0.0 address.
I am going to bed now, sorry.
I'll check this post in about 7 hours.
Last edited by blizzard182 (2008-08-26 08:17:42)
Offline
Got it. For some reason, sshd.sh was still set to execute. I changed it to chmod a-x /ffp/start/sshd.sh and that resolved the issue. inetd is starting sshd and sshd is also trying to start
Offline
Great. I guess that error message wasn't that descriptive.
Anyway. Good news.
Cheers
Offline
The message "address already in use" is a bit tricky as it is not really what it says it is: it means that some process is already listening on the same port.
Here you already had some sshd process listening to port 22; by removing the exec bit from /ffp/start/sshd.sh, you managed to disable the first one and then the other one (started through inetd??) could start without any message.
Offline