[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-07-12 Thread Robie Basak
> 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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-07-11 Thread Bill Gradwohl
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.

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-06-22 Thread  Christian Ehrhardt 
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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-06-21 Thread Bill Gradwohl
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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-06-21 Thread Robie Basak
> 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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-06-15 Thread Bill Gradwohl
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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-04-29 Thread Bill Gradwohl
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.

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2018-04-29 Thread Launchpad Bug Tracker
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:

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2017-08-09 Thread Chowdhury Masum
** 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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2017-08-09 Thread Chowdhury Masum
** 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 ->

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2017-08-09 Thread Chowdhury Masum
** 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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-06-29 Thread Seth Arnold
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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-04-27 Thread Launchpad Bug Tracker
[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.

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-02-27 Thread Andrew Aldridge
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:

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-02-27 Thread Andrew Aldridge
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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-02-27 Thread Andrew Aldridge
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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-02-27 Thread Andrew Aldridge
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:

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-02-25 Thread Colin Watson
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

[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

2016-02-25 Thread Colin Watson
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