It seems like I can't add another Debian bug reference to this bug, but
I found this one to be a very interesting read:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982950
In a nutshell, although the "After=network-online.target" change can be
considered to be a workaround here, I find it
** Changed in: openssh (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, 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
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986761 another debian
report.
** Bug watch added: Debian Bug tracker #986761
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986761
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the
cjwatson (if you're still watching) or other openssh uploaders - would
you accept a patch to adjust ssh service files default behaviour to
network-online instead of network ready? If yes I'll prepare a debdiff
for review.
--
You received this bug notification because you are a member of Ubuntu
Also duplicate https://bugzilla.redhat.com/show_bug.cgi?id=1352214
** Bug watch added: Red Hat Bugzilla #1096081
https://bugzilla.redhat.com/show_bug.cgi?id=1096081
** Also affects: openssh (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1096081
Importance: Unknown
I researched this issue for about 6+ hours or so and finally came across
this thread. I have been able to solve the issue thanks to this thread.
# ENVIRONMENT INFO:
Ubuntu 20.04.2 LTS (Focal Fossa)
OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020
# PROBLEM:
Open
Le 27/02/2021 à 08:39, Andy Igoshin a écrit :
> /etc/systemd/system/ssh.service.d/override.conf
>
> [Unit]
> After=network-online.target auditd.service
>
It has worked very well for me.
Thanks.
Regards
Jean-Marie
--
You received this bug notification because you are a member of Ubuntu
Bugs,
/etc/systemd/system/ssh.service.d/override.conf
[Unit]
After=network-online.target auditd.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will not start at boot if
** Tags added: network-online-ordering
--
You received this bug notification because you are a member of Ubuntu
Bugs, 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
Came across this issue on a system I'm rebuilding and spun up a VM
running 18.04.3 to test. It seems like I got it working consistently on
every reboot. I'll try and breakdown what I've tried and what worked.
Everyone & Dev's can let me know if they see any issues of setting it up
the way it's
@ahasenack, I found this post (took plenty of Google foo) but it was
helpful.
For anyone else, 18.04 LTS STILL has this issue. The following fixed
it:
After=network-online.target
Wants=network-online.target
These are in my [Unit] section at the top of
/etc/systemd/system/sshd.service
[Unit]
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
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
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd
Sorry, it should have read "After=network-online.target".
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#cutthecraphowdoimakesurethatmyservicestartsafterthenetworkisreallyonline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Rodman, as a workaround, maybe you could try to add an "After=systemd-
networkd-wait-online.service" clause in a drop-in snippet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
This is still broken in 18.04 Server. Setting the listen address fails
to load the SSHD daemon at boot time. You have to have console access
and do a "service sshd restart" to fix.
How is this bug still here???
--
You received this bug notification because you are a member of Ubuntu
Bugs,
10 years ago ... Same bug !
Incredible :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, 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
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:
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:
Thanks for the confirmation Gennady.
Now that there is a suggested and confirmed solution, would anybody that
personally requires (alway better to make an argument) this fix mind filing
this in Debian as well to be changed in ./debian/systemd/ssh.service.
I'd think at least eventually we want
Ubuntu 17.10
Changing network.target to network-online.target in
/lib/systemd/system/ssh.service worked. I also added
Wants=network-online.target (don't know if it's necessary but
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ suggests it)
--
You received this bug
** Attachment removed: "CF03A0B90095673B.jpg"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847/+attachment/4925374/+files/CF03A0B90095673B.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
As Seth mentioned in comment #13 likely network-online.target should be the
solution.
@Owlbsidian - could you test and confirm with that as a fix as well?
A related fun quote from the systemd page about it:
"... please just fix your program to be friendly to dynamically changing
network
For me after changing network.target to network.service on
/usr/lib/systemd/system/sshd.service it started at the right time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
This has been broken for almost 10 years, still broken in 16.10
It is useful to set sshd ListenAddress so ssh won't be available when
connected to a different network (laptop on a public wifi etc). However
with ListenAddress set, sshd always fails a rebooot/network disconnect.
--
You received
This is still broken in 16.04 / Xenial.
I'm going to try using a root cronjob to catch and recover:
*/5 * * * * if [ $(ps -ef | grep /usr/sbin/sshd | grep -v grep
| wc -l) -eq 0 ]; then /usr/sbin/service ssh start; fi
--
You received this bug notification because you are a member of
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
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
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
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
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.
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
Bugs, which is subscribed to the bug report.
** 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
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, 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 up
To
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
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
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
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will not start
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
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
Bugs, which is subscribed
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
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.
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.
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
** 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
** 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
Bugs, which is subscribed to the bug
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
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
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd will not
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
Three years and six releases later, this is still present :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, 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
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
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
** 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
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
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
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
** 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
** 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
58 matches
Mail list logo
