I think I had the same problem. I think it was fixed with "chown
root:root /var".
Related to this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394
I think it also caused screen to be unusable until it was run by root.
--
You received this bug notification because you are a
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thank you @vorlon . I made some test with that image on a clean server
and it works with no issues, but I had issues in different servers with
the same image and other worked fine with the same AMI.
I use a proxy repository, this can be related to different/incompatible
systemd and kernel
On Tue, 26 Feb 2019 at 18:05, Matt P <1811...@bugs.launchpad.net> wrote:
>
> Okay. I guess I would have expected that if there was a dependency on a
> specific kernel version, that I wouldn't be able to install a package
> that wasn't compatible and breaks the system by installing a security
>
On Tue, Apr 23, 2019 at 04:44:07PM -, Julian Alarcon wrote:
> There is something that I cant understand.
> I get that systemd new update changes some stuff and needs an specific
> path.
> But, why are the owners of / directory or others directories being
> changed?
> I got this issue with
There is something that I cant understand.
I get that systemd new update changes some stuff and needs an specific
path.
But, why are the owners of / directory or others directories being
changed?
I got this issue with this ami-059eeca93cf09eebd on AWS, but not in all
the servers that have this
Okay. I guess I would have expected that if there was a dependency on a
specific kernel version, that I wouldn't be able to install a package
that wasn't compatible and breaks the system by installing a security
update. It would be preferable to be informed there is a security
update but that I
On Tue, Feb 26, 2019 at 02:39:55PM -, Matt P wrote:
> Anyway, root cause seems to be this systemd-tmpfiles error. Tmpfile gets
> purged at reboot and doesn't get recreated.
> Seems pretty major that applying security updates would lock you out of
> your server. If I didn't happen to have a
Same situation. Ubuntu 16.04 openvz vps image of unknown origin.
Minimized image, ran security updates and rebooted. openssh server
failed to start due to systemd-tmpfiles failing with
Failed to validate path /var/run/sshd: Too many levels of symbolic
links
Which then causes ssh server to
Hi xnox
Thank your for your fast reply!
Indeed, i found the problem with a self-compiled package, which made a file in
/usr/lib/tmpfiles.d and ran the command "chown nrpe.nrpe /var".
After deleting the affected file out of /usr/lib/tmpfiles.d and made a manual
"chown root.root /var" everything
@cadirol
most likely your system is broken, insecure and vulnerable to the
relevant CVE. Please provide output from journal logs, and permissions
of the root directory
$ ls -latr /
$ journalctl -b
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Good day
Same issue here! After upgrade systemd from 229-4ubuntu21.10 to
229-4ubuntu21.15 and a reboot, ssh did not start anymore.
As ugly workaround i ran #mkdir -p -m0755 /var/run/sshd && systemctl restart
ssh.service
$ uname -a
Linux aws01.nts.ch 4.4.0-142-generic #168-Ubuntu SMP Wed Jan
@Dimitri John Ledkov (xnox)
I know that in my case the Kernel is quite old, however it still affects the
version I reported above and upgrading has some drawbacks in this case. What is
the reason causing the issue I described? Are there any options fixing it
without switching kernel version?
@ Spas Spasov (spaszspasov)
Your kernel is out of date. Please upgrade the kernel, or contact the
host administrators to apply at least
https://wiki.openvz.org/Download/kernel/rhel6/042stab134.7
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Description changed:
+ So
@ David (dasoto)
Please report bad permissions to whoever is distributing the "NVIDIA Jetson TX2
users" installation you are using. Maybe there are some upgrade hooks that
could be shipped by packages install in that installation to fix / mitigate
this issue.
--
You received this bug
I'm experiencing the same problem with Ubuntu 16.04.5 on OpenVZ (with
kernel: 2.6.32-042stab127.2).
The workaround that I found is to edit `/usr/lib/tmpfiles.d/sshd.conf`
in the following way:
d /run/sshd 0755 root root
Here is the question on askubuntu.com, where my case decribed in more
@Dimitri John Ledkov (xnox) I manully upgrade to
Linux pan 4.19.13-sunxi #5.70 SMP Sat Jan 12 15:43:21 CET 2019 armv7l armv7l
armv7l GNU/Linux
and the issue seems also to be fixed for me now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
@Dimitri John Ledkov (xnox) I think I'm forced by Armbian to this kernel
revision by default. TBH I don't know if a manual upgrade will break the
OS or not. I also have not investigated on how to upgrade it manually. I
have no permission issues like David (dasoto) I already checked that
before I
@Dimitri John Ledkov (xnox) It's Armbian (Xenial) for OrangePI One. Here
df -Th of my filesystem:
udev devtmpfs 165M 0 165M0% /dev
tmpfs tmpfs 50M3,9M 46M8% /run
/dev/mmcblk0p1 ext4 7,2G4,1G 3,1G 57% /
tmpfs tmpfs 248M 0
This solve the issue.
sudo chown root:root /
I think this will affect a lot of NVIDIA Jetson TX2 users, due the
Jetpack version that they include with ubuntu have the / folder with
owner ubuntu:ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@ David (dasoto)
nvidia@tegra-ubuntu:/$ ls -la
total 108
drwxrwxr-x 23 ubuntu ubuntu 4096 Oct 30 17:36 .
drwxrwxr-x 23 ubuntu ubuntu 4096 Oct 30 17:36 ..
drwxrwxr-x 22 ubuntu ubuntu 4096 Oct 29 20:31 lib
drwxr-xr-x 5 nvidia nvidia 4096 Oct 29 20:36 media
-rw-r--r-- 1 ubuntu ubuntu 62 May 17 2018
@Dimitri John Ledkov (xnox)
nvidia@tegra-ubuntu:~$ mount
/dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs
(rw,relatime,size=7976720k,nr_inodes=1994180,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc
@ Andreas Kar (thexmanxyz)
3.4.113-sun8i is an extremely ancient kernel. Why are you using such a kernel
and where does it come from?
Which filesystems are you using? is it btfs or something else?
@ David (dasoto)
Your system appears to have an up to date kernel... but also and odd one where
I have exactly the same problem. I check and an auto update was made for
systemd from 229-4ubuntu21.10 to 229-4ubuntu21.15 on many of my
devices (Jetson TX2). Now devices rebooted doesn't start ssh and I lost
complete communication with all those devices.
I were able to log in through serial
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This problem is not new and it appears again with the new systemd
"229-4ubuntu21.15" released.
See also these bug reports which somehow relate to the issue:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603
As I'm no
Thank you for your bug report. What update are you talking about? Did
you try to downgrade the packages to see if that resolves your issue?
The most recent security update includes fixes for journal and tmpfile
error, that shouldn't have an impact on the ssh service and there has
been no other
27 matches
Mail list logo
