PVE 4.2-15 Container not starting ext4-fs Device is already active on another node

[Björn]

Hello Everybody,

we run proxmox 4.2.15 and have some issues with a lxc container running Debian 8.5
Inside the container we installed McAffee VirusScan Enterprise for Linux.
Now the problem is everything is fine until we want to restart the container.
After shutdown it is not starting anymore.
Without McAffee everything is working fine.

Attached is the output of

pveversion -v
syslog
lxc log

Any help is highly appreciated!


Best Regards,
Björn




pveversion -v :

proxmox-ve: 4.2-52 (running kernel: 4.4.8-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.8-1-pve: 4.4.8-52
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-83
pve-firmware: 1.1-8
libpve-common-perl: 4.0-70
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-55
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-70
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80

var/lib/syslog

Jul  8 14:13:15 pve pvedaemon[7509]: starting CT 100: UPID:pve:00001D55:0008CD3F:577F98DB:vzstart:100:root@pam:
Jul  8 14:13:15 pve kernel: [ 5767.478354] EXT4-fs warning (device loop1): ext4_multi_mount_protect:318: MMP interval 42 higher than expected, plea                  se wait.
Jul  8 14:13:15 pve kernel: [ 5767.478354]
Jul  8 14:13:36 pve kernel: [ 5788.471104] EXT4-fs warning (device loop1): ext4_multi_mount_protect:331: Device is already active on another node.
Jul  8 14:13:36 pve kernel: [ 5788.471108] EXT4-fs warning (device loop1): ext4_multi_mount_protect:331: MMP failure info: last update time: 1467980015, last update node: pve, last update device: loop0
Jul  8 14:13:36 pve kernel: [ 5788.471108]
Jul  8 14:13:37 pve pvedaemon[6940]: unable to get PID for CT 100 (not running?)
Jul  8 14:13:37 pve pvestatd[1172]: status update time (15.878 seconds)
Jul  8 14:13:37 pve pmxcfs[1108]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve/local: -1
Jul  8 14:13:42 pve pvedaemon[7509]: command 'lxc-start -n 100' failed: exit code 1

from the lxc log

lxc-start 1467619084.340 INFO     lxc_seccomp - seccomp.c:parse_config_v2:429 - Adding compat rule for delete_module action 327681
lxc-start 1467619084.340 INFO     lxc_seccomp - seccomp.c:parse_config_v2:436 - Merging in the compat seccomp ctx into the main one
lxc-start 1467619084.340 INFO     lxc_start - start.c:lxc_check_inherited:226 - closed inherited fd 4
lxc-start 1467619084.340 INFO     lxc_conf - conf.c:run_script_argv:362 - Executing script '/usr/share/lxc/hooks/lxc-pve-prestart-hook' for container '100', config section 'lxc'
lxc-start 1467619084.344 INFO     lxc_monitor - monitor.c:lxc_monitor_sock_name:178 - using monitor sock name lxc/ad055575fe28ddd5//var/lib/lxc
lxc-start 1467619085.202 ERROR    lxc_conf - conf.c:run_buffer:342 - Script exited with status 255
lxc-start 1467619085.202 ERROR    lxc_start - start.c:lxc_init:436 - failed to run pre-start hooks for container '100'.
lxc-start 1467619085.202 ERROR    lxc_start - start.c:__lxc_start:1170 - failed to initialize the container
lxc-start 1467619085.202 WARN     lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - command get_init_pid failed to receive response
lxc-start 1467619085.202 WARN     lxc_cgmanager - cgmanager.c:cgm_get:994 - do_cgm_get exited with error
lxc-start 1467619090.208 ERROR    lxc_start_ui - lxc_start.c:main:344 - The container failed to start.
lxc-start 1467619090.208 ERROR    lxc_start_ui - lxc_start.c:main:346 - To get more details, run the container in foreground mode.
lxc-start 1467619090.208 ERROR    lxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options.