Wired uptime problem with LXC Containers

[dw2412]

Hi all out there,

today it happened again - I've found out some strange behaviour in Proxmox 4 with LXC Containers. Container is running Ubuntu 14.04 LTS all updates applied, Node is running Proxmox, all patches applied:

proxmox-ve: 4.2-54 (running kernel: 4.4.8-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-81
pve-firmware: 1.1-8
libpve-common-perl: 4.0-68
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-68
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-pve9~jessie

root@mysql:~# uptime
 08:32:52 up 4 days, 16:01,  0 users,  load average: 1.45, 0.82, 0.62
root@mysql:~# ./mysqltuner.pl
 >>  MySQLTuner 1.6.10 - Major Hayden <major@mhtx.net>
 >>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
 >>  Run with '--help' for additional options and output filtering
[OK] Logged in using credentials from debian maintenance account.

[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.6.30-0ubuntu0.14.04.1
[OK] Operating on 64-bit architecture

-------- CVE Security Recommendations --------------------------------------------------------------
[OK] NO SECURITY CVE FOUND FOR YOUR VERSION

-------- Performance Metrics -----------------------------------------------------------------------
[--] Up for: 29d 0h 23m 44s (2 q [0.000 qps], 425K conn, TX: 185B, RX: 262B)

Please have a look at uptime output and on performance metrices - they're quite different and container was not restartet.

I've no idea why this happens but it seems to be independent from which kernel is currently being used. I experience this already since long time but only found time now to document it here.

Thanks for help

Andreas