[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-12 Thread Dan Streetman
*** 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 revert the security patches.  so no need to delete it.

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-12 Thread Dimitri John Ledkov
*** 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:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/comments/20

"""
Updated OpenVz6 kernel was released:
https://wiki.openvz.org/Download/kernel/rhel6/042stab134.7

We are very grateful for Ubuntu team for reverting of patches specially
for OpenVz.

For affected hosters: OpenVz6 is great but it is really old,
and similar incidents can happen again and again.
Please think about switch to RHEL7-based OpenVz7.

Thank you,
   Vasily Averin
"""

Which was released in November 2018. All your provider needs to do, is
to apply OpenVZ updates.

>From Ubuntu point of view this is a wontfix, as providing systemd
without using fchownat opens a security vulnerability CVE-2018-6954.

Please upgrde to OpenVZ kernel 042stab134.7 or anything better. I
believe currently the latest kernel is 042stab136.1.

@ddstreet please delete your packages from the PPA, as you are
intentially distributing security vulnerable systemd.

Regards,

Dimitri.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6954

** Changed in: systemd (Ubuntu Xenial)
   Status: Invalid => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

** This bug has been marked a duplicate of bug 1804847
   systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-12 Thread Dan Streetman
> 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 kernel
provided by Ubuntu in the Xenial release.  So, it's rather likely
someone else will come along and set this bug back to Invalid.

> I'm changing this status back to New, as there needs to be a way to support
> Xenial installations in OpenVZ environments

a way for who to support Xenial, OpenVZ?  Sure, they could provide a
custom systemd package, that works with the custom kernel they provide.

Without a custom systemd package from OpenVZ, you have a couple options; you 
can pin your systemd version to the last one before the change to use 
fchownat().  You'll never get any more systemd upgrades for bugfixes, or 
security issues, though.  Alternately, you can maintain your own systemd 
package with a patch to replace the fchownat() usage; I have a test build in 
this ppa
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1818814

The last patch listed in the debian/patches/series file is what reverts
the fchownat() back to a fchown().

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-12 Thread Kalle Tuulos
>> 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.

> tmpfiles was recently updated to start using fchownat()
> with the AT_EMPTY_PATH flag, and:
> $ man fchownat | grep AT_EMPTY_PATH
>   AT_EMPTY_PATH (since Linux 2.6.39)

This means, that the Xenial LTS has been broken :(

I'm changing this status back to New, as there needs to be a way to
support Xenial installations in OpenVZ environments, until service
providers have upgraded their systems.


** Changed in: systemd (Ubuntu)
   Status: Invalid => New

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-12 Thread Dan Streetman
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 AT_EMPTY_PATH
   AT_EMPTY_PATH (since Linux 2.6.39)

upgrade your kernel to a supported version provided by Ubuntu in Xenial.

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Invalid

** Changed in: systemd (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: systemd (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: systemd (Ubuntu Xenial)
   Importance: Medium => Undecided

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-12 Thread Kalle Tuulos
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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Kalle Tuulos
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 root4096 Apr 11 15:18 ..
drwx--   2 root root4096 Nov 27  2016 
.cpt_hardlink_dir_a920e4ddc233afddc9fb53d26c392319
-rw-r--r--   1 root root   0 Apr 11 15:20 .vzfifo
drwxr-xr-x   2 root root4096 Apr 11 15:17 bin
drwxr-xr-x   2 root root4096 May 14  2018 boot
-rw---   1 root root 1671168 Apr 11 15:19 core
drwxr-xr-x   5 root root 640 Apr 11 15:19 dev
drwxr-xr-x 154 root root   12288 Apr 11 15:18 etc
drwxr-xr-x   5 root root4096 Apr 10 15:46 home
drwxr-xr-x  16 root root4096 Jun  9  2018 lib
drwxr-xr-x   2 root root4096 Mar  4 08:56 lib64
drwx--   2 root root4096 Nov 27  2016 lost+found
drwxr-xr-x   2 root root4096 Nov 27  2016 media
drwxr-xr-x   2 root root4096 Nov 27  2016 mnt
drwxr-xr-x   2 root root4096 Nov 27  2016 opt
dr-xr-xr-x 139 root root   0 Apr 11 15:18 proc
drwx--   9 root root4096 Apr 11 08:29 root
drwxr-xr-x  32 root root 980 Apr 12 08:25 run
drwxr-xr-x   2 root root   12288 Apr 11 15:17 sbin
drwxr-xr-x   2 root root4096 May 14  2018 snap
drwxr-xr-x   2 root root4096 Nov 27  2016 srv
drwxr-xr-x   7 root root   0 Apr 11 15:18 sys
drwxrwxrwt   9 root root4096 Apr 12 08:25 tmp
drwxr-xr-x  10 root root4096 Nov 27  2016 usr
drwxr-xr-x  13 root root4096 Dec 17 13:37 var

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Dimitri John Ledkov
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.
https://bugs.launchpad.net/bugs/1818814

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Dan Streetman
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 reproduced) and get the output of

$ journalctl -b

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Kalle Tuulos
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
  Candidate: 229-4ubuntu21.21+bug1818814v20190411b1
  Version table:
 *** 229-4ubuntu21.21+bug1818814v20190411b1 500
500 http://ppa.launchpad.net/ddstreet/lp1818814/ubuntu xenial/main 
amd64 Packages
100 /var/lib/dpkg/status
 229-4ubuntu21.21 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Dan Streetman
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 Released

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Kalle Tuulos
** 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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Kalle Tuulos
>> /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
/var/run/zabbix

Following directory was created, but its ownership was not proper:

/var/run/redis

> What's the output of:

> $ sudo find /run -ls
Please see attached file: sudo_find_run_ls.txt (working situation) and 
find_run_ls_after_reboot.txt (after the system was rebooted i.e. not working 
situation).

> $ df
Filesystem 1K-blocksUsed Available Use% Mounted on
/dev/simfs  52428800 7818704  44610096  15% /
devtmpfs 1572864   0   1572864   0% /dev
tmpfs1572864   0   1572864   0% /dev/shm
tmpfs15728649488   1563376   1% /run
tmpfs   5120   4  5116   1% /run/lock
tmpfs1572864   0   1572864   0% /sys/fs/cgroup
none 1572864   0   1572864   0% /run/shm


To make this a bit more complete, I removed the var.conf and restarted the 
system. When I checked the md5sum of files /usr/lib/tmpfiles.d, they matched to 
my other Ubuntu 16.04 server.

After reboot, syslog relevant parts showed following:
---8<---8<---
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: [/usr/lib/tmpfiles.d/var.conf:14] 
Duplicate line for path "/var/log", ignoring.
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of /run/named failed: 
Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: Failed to validate path 
/var/run/fail2ban: Too many levels of symbolic links
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of /run/redis failed: 
Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: Failed to validate path 
/var/run/screen: Too many levels of symbolic links
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: Failed to validate path 
/var/run/sshd: Too many levels of symbolic links
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: Failed to validate path 
/var/run/sudo: Too many levels of symbolic links
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: Failed to validate path 
/var/run/sudo/ts: Too many levels of symbolic links
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of /run/utmp failed: 
Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of /run/systemd/netif 
failed: Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: Failed to validate path 
/var/run/zabbix: Too many levels of symbolic links
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of /run/log/journal 
failed: Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of 
/run/log/journal/6d9c7cc322ee4c48af7c0ec3b492b5cc failed: Invalid argument
Apr 11 08:44:50 vspk systemd-tmpfiles[85]: fchownat() of 
/run/log/journal/6d9c7cc322ee4c48af7c0ec3b492b5cc/system.journal failed: 
Invalid argument
Apr 11 08:44:50 vspk systemd[1]: systemd-tmpfiles-setup.service: Main process 
exited, code=exited, status=1/FAILURE
Apr 11 08:44:50 vspk systemd[1]: Failed to start Create Volatile Files and 
Directories.
Apr 11 08:44:50 vspk systemd[1]: systemd-tmpfiles-setup.service: Unit entered 
failed state.
Apr 11 08:44:50 vspk systemd[1]: systemd-tmpfiles-setup.service: Failed with 
result 'exit-code'.
---8<---8<---

This caused, that sshd, redis, fail2ban and zabbix agent were not able
to start.

In order for me to make the system usable, I needed to perform following
steps:

1) Log in to system using the serial console from the VPS control panel.

root@vspk:/var/run# ls -la /var/run 
 
lrwxrwxrwx 1 root root 4 May 14  2018 /var/run -> /run  
   

Contents of /run directory:
root@vspk:/var/run# find /run -ls > /home/kalle/find_run_ls_after_reboot.txt 
(attached)

2) Give following commands:

root@vspk:/var/run# mkdir sshd  
 
root@vspk:/var/run# /etc/init.d/ssh start   
 
Starting ssh (via systemctl): ssh.service.

--> Now the system can be again accessed through SSH.

After that:
kalle@vspk:~$ sudo mkdir /var/run/zabbix
kalle@vspk:~$ sudo chown zabbix:zabbix /var/run/zabbix
kalle@vspk:~$ sudo chown redis:redis /var/run/redis
kalle@vspk:~$ sudo mkdir /var/run/fail2ban
kalle@vspk:~$ sudo mkdir /var/run/screen
kalle@vspk:~$ sudo chmod 777 /var/run/screen

-- 
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 

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-11 Thread Kalle Tuulos
** 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.
https://bugs.launchpad.net/bugs/1818814

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-10 Thread Dan Streetman
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 you see log errors?

What's the output of:

$ sudo find /run -ls

$ df


** 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-10 Thread Kalle Tuulos
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:

kalle@vspk:~$ ls -lad /run /var/run
drwxr-xr-x 31 root root 980 Apr 10 23:03 /run
lrwxrwxrwx  1 root root   4 May 14  2018 /var/run -> /run


** Changed in: systemd (Ubuntu)
   Status: Incomplete => New

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-10 Thread Dan Streetman
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

** 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-10 Thread Kalle Tuulos
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 13:31:24 vspk sshd[1928]: Missing privilege separation directory: 
/var/run/sshd
Apr 10 13:31:24 vspk systemd[1]: ssh.service: Control process exited, 
code=exited status=255
Apr 10 13:31:24 vspk systemd[1]: Failed to start OpenBSD Secure Shell server.
Apr 10 13:31:24 vspk systemd[1]: ssh.service: Unit entered failed state.
Apr 10 13:31:24 vspk systemd[1]: ssh.service: Failed with result 'exit-code'.

Grep results are attached.


** Attachment added: "grep_result.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5254655/+files/grep_result.txt

** Changed in: systemd (Ubuntu)
   Status: Incomplete => New

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-09 Thread Dan Streetman
** 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-09 Thread Kalle Tuulos
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 to Ubuntu.
https://bugs.launchpad.net/bugs/1818814

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-09 Thread Kalle Tuulos
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: "Grep result"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5254409/+files/grep_result.txt

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-04-08 Thread Dan Streetman
@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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818814

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-03-06 Thread Kalle Tuulos
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
have to take care, that I don't upgrade my other VPS servers before this
bug has been corrected.

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

2019-03-06 Thread Kalle Tuulos
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:
  systemd-tmpfiles-setup.services fails to create /var/run directories

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs