[SOLVED] When you restart a node, all VMs were killed, not cleanly shutdown

fireon

Famous Member
Oct 25, 2010
3,906
324
103
40
Austria/Graz
iteas.at
I noticed by chance... since PVE4 when we shudown a node or reboot a node, all VMs were killed!!! What a f.... I setuped a new Host with PVE4 for testing. Same thing. On PVE we never had this problem. So... do i something wrong? Or is it a nice Bug?
For info: When i click on an VM and say shutdown in PVE this works fine, Linux and Windows. But on Shutdown the Host or reboot the Host the VMs were killed.

So what about the nice button on the right side? On "more" i can click on "stop all vms". Never testet the button. But when you shutdown/reboot a node, this is the message you can see in task.

Is the already noticed someone?

Thanks and best Regards
 
Last edited:

Knight

Member
Mar 24, 2014
6
1
23
I have the same problem with pve 3.4

If the system sends the stopall command to the manager it responds with

Code:
pvesh starting task stopall 
pvesh : writing cluster log failed : ipcc_send_rec failed : Connection refused
pvesh : end task stopall OK
pvesh : writing cluster log failed : ipcc_send_rec failed : Connection refused

Code:
# pvecm status
cman_tool: Cannot open connection to cman, is it running ?

This is atm my only problem why i can't update to pve 4 - any ideas?

I had to truncate this because vbulletin recognizes in my log any kind of images or something :)
 

fireon

Famous Member
Oct 25, 2010
3,906
324
103
40
Austria/Graz
iteas.at
Tested in actually "no sub. Repo". The button "stopall" works correctly. It shutdown all VMs cleanly. But it is an good idea to change the stopicon to the shutdownicon.

The reboot and shutdown of the server kills the vm's
immediately. Not yet fixed.

proxmox-ve: 4.0-19 (running kernel: 4.2.3-2-pve)
pve-manager: 4.0-57 (running version: 4.0-57/cc7c2b53)
pve-kernel-4.2.3-2-pve: 4.2.3-19
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-24
qemu-server: 4.0-35
pve-firmware: 1.1-7
libpve-common-perl: 4.0-36
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-29
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-12
pve-container: 1.0-20
pve-firewall: 2.0-13
pve-ha-manager: 1.0-13
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.4-3
lxcfs: 0.10-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve4~jessie

Thanks for help and best Regards
fireon
 

fireon

Famous Member
Oct 25, 2010
3,906
324
103
40
Austria/Graz
iteas.at
It is working now, after Upgrade.
pve-manager/4.1-1/2f9650d4 (running kernel: 4.2.6-1-pve)
Bug is fixed in nosubscription and enterprise repo.
Thanks!
 

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 your own in 60 seconds.

Buy now!