start: Unknown job: ssh

[yawnmoth]

initctl list | grep ssh returns nothing.

ldd /usr/sbin/sshd:

	linux-vdso.so.1 =>  (0x00007ffff65ff000)
	libwrap.so.0 => /lib/x86_64-linux-gnu/libwrap.so.0 (0x00007f6cd9d58000)
	libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007f6cd9b4a000)
	libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f6cd992b000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6cd970e000)
	libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f6cd935f000)
	libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f6cd915b000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6cd8f43000)
	libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f6cd8d0a000)
	libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f6cd8acb000)
	libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f6cd8802000)
	libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f6cd85fe000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6cd825e000)
	libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x00007f6cd8044000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6cd7e40000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f6cda1f7000)
	libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f6cd7c17000)
	libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f6cd7a0f000)
	libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f6cd780c000)
	libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f6cd75f0000)

[matt_symes]

Hi

initctl list | grep ssh returns nothing.

Well everything looks fine apart from this. Upstart knows nothing about your ssh service.

The only thing i can think of at the moment is that upstart is not picking up the configuration file ssh.conf in /etc/init. It is meant to do this automatically using inotify.

From man initctl.

reload-configuration

              Requests that the init(8) daemon reloads its configuration.

              This  command  is generally not necessary since init(8) watches its configuration directories with inotify(7) and auto‐
              matically reloads in cases of changes.

              No jobs will be started by this command.

Let's try to reload manually. From a terminal

sudo initctl reload-configuration

and then

sudo service ssh start

Kind regards

[supercheetah]

This is likely a bug because I just tried installing and running sshd on my computer as well, and I ran into the same issue, and after running initctl reload-configuration, I'm still getting start: unrecognized service.

A bug report should probably be filed. I tried finding a relevant bug report on Launchpad, but I couldn't find anything in my initial search. I am going to keep on looking, though.

Ignore this, I just realized I was using service incorrectly (I had service start ssh instead of service ssh start), sorry.

[matt_symes]

Hi

@supercheetah. Did reloading the configuration work for you ?

This is likely a bug because I just tried installing and running sshd on my computer as well, and I ran into the same issue, and after running initctl reload-configuration, I'm still getting start: unrecognized service.

A bug report should probably be filed. I tried finding a relevant bug report on Launchpad, but I couldn't find anything in my initial search. I am going to keep on looking, though.

Ignore this, I just realized I was using service incorrectly (I had service start ssh instead of service ssh start), sorry.

Kind regards

[supercheetah]

Hi

@supercheetah. Did reloading the configuration work for you ?



Kind regards

It was kind of pointless for me since there were no issues.

One thing that I thought about though is I wonder if there was a problem with the package that was downloaded, and so thus openssh-server may have been installed incorrectly. Try this:

apt-get --purge remove openssh-server
apt-get clean
apt-get install openssh-server

It's perhaps a long shot, but...

[grndamgt4]

Hi

@supercheetah. Did reloading the configuration work for you ?



Kind regards

Hello, I had the same problem and did everything in this thread. After reloading the configuration as you suggested the ssh service started and is working. Thank you for the help.
I'm running a 11.10 live cd off USB with a casper-rw. Thanks again.

[sfinktah]

[edited] thought i had the solution, but i was wrong. (12.04)

[aname4]

I just had this problem. The problem was that the value in

hostname

was not in

/etc/hosts

with 127.0.0.1 assigned.