[Bug 926835] sshd.service (openssh) fails on boot when primary listener is a bridge (br0) instead of real interface (eth0).
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=926835
lynda t
this fails
systemctl enable sshd@.service Failed to execute operation: No such file or directory
and so does this
systemctl enable sshd@service
I'm not completely familiar with this multi-instance usage. What needs to be fixed here?
The problem's that I created sshd@service instead of sshd@.service That's from the reading the attachment label of https://bugzilla.suse.com/show_bug.cgi?id=926835#c11 Thomas Blume 2015-04-14 13:49:37 UTC Created attachment 631010 [details] sshd@service <------------- https://bugzilla.suse.com/attachment.cgi?id=631010&action=edit sshd@service (edit details) <---------------- sshd@.service (text/plain), 255 bytes, created by Thomas Blume on 2015-04-14 13:49 UTC Fixing by switching service name to "sshd@.service" enable of that ^^ service works now, systemctl stop sshd.service systemctl disable sshd.service systemctl enable sshdgenkeys.service systemctl enable sshd@.service systemctl enable sshd.socket systemctl start sshd.socket systemctl start sshd.service are all OK. Now after reboot sshd appears to be up and accessible without any other actions. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com