[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sshd daemon failed to start



thanks a lot Mr jochen , sshd init script is working well after i remade /dev/null .
did you have any idea about what can change /dev/null to regular file.
perhaps i installed a package that did this big mistake , i don't know. ???????????????
i notice that something has changed keyboard config  from French to English at the same time when sshd was broken, i used dpkg-reconfigure console-data to resolve this.


On 3/29/07, Jochen Schulz <ml@well-adjusted.de> wrote:
Please don't top post.

anisadmin@gmail.com:
>
> unfortunately  the invoke-rc.d  didn't  succeeded to force sshd init, the
> output to stdout  is the echo sentence of start init script :
> Restarting OpenBSD Secure Shell server: sshd.

Strange. Looks perfect.

> despite set of log level debug3 in the sshd_config i found no log in syslog,
> note that my log config is:
> # Logging
> SyslogFacility AUTH

As I understand it, AUTH should still go to syslog (*and* auth.loh). But
nevermind.

> LogLevel DEBUG3
> Mar 29 12:53:19 fwnet sshd[5030]: fatal: daemon() failed: Success

Did you google already for that message? One hit I am finding suggests
to check that /dev/null is a character device, not a regular file. if it
doesn't look like this:

ls -lh /dev/null
crw-rw-rw- 1 root root 1, 3 2007-03-25 16:24 /dev/null

you can delete it and recreate it with the command 'mknod /dev/null c 1
3'

J.
--
In an ideal world I would cure poverty and go to the gym at least three
days a week.
[Agree]   [Disagree]
                 <http://www.slowlydownward.com/NODATA/data_enter2.html>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGC6aI+AfZydWK2zkRAuOtAJ4sbCjdldNBh41i9NWSmsqU/TBDRgCgjk01
CSjpzP9oFCyHvLHtPFvQFNE=
=quJV
-----END PGP SIGNATURE-----



Reply to: