Pvedaemon worker with pveprox producing higher than expected CPU utilization

[drott]

Hello,

With the most recent updates applied to 3.3 Proxmox, both pvedaemon and pveproxy are consuming approximately 6+ percent CPU on a regular and consistent basis.

Looked in sys log and there are a number of worker processes firing.

This sever should be at near zero cpu utilization and only brief peaks. This server is running light duty apache Deb 7 CT's only.

I compared this to an identically configured server that has not been upgrade yet and runs 2 good size mail server hosting lots of people and the entire system is running a .02.

Any place I can look to get an idea.

Thanks in advance


PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
40635 root 20 0 287m 62m 6488 S 5.6 0.2 0:13.85 pvedaemon worke
50790 www-data 20 0 285m 60m 4504 S 1.0 0.2 0:03.75 pveproxy worker
56026 root 20 0 23536 2000 1192 R 1.0 0.0 0:00.13 top


Syslog

Feb 15 09:28:27 exxxxx pvedaemon[2738]: worker exit
Feb 15 09:28:27 exxxxx pvedaemon[2737]: worker 2738 finished
Feb 15 09:28:27 exxxxx pvedaemon[2737]: starting 1 worker(s)
Feb 15 09:28:27 exxxxx pvedaemon[2737]: worker 49717 started
Feb 15 09:29:47 exxxxx pveproxy[32647]: worker exit
Feb 15 09:29:47 exxxxx pveproxy[2765]: worker 32647 finished
Feb 15 09:29:47 exxxxx pveproxy[2765]: starting 1 worker(s)
Feb 15 09:29:47 exxxxx pveproxy[2765]: worker 50790 started
Feb 15 09:30:19 exxxxx pveproxy[35329]: worker exit
Feb 15 09:30:19 exxxxx pveproxy[2765]: worker 35329 finished
Feb 15 09:30:19 exxxxx pveproxy[2765]: starting 1 worker(s)
Feb 15 09:30:19 exxxxx pveproxy[2765]: worker 51190 started


Output of pveversion
proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve)
pve-manager: 3.3-19 (running version: 3.3-19/c4c740ea)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-37-pve: 2.6.32-147
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-31-pve: 2.6.32-132
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-17
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-30
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[dietmar]

How many open web clients access the proxmox gui? You can analyze that with /var/log/pveproxy/access.log

CPU usage should be zero unless someone use the GUI (or API).

 

[drott]

How many open web clients access the proxmox gui? You can analyze that with /var/log/pveproxy/access.log

CPU usage should be zero unless someone use the GUI (or API).

HI, One me and that is not that often since I work mostly with the CLI.

I noticed in Top with pvestatd that on the upgraded machine it runs consistently at 5.2% CPU
noupgraded machine it runs around 2.3% CPU

Notice at when In top for the upgraded machine pvestatd and other pvecfx will show for 5 second vs 1second when running top on the other machine. They are identical machines which helps when looking at things.


I will check.

Thanks for responding on Sunday. aka SONTAG.