> Robie: If the service offers a mechanism to set a specific NIC to
listen on, then the service should make good on that offer when it's
requested. Doesn't that make sense to you?
Correct. If you configure the service to listen on a specific NIC, you
should also configure the service to wait for
For anyone that's interested ---
I added the following to root's crontab:
@reboot sleep 120 && /bin/systemctl restart sshd
That works for me to get sshd up AND listening
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
SSH to finally learn how to pick up addresses later is a long time demand for
ssh to do that.
But it is a demand for an upstream feature IMHO.
I know it can thse day's re-pickup adresses that it lost:
- I have a KVM guest with one interface and I have set up ssh listen to only
interface
Robie: If the service offers a mechanism to set a specific NIC to listen
on, then the service should make good on that offer when it's requested.
Doesn't that make sense to you?
All services that require a NIC to function should wait for that NIC to
come alive. Having a service start or attempt
> Both services fail when an attempt is made to specify a particular NIC
via their respective config files.
If this is the case, then I don't think this can be treated as a bug in
Ubuntu. Currently, if you change one end of the configuration that
requires one thing, you need to change the other
I created Bug 1774788 which is for rsyncd not starting at boot and was
provided with a fix by Andreas Hasenack that works. I tried using that
fix for ssh and it does not work.
Both services fail when an attempt is made to specify a particular NIC
via their respective config files. In the case of
I installed version 16LTS recently and just upgraded the box to 18LTS
and both display the error.
I have 2 NICs (Private / Public) with an sshd config file set to only
listen to the private side. It appears sshd attempt to start after the
Public NIC is up, but before the private NIC is available.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549473
Title:
** Changed in: openssh (Debian)
Assignee: (unassigned) => Andrew T. Aldridge (dubleeh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549473
Title:
ssh will not start at boot: systemctl
** Also affects: openssh (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549473
Title:
ssh will not start at boot: systemctl status ssh ->
** Also affects: openssh
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549473
Title:
ssh will not start at boot: systemctl status ssh -> output is
Tarifa on #ubuntu-server reported problems with his ssh service. The
steps he found that he needed to make sshd start reliably:
systemctl disable ssh
update-rc.d ssh disable
systemctl enable ssh
"Then add both Wants=network-online.target & Requires=network-
online.target in an ssh service
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sure thing:
$ sudo systemctl status ssh
[sudo] password for andrewta:
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: failed (Result: start-limit) since Wed 2016-02-24 14:44:04 CST; 20s
ago
Process:
After boot starting ssh has never fails to start and correctly runs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1549473
Title:
ssh will not start at boot: systemctl status ssh
After boot starting ssh has never fails to start and correctly runs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549473
Title:
ssh will not start at boot: systemctl status ssh -> output is
Sure thing:
$ sudo systemctl status ssh
[sudo] password for andrewta:
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: failed (Result: start-limit) since Wed 2016-02-24 14:44:04 CST; 20s
ago
Process:
Please can you provide as much information as you have? For example,
"the ctl status is failed 255" is clearly a paraphrase of something that
you're seeing; it would be more useful if you could please copy and
paste the original text of the error messages.
Forum research is probably leading you
Please can you provide as much information as you have? For example,
"the ctl status is failed 255" is clearly a paraphrase of something that
you're seeing; it would be more useful if you could please copy and
paste the original text of the error messages.
Forum research is probably leading you
19 matches
Mail list logo