Debian Jessie Systemd Degraded

P

penguin_brian

New Member
Dec 9, 2010
14
0
1
linuxpenguins.xyz
Hello,

After upgrading my kernel to the latest 2.6.32-39-pve, I upgraded a VM to Debian Jessie. It seems to work well, however systemd reports it is degraded:

Code: 
● webby
    State: degraded
     Jobs: 0 queued
   Failed: 2 units
    Since: Sat 2015-05-16 10:51:28 AEST; 2 weeks 1 days ago

If I look up details on the failed units, I see:

Code: 
● proc-sys-fs-binfmt_misc.automount       loaded failed failed    Arbitrary Executable File Formats File System Automount Point
● vzquota.service                         loaded failed failed    LSB: Start vzquota at the end of boot

This is where I get stuck. "Failed to initialize automounter: No such file or directory" - am I missing something. vzquota seems to die due to the quotaon syscall failing.

Code: 
root@webby:~# systemctl status proc-sys-fs-binfmt_misc.automount
● proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point
   Loaded: loaded (/lib/systemd/system/proc-sys-fs-binfmt_misc.automount; static)
   Active: failed (Result: resources)
    Where: /proc/sys/fs/binfmt_misc
     Docs: https://www.kernel.org/doc/Documentation/binfmt_misc.txt
           http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems

May 31 13:58:29 webby systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
May 31 13:58:29 webby systemd[1]: Failed to initialize automounter: No such file or directory
May 31 13:58:29 webby systemd[1]: Failed to set up automount Arbitrary Executable File Formats File System Automount Point.
root@webby:~# systemctl status vzquota.service
● vzquota.service - LSB: Start vzquota at the end of boot
   Loaded: loaded (/etc/init.d/vzquota)
   Active: failed (Result: exit-code) since Sun 2015-05-31 13:58:35 AEST; 21s ago
  Process: 14589 ExecStart=/etc/init.d/vzquota start (code=exited, status=2)

May 31 13:58:35 webby systemd[1]: Starting LSB: Start vzquota at the end of boot...
May 31 13:58:35 webby vzquota[14589]: quotaon: using //aquota.group on /dev/simfs [/]: Device or resource busy
May 31 13:58:35 webby vzquota[14589]: quotaon: using //aquota.user on /dev/simfs [/]: Device or resource busy
May 31 13:58:35 webby systemd[1]: vzquota.service: control process exited, code=exited status=2
May 31 13:58:35 webby systemd[1]: Failed to start LSB: Start vzquota at the end of boot.
May 31 13:58:35 webby systemd[1]: Unit vzquota.service entered failed state.

Any ideas??

Thanks
 
First, v4.0 is not ready for general use. Besides, openvz does not work on 4.0, because there is no stable openvz release for kernel 3.10 or newer.
 
dietmar said:
First, v4.0 is not ready for general use. Besides, openvz does not work on 4.0, because there is no stable openvz release for kernel 3.10 or newer.
Click to expand...

I am not sure how this relates to my question. I am using 2.6.32-39-pve, I have been told (on debian-devel) that this contains backports of the features systemd requires from newer kernels.

I never mentioned anything about using v4 kernels.
 
udo said:
Hi,
your upgraded VM is an Container? EG. you upgraded an wheezy-CT to jessie?

Udo
Click to expand...

Sorry, I should have been more clear. Yesm this was a Container. Jessie + Systemd work fine (as expected) in a VM.

I have been led to believe that systemd works fine on proxmox as long as the host kernel is using the lastest proxmox kernel, which appears to be the 2.6.32-39-pve kernel that I am using.
 
No, since the pve kernel is a Redhat kernel and systemd requires kernel support and the fact that systemd is first supported in RHEL 7 this means IMHO you need to run a 3.10 kernel to be able to have systemd in a CT. Second, OpenVZ is not supported in the 3.10 kernel so you are restricted to running CT with SYSV init system. Debian Jessie can be installed without systemd: https://wiki.debian.org/systemd#Installing_without_systemd
 
Last edited:
mir said:
No, since the pve kernel is a Redhat kernel and systemd requires kernel support and the fact that systemd is first supported in RHEL 7 this means IMHO you need to run a 3.10 kernel to be able to have systemd in a CT. Second, OpenVZ is not supported in the 3.10 kernel so you are restricted to running CT with SYSV init system. Debian Jessie can be installed without systemd: https://wiki.debian.org/systemd#Installing_without_systemd
Click to expand...

I have been told that the required changes were backported into version -37 of the kernel.

https://lists.debian.org/20150504091205.GB18109@fernst.no-ip.org

Actually we are kind of getting off track here, because the system clearly boots systemd just fine, it is just two (I suspect relatively minor) components that don't work correctly.
 
penguin_brian said:
I have been told that the required changes were backported into version -37 of the kernel.

https://lists.debian.org/20150504091205.GB18109@fernst.no-ip.org

Actually we are kind of getting off track here, because the system clearly boots systemd just fine, it is just two (I suspect relatively minor) components that don't work correctly.
Click to expand...

Just for reference:

root@webby:~# quotaon -a
quotaon: using //aquota.group on /dev/simfs [/]: Device or resource busy
quotaon: using //aquota.user on /dev/simfs [/]: Device or resource busy
Click to expand...

I don't see how this relates in anyway to systemd.

Also for the record, installing Jessie without systemd isn't always an option, because some packages in Debian stable don't work with out it.

I suspect the best way forward is to gradually replace my openvz containers with KVM images. That way hopefully I can remove my dependency on proxmox too; which seems to be ultra conservative with updates and now wants to get paid far more then I can afford for a private home VM system for the privilege.
 
You must log in or register to reply here.
Top Bottom