*** This bug is a duplicate of bug 1804847 ***
https://bugs.launchpad.net/bugs/1804847
> @ddstreet please delete your packages from the PPA, as you are intentially
> distributing security vulnerable systemd.
hmm, i see you didn't actually look at my ppa, since if you did you'd
know i didn't
*** This bug is a duplicate of bug 1804847 ***
https://bugs.launchpad.net/bugs/1804847
OpenVZ has been proactive w.r.t. this issue and have issued an update
that includes the required backports a long time ago.
Please see this comment:
> This is something I (and quite many others) can't do anything, as the kernel
> is provided by OpenVZ
> This means, that the Xenial LTS has been broken :(
well...what you mean is that Xenial LTS is broken *when using a custom
kernel from OpenVZ*. The Xenial LTS isn't broken when using any
>> Uname: Linux 2.6.32-042stab128.2 x86_64
> you can't run this ancient kernel in a Xenial release
This is something I (and quite many others) can't do anything, as the
kernel is provided by OpenVZ. When I last time asked the service
provider, they estimated, that it would be on Q2/2019.
>
AHA!
> Uname: Linux 2.6.32-042stab128.2 x86_64
you can't run this ancient kernel in a Xenial release (and expect things
to work right). That's the cause of your problems; tmpfiles was
recently updated to start using fchownat() with the AT_EMPTY_PATH flag,
and:
$ man fchownat | grep
For Dan:
> then, reboot (so the problem is reproduced) and get the output of
> $ journalctl -b
Attached.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5255102/+files/journalctl.txt
--
You received this bug notification
For Dimitri:
> In addition to debug output from systemd-tmpfiles-setup.service
> as above, it is also interesting to know the permiissions
> on / itself, ie. what's the output of:
> $ ls -la /
kalle@vspk:~$ ls -la /
total 1272
drwxr-xr-x 24 root root4096 Apr 11 15:18 .
drwxr-xr-x 24 root
In addition to debug output from systemd-tmpfiles-setup.service as above, it is
also interesting to know the permiissions on / itself, ie. what's the output of:
$ ls -la /
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ok, let's try this; please create a file with the contents and location
shown below:
ubuntu@lp1818814:~$ cat
/etc/systemd/system/systemd-tmpfiles-setup.service.d/debug.conf
[Service]
Environment="SYSTEMD_LOG_LEVEL=debug"
PassEnvironment=SYSTEMD_LOG_LEVEL
then, reboot (so the problem is
Yes, tested, and sorry, it did not help. There are still the same errors
in syslog, and /var/run don't have proper directories for sshd etc.
The systemd (etc) version is now as follows:
kalle@vspk:~$ apt-cache policy systemd
systemd:
Installed: 229-4ubuntu21.21+bug1818814v20190411b1
ok, maybe there is a tmpfiles problem :)
can you test with the systemd pkg from this ppa?
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1818814
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix
** Attachment added: "find_run_ls_after_reboot.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5254877/+files/find_run_ls_after_reboot.txt
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
>> /var/run directories are not created properly
>what specifically do you mean by this? just that you see log errors?
Following directories were not created automatically, I had to create
them manually in order to enable services to start:
/var/run/fail2ban
/var/run/screen
/var/run/sshd
** Attachment added: "sudo_find_run_ls.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5254876/+files/sudo_find_run_ls.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Your /run dir and /var/run link look fine - I am 99% sure that tmpfiles
has nothing to do with whatever problem you're having (tmpfiles doesn't
even create the /var/run symlink, base-files does).
> /var/run directories are not created properly
what specifically do you mean by this? just that
About var.conf, I wrote that in the initial bug report:
"My first idea was, that for some reason, systemd-tmpfiles was not able to
create the /var directory properly, so I renamed /usr/lib/tmpfiles.d/var.conf
to var.conf, but it was no help."
The output of "ls -lad" is as follows:
Did you create/copy this file yourself? systemd drops the var.conf file
there, not var.conf...not that I see any reason it would cause any
problems, but it shouldn't be there.
/usr/lib/tmpfiles.d/var.conf
What does your /var/run and /run dirs look like?
$ ls -lad /run /var/run
**
Now I tested on the original host. On that machine, update to
229-4ubuntu21.21 did not work - /var/run directories are not created
properly and e.g. OpenSSH server can't start, following is printed on
the log:
Apr 10 13:31:24 vspk systemd[1]: Starting OpenBSD Secure Shell server...
Apr 10
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818814
Title:
systemd-tmpfiles-setup.services fails to create /var/run directories
Correction to previous comment: /var/run directories seem to be pretty
much ok now, i.e. openssh starts, but mysql refuses still to start. I'll
try to find out reason for that and get back to here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The problem still exists in the latest (229-4ubuntu21.21) version.
The grep result is attached as "grep_result.txt" file:
kalle@nxld:~$ grep . /etc/tmpfiles.d/* /run/tmpfiles.d/* /usr/lib/tmpfiles.d/*
> grep_result.txt
grep: /run/tmpfiles.d/*: No such file or directory
** Attachment added:
@kalle-tuulos,
are you able to test with the latest systemd pkgs to see if this still
happens? If it does, can you paste the output of:
$ grep . /etc/tmpfiles.d/* /run/tmpfiles.d/* /usr/lib/tmpfiles.d/*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I got this fixed by manually downgrading packages libsystemd0 and
systemd to versions 229-4ubuntu21.10. I just downloaded those from here:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+build/15710450
After rebooting the server, the system works again fine. Anyway, now I
Additional information: the problem appeared after updating
libsystemd0:amd64 from 229-4ubuntu21.10 to 229-4ubuntu21.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818814
Title:
24 matches
Mail list logo
