problem after update - pvestatd look for control socket

  • Thread starter Thread starter zvn
  • Start date Start date
Z

zvn

Guest
XXXXXXXX pvestatd[109381]: WARNING: unable to connect to VM 100 socket - No such file or directory

for all VM after an update

# pvestatd -v
USAGE: /usr/bin/pvestatd [--debug]

hmm

Is it Possible to create the socket without restarting the vms ?
 
What is the output of:

# pveversion -v


root:~# pveversion -v
pve-manager: 2.1-12 (pve-manager/2.1/be112d89)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-72
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-45
pve-firmware: 1.0-17
libpve-common-perl: 1.0-28
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-27
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-6
ksm-control-daemon: 1.1-1
 
Same behavior



root@ns222594:~# pveversion -a
Unknown option: a
USAGE: pveversion [--verbose]
root@ns222594:~# pveversion -v
pve-manager: 2.1-13 (pve-manager/2.1/bdd3663d)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-72
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-47
pve-firmware: 1.0-17
libpve-common-perl: 1.0-28
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-29
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-6
ksm-control-daemon: 1.1-1


(it was After an update !)
 
Why do you run that command?

# pvestatd -v

That is simple no valid command.

Does it help if you stop the VM, and start it again?
 
Last edited:
Why do you run that command?

# pvestatd -v

That is simple no valid command.

Yes, dont you see the irony >...

Does it help if you stop the VM, and start it again?

As i said i dont want to do that. I was asking , is there a way to create the control socket ewith qemu while they are up
 
What if i link :

/var/run/qemu-server/XXX.qmp to /var/run/qemu-server/XXX.mon
 
Ok, I can see the bug now. Seems those VMs are started before we added the new control socket.

Unfortunately, the only way I see is to restart those VMs. I guess you can still open the console? If so, do a power-down, then restart the VM.
 
Ok, I can see the bug now. Seems those VMs are started before we added the new control socket.

Unfortunately, the only way I see is to restart those VMs. I guess you can still open the console? If so, do a power-down, then restart the VM.

I have the same problem, but an restart does not help to fix this. I only have problems with my Windows-Guest.

Any other idea? Any workaround? The Windows-Guest won't start and i need them.

Regards,

f.
 
What error do you get exactly?

Aug 16 11:56:53 imp02 pvedaemon[18413]: start VM 101: UPID:imp02:000047ED:000A791E:502CC3E5:qmstart:101:root@pam:
Aug 16 11:56:53 imp02 pvedaemon[15649]: <root@pam> starting task UPID:imp02:000047ED:000A791E:502CC3E5:qmstart:101:root@pam:
Aug 16 11:56:53 imp02 kernel: device tap101i0 entered promiscuous mode
Aug 16 11:56:53 imp02 kernel: vmbr0: port 12(tap101i0) entering forwarding state
Aug 16 11:56:57 imp02 pvedaemon[15649]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 11:56:58 imp02 pvedaemon[15650]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 11:56:59 imp02 pvedaemon[15648]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 11:57:00 imp02 pvedaemon[15649]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 11:57:01 imp02 pvedaemon[15649]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 11:57:02 imp02 pvedaemon[15649]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 11:57:03 imp02 pvedaemon[15650]: WARNING: unable to connect to VM 101 socket - Resource temporarily unavailable
Aug 16 11:57:04 imp02 kernel: tap101i0: no IPv6 routers present
 
root@imp02 /var/log/pve/tasks # pveversion -v
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-73
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-14-pve: 2.6.32-73
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-48
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-30
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-7
ksm-control-daemon: 1.1-1



And how do you stop that VM?

I open the console-windows and click on the stop-button.
 
You need to login into the VM, then do a shutdown inside the VM (because stop button does not work because of the bug)

i can't login. console isn't working on these windows-guests. i get an "Network error:remote side closed connection"-error.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!