Index: [Article Count Order] [Thread]

Date:  Fri, 31 Oct 2008 02:38:45 -0000
From:  "Howie Dines" <howie (at mark) howie.co.uk>
Subject:  [coba-e:14237] Re: ssh sshd problems.
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <891D409E966C41A8B86DE566F52F43AC@howies>
In-Reply-To:  <7AAE927A3EB54F0B9D79E3C00A29C591@howies>
References:  <7AAE927A3EB54F0B9D79E3C00A29C591@howies>
X-Mail-Count: 14237

Oop's almost forgot, also reset permissions on the null file

"chmod 666 /dev/null"

Best Regards,
Howie.

-----Original Message-----
From: Howie Dines [mailto:howie (at mark) howie.co.uk] 
Sent: 31 October 2008 02:27
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:14236] ssh sshd problems.

Since my last yum update I've not been able to ssh to one of my boxes.
The sshd wouldn't restart.

[root (at mark) ns1 /]# /etc/init.d/sshd start
Starting sshd:FAILED]

 
I've now found the solution and I wanted to share just in case anyone else
is having the same issue.
 
solution was found at
http://www.linuxquestions.org/questions/linux-networking-3/sshd-fatal-daemon
-failed-no-such-device-279664/
 
 
>the solution is in the /dev/null file. it should now be a regular file,
which is not recommended
>some install script probably replaced the /dev/null with a file of the 
>same
name...

>do the following:
>remove "rm /dev/null"
>and then: "mknod /dev/null c 1 3"

>this will create the /dev/null and sshd should start as normal.
 
 
Best Regards,
Howie.