Just passing by to see if anything has changed. Would be good to know if
the workaround is effective for those affected.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd wi
Upstream server about using IP_FREEBIND:
https://bugzilla.mindrot.org/show_bug.cgi?id=2512
** Bug watch added: OpenSSH Portable Bugzilla #2512
https://bugzilla.mindrot.org/show_bug.cgi?id=2512
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=2512
Importance: Unkn
Under systemd, if the ListenAddress is on an interface that is manually
brought up, the ifup script doesn't help. In that situation, the invoke-
rc.d reload/restart fails because the initial startup of sshd wasn't
successful.
--
You received this bug notification because you are a member of Ubunt
Since so many things changed since this - admittedly embarrassing old -
bug was reported I thought I retest it before the next LTS comes out.
I looked at the Xenial content and found stuff like:
Not only is it specified "After network.target", but on top there is
/etc/network/if-up.d/openssh-serv
Would be nice if it was fixed once for all. This is a critical bug when
your server is in a distant location, and you cannot log on it because
of that bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.lau
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will not start at boot if ListenAddress is set, because network
interface is not yet u
Changing the ssh service file to use network-online.target should also
work; see
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ for more
information.
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
Wouldn't it be possible to have sshd use "IP_FREEBIND" so that it can
bind an IP that has not materialized yet?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will n
same in vivid
Mai 11 12:40:44 pcds systemd[1]: Unit ssh.service entered failed state.
Mai 11 12:40:44 pcds systemd[1]: ssh.service failed.
Mai 11 12:40:44 pcds systemd[1]: ssh.service holdoff time over, scheduling ...t.
Mai 11 12:40:44 pcds systemd[1]: start request repeated too quickly for ssh...
same problem with package openssh-server of Ubuntu 13.10 (Saucy)
error messages in /var/log/auth.log after boot process:
Nov 1 17:31:46 pc sshd[1209]: error: Bind to port xxx on yyy.yyy.y.y failed:
Cannot assign requested address.
Nov 1 17:31:46 pc sshd[1209]: fatal: Cannot bind any address.
r
** Patch added: "ubuntu 12.10 patch /etc/init/ssh.conf without sleep"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847/+attachment/3889510/+files/ssh.conf_12.10.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the
I tested on 12.10.
Unfortunately the solution from Claus interferes with the network
manager. On my 12.10 system I wasn't able to handle the eth0 by the
network manager any more.
As I don't like arvitrary sleep times, I figured out a solution just
changing the start on line in /etc/init/ssh. It
I have fixed this problem for me in /etc/network/interfaces
auto eth0
iface eth0 inet dhcp
up service ssh start
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd wil
Three years and six releases later, this is still present :(
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will not start at boot if ListenAddress is set, because n
Adding random sleeps is usually not the best possible solution, as the
required delay varies between systems (for example, when using a network
bridge). Maybe depending on net-device-up would be better.
--
sshd will not start at boot if ListenAddress is set, because network interface
is not yet
** Tags added: patch
--
sshd will not start at boot if ListenAddress is set, because network interface
is not yet up
https://bugs.launchpad.net/bugs/216847
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
--
Ubuntu-server-bugs mai
I'm having this exact symptom but in a different environment: Ubuntu
10.04 Lucid Server.
After configuring /etc/ssh/sshd_config to have a specific ListenAddress
instead of 0.0.0.0, the ssh daemon consistently fails to start at boot
time.Errors from /var/log/auth.log:
Sep 23 14:26:45 a02-gsp
** Summary changed:
- sshd will not start at boot
+ sshd will not start at boot if ListenAddress is set, because network
interface is not yet up
** Visibility changed to: Public
--
sshd will not start at boot if ListenAddress is set, because network interface
is not yet up
https://bugs.launch
18 matches
Mail list logo