[SOLVED] pvestatd causing major kernel warnings

[12jdlovins]

For some reason when pvestatd is enabled, i get a slew of kernel issues. Something about being tainted, as soon as i disable it, syslog doesnt get slammed with stuff anymore

https://transfer.sh/M4TE9/syslog.txt

 

[12jdlovins]

Relevant information i think, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609

 

[wolfgang]

Hi,

can you please send your version.

pveversion -v

 

[12jdlovins]

Hi,

can you please send your version.

pveversion -v

Latest version,

proxmox-ve: 5.0-21 (running kernel: 4.10.17-3-pve)
pve-manager: 5.0-31 (running version: 5.0-31/27769b1f)
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.79-1-pve: 4.4.79-95
pve-kernel-4.10.17-3-pve: 4.10.17-21
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-5
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.11-pve17~bpo90
openvswitch-switch: 2.7.0-2

It also says in the logs that a process is tainted, when i look for the pid thats tainted its always pvestatd.

 

[micro]

https://bugzilla.proxmox.com/show_bug.cgi?id=1505

Related ?

 

[12jdlovins]

https://bugzilla.proxmox.com/show_bug.cgi?id=1505

Related ?

seems to be the exact same thing. It doesnt seem to hurt anything obviously but i would still like to not have my syslogs spammed

 

[12jdlovins]

.

Any ideas on what is going on with it? It doesnt seem to be impacting anything negatively but definitely is annoying.

 

[fabian]

updated kernel (package version 4.10.17-23) on pvetest should fix this.

 

[12jdlovins]

updated kernel (package version 4.10.17-23) on pvetest should fix this.

Good to know! Is it safe to jump to that kernel for now to remove the errors and then jump back to stable once it gets merged into it?

 

[fabian]

Good to know! Is it safe to jump to that kernel for now to remove the errors and then jump back to stable once it gets merged into it?

it contains other changes as well (everything from Ubuntu-4.10.0-35.39 and -34.38), so you'll need to decide for yourself