Hello, ssh won't start

chaddelange · 2012-10-24 04:52:34

Hello,

I installed ssh with pacman -S openssh

Below are the errors I'm gettting, if there is any files you want to see please let me know.

I installed arch a few days ago, been using ubuntu and linuxmint for a while.

When I run

sudo /etc/rc.d/sshd start

I get

/etc/rc.d/sshd: line 4: /etc/rc.d/functions: No such file or directory
/etc/rc.d/sshd: line 16: stat_busy: command not found
Disabling protocol version 2. Could not load host key
sshd: no hostkeys available -- exiting.
/etc/rc.d/sshd: line 20: stat_fail: command not found

When I run

sudo /etc/rc.d/sshd -k start

I get

/etc/rc.d/sshd: line 4: /etc/rc.d/functions: No such file or directory
usage: /etc/rc.d/sshd {start|stop|restart}

Last edited by chaddelange (2012-10-24 04:53:40)

WonderWoofy · 2012-10-24 05:35:09

If you installed a few days ago I would tink you are using systemd.

What does

$ cat /proc/1/comm

return to you?

If it says systemd, you need to use the systemd syntax to start services. If this is the case, please refer to the systemd wiki page.

chaddelange · 2012-10-24 09:15:57

Thanx, it returned systemd

systemd is busy downloading, got another question though, I browsed through this whole page

Another question? how do I Add init=/usr/lib/systemd/systemd to the kernel parameters in your bootloader.

Thanx, googled it, but didn't find anything

skunktrader · 2012-10-24 09:47:48

systemctl start sshd

chaddelange · 2012-10-24 09:53:31

skunktrader wrote:

systemctl start sshd

Thanx, that seemed to have worked, how do I check to make sure it worked though

ssh localhost

And

ssh chad@localhost

Gave

ssh: connect to host localhost port 22: Connection refused

Not too sure how to use ssh, but once I know it working

WorMzy · 2012-10-24 09:56:26

chaddelange wrote:

how do I Add init=/usr/lib/systemd/systemd to the kernel parameters in your bootloader.
Thanx, googled it, but didn't find anything

You don't need to do that. That's there for people who are still using initscripts, but want to try systemd. For future reference, this wiki page explains how to pass additional arguments to your kernel in grub2 (which you are probably using).

It's "thanks", not "thanx", by the way. I know it's not relevant to your problem, but I thought I'd point it out in case English isn't your first language.

chaddelange wrote:

how do I check to make sure it worked though

Use systemctl status, as instructed on the systemd wiki page.

Last edited by WorMzy (2012-10-24 10:00:07)

chaddelange · 2012-10-24 10:07:23

O ok nice!

I know know its thanks, but I've almost always used thanx, Thanks for letting me know.

 sudo systemctl status sshd

returns

sshd.service - OpenSSH Daemon
	  Loaded: loaded (/usr/lib/systemd/system/sshd.service; disabled)
	  Active: failed (Result: start-limit) since Wed, 24 Oct 2012 11:50:57 +0000; 15min ago
	 Process: 8138 ExecStart=/usr/sbin/sshd -D (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/sshd.service

Oct 24 11:50:57 chad-arch systemd[1]: Stopping OpenSSH Daemon...
Oct 24 11:50:57 chad-arch systemd[1]: Starting OpenSSH Daemon...
Oct 24 11:50:57 chad-arch systemd[1]: Failed to start OpenSSH Daemon.

WorMzy · 2012-10-24 10:20:20

So it's failed. At a guess, this is because you haven't addressed this error from your first post:

Disabling protocol version 2. Could not load host key
sshd: no hostkeys available -- exiting.

What is the status of sshdgenkeys.service?

chaddelange · 2012-10-24 10:29:24

sudo systemctl status sshdgenkeys.service

Returns

sshdgenkeys.service - SSH Key Generation
	  Loaded: loaded (/usr/lib/systemd/system/sshdgenkeys.service; disabled)
	  Active: inactive (dead)
	          start condition failed at Wed, 24 Oct 2012 11:50:57 +0000; 36min ago
	  CGroup: name=systemd:/system/sshdgenkeys.service

Oct 24 11:50:56 chad-arch systemd[1]: Started SSH Key Generation.
Oct 24 11:50:56 chad-arch systemd[1]: Started SSH Key Generation.
Oct 24 11:50:56 chad-arch systemd[1]: Started SSH Key Generation.
Oct 24 11:50:56 chad-arch systemd[1]: Started SSH Key Generation.
Oct 24 11:50:57 chad-arch systemd[1]: Started SSH Key Generation.
Oct 24 11:50:57 chad-arch systemd[1]: Started SSH Key Generation.
Oct 24 11:50:57 chad-arch systemd[1]: Started SSH Key Generation.

Guesing I was supposed to use that command

Last edited by chaddelange (2012-10-24 10:30:25)

WorMzy · 2012-10-24 11:48:57

Not as such; systemd should try to start it before it starts sshd.service, but it will only run if the start conditions are correct:

ConditionPathExists=|!/etc/ssh/ssh_host_key
ConditionPathExists=|!/etc/ssh/ssh_host_key.pub
ConditionPathExists=|!/etc/ssh/ssh_host_ecdsa_key
ConditionPathExists=|!/etc/ssh/ssh_host_ecdsa_key.pub
ConditionPathExists=|!/etc/ssh/ssh_host_dsa_key
ConditionPathExists=|!/etc/ssh/ssh_host_dsa_key.pub
ConditionPathExists=|!/etc/ssh/ssh_host_rsa_key
ConditionPathExists=|!/etc/ssh/ssh_host_rsa_key.pub

So if these files exist, then the service (sshdgenkeys) will not need to run. But if these files exist, then sshd shouldn't be failing due to missing keys.

Can you post the output of:

ls -l /etc/ssh

chaddelange · 2012-10-24 13:42:27

Okay, here is the out put of

ls -l /etc/ssh

total 280
-rw-r--r-- 1 root root 245058 Sep  3 12:59 moduli
-rw-r--r-- 1 root root   1555 Sep  3 12:59 ssh_config
-rw-r--r-- 1 root root   3443 Oct 23 22:14 sshd_config
-rw------- 1 root root    668 Oct 24 06:45 ssh_host_dsa_key
-rw-r--r-- 1 root root    604 Oct 24 06:45 ssh_host_dsa_key.pub
-rw------- 1 root root    227 Oct 24 06:45 ssh_host_ecdsa_key
-rw-r--r-- 1 root root    176 Oct 24 06:45 ssh_host_ecdsa_key.pub
-rw------- 1 root root    979 Oct 24 06:45 ssh_host_key
-rw-r--r-- 1 root root    644 Oct 24 06:45 ssh_host_key.pub
-rw------- 1 root root   1675 Oct 24 06:45 ssh_host_rsa_key
-rw-r--r-- 1 root root    396 Oct 24 06:45 ssh_host_rsa_key.pub

WorMzy · 2012-10-24 19:06:23

Hmm, you have the necessary files so I guess that's not a problem any more. That means that you have a different problem with sshd.

Check your journal (sudo journalctl) for errors regarding sshd.service, and see if you can run the daemon manually.

chaddelange · 2012-10-25 08:14:13

[chad@chad-arch ~]$ sudo journalctl

Returns

Logs begin at Mon, 22 Oct 2012 13:09:12 +0000, end at Thu, 25 Oct 2012 10:12:46 +0000.
Oct 22 13:09:12 chad-arch systemd-journal[115]: Allowing runtime journal files t
Oct 22 13:09:12 chad-arch kernel: Initializing cgroup subsys cpuset
Oct 22 13:09:12 chad-arch kernel: Initializing cgroup subsys cpu
Oct 22 13:09:12 chad-arch kernel: Linux version 3.6.2-1-ARCH (tobias@testing) (g
Oct 22 13:09:12 chad-arch kernel: e820: BIOS-provided physical RAM map:
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x000000000009dc00-0x000000000
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x00000000000ce000-0x000000000
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x00000000000e0000-0x000000000
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x000000003f6b0000-0x000000003
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x000000003f6c8000-0x000000003
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x000000003f6cb000-0x000000003
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000e
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000f
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000f
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000f
Oct 22 13:09:12 chad-arch kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000f
Oct 22 13:09:12 chad-arch kernel: Notice: NX (Execute Disable) protection cannot
Oct 22 13:09:12 chad-arch kernel: DMI present.
Oct 22 13:09:12 chad-arch kernel: DMI: LENOVO 8811ZUN/LENOVO, BIOS 2JKT40AUS 12/
Oct 22 13:09:12 chad-arch kernel: e820: update [mem 0x00000000-0x0000ffff] usabl
Oct 22 13:09:12 chad-arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usabl
:

How do I run the daemon manually?

WorMzy · 2012-10-25 09:35:08

That's just the top of the journal, search through it (e.g. using /) for messages about sshd, or pipe journalctl into grep.

The command to start the daemon is listed as "ExecStart" in the service file.

chaddelange · 2012-10-25 10:06:03

[chad@chad-arch ~]$ sudo journalctl | grep sshd

Returned

Oct 24 11:50:56 chad-arch sshd[8127]: Disabling protocol version 2. Could n...ey
Oct 24 11:50:56 chad-arch sshd[8127]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service: main process exited, co...=1
Oct 24 11:50:56 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service holdoff time over, sched...t.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service: main process exited, co...=1
Oct 24 11:50:56 chad-arch sshd[8130]: Disabling protocol version 2. Could n...ey
Oct 24 11:50:56 chad-arch sshd[8130]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:56 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service holdoff time over, sched...t.
Oct 24 11:50:56 chad-arch sshd[8132]: Disabling protocol version 2. Could n...ey
Oct 24 11:50:56 chad-arch sshd[8132]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service: main process exited, co...=1
Oct 24 11:50:56 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service holdoff time over, sched...t.
Oct 24 11:50:57 chad-arch sshd[8134]: Disabling protocol version 2. Could n...ey
Oct 24 11:50:57 chad-arch sshd[8134]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service: main process exited, co...=1
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service holdoff time over, sched...t.
Oct 24 11:50:57 chad-arch sshd[8136]: Disabling protocol version 2. Could n...ey
Oct 24 11:50:57 chad-arch sshd[8136]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service: main process exited, co...=1
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service holdoff time over, sched...t.
Oct 24 11:50:57 chad-arch sshd[8138]: Disabling protocol version 2. Could n...ey
Oct 24 11:50:57 chad-arch sshd[8138]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service: main process exited, co...=1
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service holdoff time over, sched...t.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service start request repeated t...t.
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.

Sorry, I don't understand this part

is listed as "ExecStart" in the service file.

I'm kinda a newbie at this

Last edited by chaddelange (2012-10-25 10:06:24)

WorMzy · 2012-10-25 10:37:58

Service files, like /usr/lib/systemd/system/sshd.service, are simple configuration files, and contain information hat systemd needs to know to start/stop/enable/etc. a specific service. The "ExecStart" line(s) are usually what systemd uses to start the service (though it can be more complicated than that in some services).

It looks like that journal output is from the first time you ran sshd, before the hostkeys existed.

Try restarting the service. Then post the output of

sudo journalctl -a | grep sshd

That -a will stop the journal "squashing" messages down to fit in the terminal width.

chaddelange · 2012-10-26 04:23:04

O ok, sorry, was by computer really yesturday

did sudo systemctl restart sshd

[sudo journalctl -a | grep sshd

Returns

Oct 23 21:57:23 chad-arch sudo[6684]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:00:45 chad-arch sudo[6709]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:03:47 chad-arch sudo[6744]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:03:48 chad-arch sudo[6746]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:07:14 chad-arch sudo[6770]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:07:42 chad-arch sudo[6772]: chad : TTY=pts/1 ; PWD=/home ; USER=root ; COMMAND=/usr/bin/nano /etc/ssh/sshd_config
Oct 23 22:10:19 chad-arch sudo[6788]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:10:26 chad-arch sudo[6790]: chad : TTY=pts/1 ; PWD=/home ; USER=root ; COMMAND=/usr/bin/nano /etc/ssh/sshd_config
Oct 23 22:14:05 chad-arch sudo[6794]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:14:06 chad-arch sudo[6796]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:16:37 chad-arch sudo[6814]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:16:58 chad-arch sudo[6818]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:30:30 chad-arch sudo[6916]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:30:33 chad-arch sudo[6918]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:30:33 chad-arch sudo[6920]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:30:34 chad-arch sudo[6922]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 23 22:33:48 chad-arch sudo[6955]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 24 06:42:18 chad-arch sudo[7567]: chad : TTY=pts/2 ; PWD=/etc/rc.d ; USER=root ; COMMAND=/usr/sbin/sshd -k start
Oct 24 06:44:52 chad-arch sudo[7571]: chad : TTY=pts/2 ; PWD=/home/chad ; USER=root ; COMMAND=/etc/rc.d/sshd -k start
Oct 24 06:45:31 chad-arch sudo[7580]: chad : TTY=pts/2 ; PWD=/home/chad ; USER=root ; COMMAND=/etc/rc.d/sshd -k start
Oct 24 06:45:39 chad-arch sudo[7587]: chad : TTY=pts/2 ; PWD=/home/chad ; USER=root ; COMMAND=/etc/rc.d/sshd start
Oct 24 06:47:13 chad-arch sudo[7600]: chad : TTY=pts/2 ; PWD=/home/chad ; USER=root ; COMMAND=/etc/rc.d/sshd start
Oct 24 06:48:08 chad-arch sudo[7613]: chad : TTY=pts/2 ; PWD=/home/chad ; USER=root ; COMMAND=/etc/rc.d/sshd start
Oct 24 06:49:19 chad-arch sudo[7624]: chad : TTY=pts/2 ; PWD=/home/chad ; USER=root ; COMMAND=/etc/rc.d/sshd -k start
Oct 24 06:50:22 chad-arch sudo[7638]: chad : TTY=pts/2 ; PWD=/home/chad ; USER=root ; COMMAND=/etc/rc.d/sshd -k start
Oct 24 11:50:44 chad-arch dbus-daemon[227]: dbus[227]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.87" (uid=1000 pid=8122 comm="systemctl start sshd ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Oct 24 11:50:44 chad-arch dbus[227]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.87" (uid=1000 pid=8122 comm="systemctl start sshd ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
Oct 24 11:50:55 chad-arch sudo[8124]: chad : TTY=pts/1 ; PWD=/home ; USER=root ; COMMAND=/usr/bin/systemctl start sshd
Oct 24 11:50:56 chad-arch sshd[8127]: Disabling protocol version 2. Could not load host key
Oct 24 11:50:56 chad-arch sshd[8127]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 24 11:50:56 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 24 11:50:56 chad-arch sshd[8130]: Disabling protocol version 2. Could not load host key
Oct 24 11:50:56 chad-arch sshd[8130]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:56 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 24 11:50:56 chad-arch sshd[8132]: Disabling protocol version 2. Could not load host key
Oct 24 11:50:56 chad-arch sshd[8132]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 24 11:50:56 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:56 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 24 11:50:57 chad-arch sshd[8134]: Disabling protocol version 2. Could not load host key
Oct 24 11:50:57 chad-arch sshd[8134]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 24 11:50:57 chad-arch sshd[8136]: Disabling protocol version 2. Could not load host key
Oct 24 11:50:57 chad-arch sshd[8136]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 24 11:50:57 chad-arch sshd[8138]: Disabling protocol version 2. Could not load host key
Oct 24 11:50:57 chad-arch sshd[8138]: sshd: no hostkeys available -- exiting.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 24 11:50:57 chad-arch systemd[1]: sshd.service start request repeated too quickly, refusing to start.
Oct 24 11:50:57 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 24 12:06:11 chad-arch sudo[8158]: chad : TTY=pts/1 ; PWD=/home ; USER=root ; COMMAND=/usr/bin/systemctl status sshd
Oct 24 12:27:15 chad-arch sudo[8252]: chad : TTY=pts/1 ; PWD=/home ; USER=root ; COMMAND=/usr/bin/systemctl status sshdgenkeys.service
Oct 25 10:12:40 chad-arch sudo[9293]: chad : TTY=pts/0 ; PWD=/home/chad ; USER=root ; COMMAND=/usr/bin/journalctl sshd.service
Oct 25 10:12:46 chad-arch sudo[9295]: chad : TTY=pts/0 ; PWD=/home/chad ; USER=root ; COMMAND=/usr/bin/journalctl sshd
Oct 26 06:19:16 chad-arch sudo[10291]: chad : TTY=pts/0 ; PWD=/home/chad ; USER=root ; COMMAND=/usr/bin/systemctl start sshd
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:17 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:17 chad-arch sshd[10294]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:17 chad-arch sshd[10294]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:17 chad-arch sshd[10296]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:17 chad-arch sshd[10296]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:17 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:17 chad-arch sshd[10299]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:17 chad-arch sshd[10299]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:17 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:17 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:17 chad-arch sshd[10301]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:17 chad-arch sshd[10301]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:17 chad-arch sshd[10303]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:17 chad-arch sshd[10303]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:17 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:17 chad-arch sshd[10305]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:17 chad-arch sshd[10305]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:17 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:17 chad-arch systemd[1]: sshd.service start request repeated too quickly, refusing to start.
Oct 26 06:19:17 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:28 chad-arch sudo[10307]: chad : TTY=pts/0 ; PWD=/home/chad ; USER=root ; COMMAND=/usr/bin/systemctl restart sshd
Oct 26 06:19:28 chad-arch sshd[10310]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:28 chad-arch sshd[10310]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:28 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:28 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:28 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:28 chad-arch sshd[10312]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:28 chad-arch sshd[10312]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:28 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:28 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:28 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:28 chad-arch sshd[10314]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:28 chad-arch sshd[10314]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:28 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:28 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:28 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:28 chad-arch sshd[10316]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:28 chad-arch sshd[10316]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:28 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:28 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:29 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:29 chad-arch sshd[10318]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:29 chad-arch sshd[10318]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:29 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:29 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:29 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:29 chad-arch sshd[10320]: Disabling protocol version 2. Could not load host key
Oct 26 06:19:29 chad-arch sshd[10320]: sshd: no hostkeys available -- exiting.
Oct 26 06:19:29 chad-arch systemd[1]: sshd.service: main process exited, code=exited, status=1
Oct 26 06:19:29 chad-arch systemd[1]: Unit sshd.service entered failed state.
Oct 26 06:19:29 chad-arch systemd[1]: sshd.service holdoff time over, scheduling restart.
Oct 26 06:19:29 chad-arch systemd[1]: sshd.service start request repeated too quickly, refusing to start.
Oct 26 06:19:29 chad-arch systemd[1]: Unit sshd.service entered failed state.

chaddelange · 2012-10-26 04:24:59

Here is the /usr/lib/systemd/system/sshd.service file

[Unit]
Description=OpenSSH Daemon
Wants=sshdgenkeys.service
After=sshdgenkeys.service

[Service]
ExecStart=/usr/sbin/sshd -D
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process
Restart=always

[Install]
WantedBy=multi-user.target
Also=sshdgenkeys.service

# This service file runs an SSH daemon that forks for each incoming connection.
# If you prefer to spawn on-demand daemons, use sshd.socket and sshd@.service.

chaddelange · 2012-10-31 10:22:30

Hello. Sorry to post again. Just want to know where can I go to get further help, or to try fix this? I don't think this problem is because of ssh, because I can't start mysql either.

Though I think mysql starts when I start in some safe way in /usr/bin

Thanx

WorMzy · 2012-10-31 11:18:46

I don't understand what's going wrong there. Could you post your /etc/ssh/sshd_config?

What journal messages do you get regarding mysql?

litemotiv · 2012-10-31 11:33:14

Probably relevant: https://bbs.archlinux.org/viewtopic.php?id=144449

(got there by googling "sshd: no hostkeys available -- exiting.")

Arch Linux

#1 2012-10-24 04:52:34

Hello, ssh won't start

#2 2012-10-24 05:35:09

Re: Hello, ssh won't start

#3 2012-10-24 09:15:57

Re: Hello, ssh won't start

#4 2012-10-24 09:47:48

Re: Hello, ssh won't start

#5 2012-10-24 09:53:31

Re: Hello, ssh won't start

#6 2012-10-24 09:56:26

Re: Hello, ssh won't start

#7 2012-10-24 10:07:23

Re: Hello, ssh won't start

#8 2012-10-24 10:20:20

Re: Hello, ssh won't start

#9 2012-10-24 10:29:24

Re: Hello, ssh won't start

#10 2012-10-24 11:48:57

Re: Hello, ssh won't start

#11 2012-10-24 13:42:27

Re: Hello, ssh won't start

#12 2012-10-24 19:06:23

Re: Hello, ssh won't start

#13 2012-10-25 08:14:13

Re: Hello, ssh won't start

#14 2012-10-25 09:35:08

Re: Hello, ssh won't start

#15 2012-10-25 10:06:03

Re: Hello, ssh won't start

#16 2012-10-25 10:37:58

Re: Hello, ssh won't start

#17 2012-10-26 04:23:04

Re: Hello, ssh won't start

#18 2012-10-26 04:24:59

Re: Hello, ssh won't start

#19 2012-10-31 10:22:30

Re: Hello, ssh won't start

#20 2012-10-31 11:18:46

Re: Hello, ssh won't start

#21 2012-10-31 11:33:14

Re: Hello, ssh won't start

Board footer