For me, the root cause of this was systemd's inability to create
temporary files. I would get a ton of messages similar to "Unsafe
symlinks encountered in /var/run/sshd, refusing." in the systemd log,
By changing my system root directory (i.e. /) to be owned by root, it
fixed all these problems, i
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/1579978
Title:
up
On Thu, May 12, 2016 at 06:21:36AM -, Daniel wrote:
> solved my problem by using sshd -t and get an error in my config file,
> which was running fine with previous version of openssh-server. It
> seems, that there is no more option to for roaming?
I believe upstream removed the roaming support
I had the same problem at my machine. I tried to remove and then
reinstall openssh-server, but the same error occurred. I know, that just
remove openssh-server takes all my conf files on the system. I finally
solved my problem by using sshd -t and get an error in my config file,
which was running f
Hi Robie,
I tried purging and reinstalling openssh-server, but that failed again
with the same error.
I then rebooted the machine and was able to then successfully run apt-
get -f install to fix the package installation. Subsequently re-
installing the package worked without a problem.
Perhaps
I've not managed to reproduce this. I tried installing upstart-sysv on a
Wily cloud image and upgrading it to Xenial. This made the systemd
preinst fail (which may be a separate bug) but I didn't see any openssh
failure. I also tried installing upstart-sysv on a Vivid cloud image and
upgrading that
Hi Robie,
I had the same problem occur this morning on a couple of server installs
running systemd-sysv, so I'm thinking it might not be an upstart-
specific issue. I rebooted one of the servers and was then able to
upgrade the package successfully. I haven't yet rebooted the other
server. Both
I upgraded from Vivid => Wily => Xenial. I had switched back to
upstart-sysv on Vivid but I noticed that the upgrade software reinstalls
the ubuntu-standard package (and therefore systemd-sysv) on upgrade to a
new release, so I had re-installed upstart-sysv after each upgrade.
--
You received th
Hi Tomas,
Did you attempt to upgrade to Xenial directly from Vivid or did you go
through Wily? Was it on Vivid that you switched back to upstart-sysv?
I'm not sure this is a supported path (it's certainly an unusual one)
but I wonder if an upgrade from Trusty to Xenial is affected since that
will
I had no problems installing the upgraded packages after switching from
upstart-sysv to systemd-sysv on the affected machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579978
Title:
upgrade to
** Description changed:
This package upgrade failure has occurred on multiple machines, with the
same error on each machine. All affected machines are running Upstart
- as /sbin/init. The package installed/updated successfully on a machine
- running Systemd as /sbin/init.
-
- The affected m
11 matches
Mail list logo
