On Thu, 7 May 2015 at 14:43 Brian May <br...@microcomaustralia.com.au>
wrote:
> Looks like my system is still using wheezy/pve which has somewhat old
> packages; will need to change that to wheezy/pve-no-subscription and update
> as soon as I can.
>
So I upgraded my kernel, at first glance it seems a lot healthier. I
noticed there are still some issues:
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
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
It provides more information if I attempt a restart:
root@webby:~# systemctl start proc-sys-fs-binfmt_misc.automount
Job for proc-sys-fs-binfmt_misc.automount failed. See 'systemctl status
proc-sys-fs-binfmt_misc.automount' and 'journalctl -xn' for details.
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 16 11:05:13 webby systemd[1]: Starting Arbitrary Executable File
Formats File System Automount Point.
May 16 11:05:13 webby systemd[1]: Failed to initialize automounter: No such
file or directory
May 16 11:05:13 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 Sat 2015-05-16 10:51:29 AEST;
5min ago
Process: 237 ExecStart=/etc/init.d/vzquota start (code=exited, status=2)
May 16 10:51:29 webby systemd[1]: Starting LSB: Start vzquota at the end of
boot...
May 16 10:51:29 webby vzquota[237]: quotaon: using //aquota.group on
/dev/simfs [/]: Device or resource busy
May 16 10:51:29 webby vzquota[237]: quotaon: using //aquota.user on
/dev/simfs [/]: Device or resource busy
May 16 10:51:29 webby systemd[1]: vzquota.service: control process exited,
code=exited status=2
May 16 10:51:29 webby systemd[1]: Failed to start LSB: Start vzquota at the
end of boot.
May 16 10:51:29 webby systemd[1]: Unit vzquota.service entered failed state.
Doing a Google search on the first suggests that I check autofs4 is
compiled into the kernel; it is:
gyro:~# cat /boot/config-2.6.32-39-pve | grep -i autofs
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
I even tried manually loading the module, but it didn't help.
Looks like /etc/init.d/vzquota is a script not owned by any package:
root@webby:~# sh -ex /etc/init.d/vzquota start
+ start
+ [ ! -L /etc/mtab ]
+ awk ($2 == "/") && ($4 ~ /usrquota/) && ($4 ~ /grpquota/) {print $1}
/etc/mtab
+ dev=/dev/simfs
+ test -z /dev/simfs
+ [ -e /dev/simfs ]
+ quotaon -aug
quotaon: using //aquota.group on /dev/simfs [/]: Device or resource busy
quotaon: using //aquota.user on /dev/simfs [/]: Device or resource busy
I don't particularly care so much about quota support, however the first
one would suggest that systemd isn't running 100%.
Any ideas?
