Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
A few days ago SSH just failed on me, after reboot.
Everytime I start sshd (/etc/rc.d/rc.sshd start), this appears in the syslog
Jan 17 22:51:18 server sshd: fatal: daemon() failed: No such device
I can run ssh in debug mode (sshd -d) and it runs fine. It just when it tried to daemonise itself that it fails. I was configuring before samba and postfix. I did a strace on working and not workind sshd daemon and they looked exactly the same.
My linux distribution is Slackware 10.0
Click here to see the post LQ members have rated as the most helpful post in this thread.
Any idea what device the sshd daemon is trying to access. You could perhaps try: grep -n '/dev/' /etc/rc.d/rc.sshd, but this would just help if the error occurred in the script and not the sshd binary.
Do you have either a /dev/random or /dev/psuedo device, as well as a /dev/null device.
Also, does your ssh daemon run in a jail? If so, there may be needed devices that need to be in jails dev directory.
Maybe someone would have more ideas. Perhaps grep'ing all of the ssh config files for the '/dev/' string may help.
I found out after "strace"-ing. after the log files failed on me, I logged in as root, stopped sshd with /etc/init.d/sshd stop, just to make sure, and typed in the following command:
strace -f sshd 2>&1 | tee sshd.straceout
I looked at the output, searching for "daemon()" and found it, after or close to some special file opening syscalls. It had to do with /dev/null. So I checked that file for existance. it did exist, so looked at the file more closely and saw, it now was a huge and regular file.