[Touch-packages] [Bug 1814124] Re: sshd does not start after update on non-Ubuntu kernels where fchownat() is broken

2019-04-08 Thread Christian Ehrhardt 
*** This bug is a duplicate of bug 1811580 *** https://bugs.launchpad.net/bugs/1811580 Same discussion and more in bug 1811580 marking as dup to have people finding this bug all get to the same main bug. ** This bug has been marked a duplicate of bug 1811580 systemd fails to start sshd at

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-26 Thread Robie Basak
> The entry in /usr/lib/tmpfiles.d/sshd.conf SHOULD be... I don't agree, even if this happens to work for you. It's valid for it to be /var/run/sshd provided that your system is properly up-to-date (see related bug 1804847). If you're using some environment that is broken, please ask the people

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-22 Thread Peter Passchier
The entry in /usr/lib/tmpfiles.d/sshd.conf SHOULD be: d /run/sshd 0755 root root When it isn't, sshd cannot be started up after a reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu.

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-04 Thread Wojciech Sulewski
I can not choose OpenVZ version or kernel. I can only pass some information to my VPS providers and I see all of them using version 6. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu.

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-04 Thread Seth Arnold
Hello Wojciech, please make sure you're on a new enough version of OpenVZ's kernel, see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847 comment #20 for more information. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-04 Thread Wojciech Sulewski
I run several OpenVZ VPS servers from 4 different providers and last month I lost ssh access to all of them after doing an update. I have never had such problem before and I update regularly. I don't have access to KVM to check it. 1 lrwxrwxrwx 1 root root 4 Feb 3 15:16 /var/run -> /run 2

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-03 Thread Christian Ehrhardt 
I took a fresh Xenial (daily) as well as a Xenial of the release day and ran the commands: $ apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && apt-get upgrade && apt-get dist-upgrade && reboot Obviously the updated different amounts of packages, but none did break

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-03 Thread Wojciech Sulewski
BTW the "fix" I got from here: https://askubuntu.com/questions/739164/ssh-connection-refused seems like an old problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu.

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-03 Thread Wojciech Sulewski
I did some additional tests and reinstalling openssh-server does not break it. It only breaks after the update procedure. To recreate the error, take a fresh OpenVZ 6 Templates of Ubuntu 16.04 64bit, and simply do: apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update &&

[Touch-packages] [Bug 1814124] Re: sshd does not start after update

2019-02-01 Thread Christian Ehrhardt 
Hi, I took a fresh system and it had openssh-server installed right away (as it is part of all the base images). /var/run/sshd was at 0755 root:root already I was wondering if the package install would kill the permission/ownership, so I did $ apt install --reinstall openssh-server But things