pveproxy running in circles an VMs not starting from console

It was dumm and it was late at night. I simply did aptitude update && aptitude -y safe-upgrade && reboot the machine.

There seemed to be a hang up with man-db, everything else (kernel, apt, etc.) updated.

I rebuild the man-db db.

But where did the webinterface go ?? Why wheren't the VMs started. Checking netstat, pveproxy is on port 8006.

Noticed while looking at top that pveproxy was hooging the machine (2.4 1.9 0.8 ... not really another process in sight). Checking the logs, they are full with:

Jan 22 12:41:58 dakota pveproxy[3673]: worker 99733 finished
Jan 22 12:41:58 dakota pveproxy[3673]: starting 1 worker(s)
Jan 22 12:41:58 dakota pveproxy[3673]: worker 99736 started
Jan 22 12:41:58 dakota pveproxy[3673]: worker 99734 finished
Jan 22 12:41:58 dakota rsyslogd-2177: imuxsock begins to drop messages from pid 3673 due to rate-limiting

Rebooting the machine, restarting the service, reinstalling the packages is all of no help. Starting the VMs by hand with qm start 100 brings:

start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -name 146 -smp 'sockets=1,cores=2' -nodefaults -boot 'menu=on' -vga qxl -cpu kvm64,+lahf_lm,+x2apic,+sep -k de -m 6144 -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -spice 'tls-port=61000,addr=127.0.0.1,tls-ciphers=DES-CBC3-SHA,seamless-migration=on' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,aio=native,cache=none,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=8E:76:AE:28:D9:46,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

Anyone an idea, as I am not sure where to look anymore. Other data about the machine:

root@dakota ~ # pveversion -v
proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-30-pve: 2.6.32-130
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
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-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
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-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
Last edited:
Ok, so I have check anything I could think of. Even read in detail the dpkg.log to see if I didn't miss anything.

Nothing.

I guess this is just a fluke.

So it is time to delete theserver and set it up new. Import the backups and call it a bad day.
 
Hi spirit,

Yes, that would have been an idea. But too late. I kompletely set it up new and dropped the backups in place.

However I have a feeling that with pveproxy spinning endlessly hat high volume I broke more than meets the eye.

It was a test setup, I found half a year old fragments of trying to get openvpn working and other bits, who knows what I all did to that poor machine.