Search results

  1. J

    Cluster nodes "offline" but working

    I have done it and nothing happens :(
  2. J

    Cluster nodes "offline" but working

    I have created a new cluster with 4 nodes, the problem is that when I reboot them all of them are working, but after some minutes some of them says that are disconnected. When this happens I execute in the shell node: service corosync restart After execute this command the node is online...
  3. J

    Some windows server 2003 are shutting down automatically in Proxmox VE 5.1

    I couldn't stop yet the vm, because they must be working until I have a backup vm, so I can't test it yet. I'll post the results when the changes have been done. Sorry for my English.
  4. J

    Some windows server 2003 are shutting down automatically in Proxmox VE 5.1

    Oh, maybe this is the problem, my vm aren't virtio too.
  5. J

    Some windows server 2003 are shutting down automatically in Proxmox VE 5.1

    proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve) pve-manager: 5.1-41 (running version: 5.1-41/0b958203) pve-kernel-4.13.13-2-pve: 4.13.13-32 libpve-http-server-perl: 2.0-8 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-19 qemu-server: 5.0-18 pve-firmware: 2.0-3...
  6. J

    Some windows server 2003 are shutting down automatically in Proxmox VE 5.1

    This version: proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
  7. J

    Some windows server 2003 are shutting down automatically in Proxmox VE 5.1

    Yes all of them are valid keys, in the windows syslog I only saw this [Event ID 6008 "The previous system shutdown at Time on Date was unexpected."], and in the proxmox syslog I saw nothing, I saw only a backup that was running when it happened. Could it be a problem because of the backup?
  8. J

    Some windows server 2003 are shutting down automatically in Proxmox VE 5.1

    Hello, Since a few days, some mv WS2003 are shutting down automatically (not forced stops). The vm are shutting down as if someone pressed start, shut down. After that, when I start the machine I found in the event viewer, the next thing: Event ID 6008 "The previous system shutdown at Time on...
  9. J

    Problem machine dissapeared in web gui after deleting .conf

    Finally I restored a vm backup that I had from the last day. I deleted previusly by console the vm and later I restored it.
  10. J

    Problem machine dissapeared in web gui after deleting .conf

    Hi, today I had a problem creating a snapshot, after that I couldn't remove the snapshot, I had this message: Cannot remove Snapshot ( VM is locked (snapshot-delete) ) I followed this thread: https://forum.proxmox.com/threads/cannot-remove-snapshot-vm-is-locked-snapshot-delete.37567/ And...
  11. J

    Problem adding 4th node to a cluster in Proxmox ve 5.1-3

    Thanks a lot, finally the problem was the gateway, that it was not correct. Regards.
  12. J

    Problem adding 4th node to a cluster in Proxmox ve 5.1-3

    Hi I'm creating a new setup, with 4 nodes. I have created the cluster in my node 1, and I can add the node 2 and 3, but when I add my node 4, I'm getting a timeout error and it doesn't finalize (I have reinstalled proxmox in all the nodes 3 times, and it happens again). I'm following this...

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!