Recent content by hermelin

  1. [SOLVED] Promox 6: problem with noVNC - failed to connect to server

    solved https://forum.proxmox.com/threads/certain-vms-from-a-cluster-cannot-be-backed-up-and-managed.57016/page-5#post-272544
  2. [SOLVED] Certain VMs from a cluster cannot be backed up and managed

    Yes, you need shutdown and start again the VMs. Or maybe help hibernate and start, but this I didn't test.
  3. [SOLVED] Certain VMs from a cluster cannot be backed up and managed

    I do tracing too, but tracing freeze about time when scheduled backup started backup VM syslog message backup log So can be some relation with services started in this time
  4. [SOLVED] Promox 6: problem with noVNC - failed to connect to server

    I am upgrade to 6 using https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0. All packages are sucessfully upgraded to Buster and Proxmox 6 packages upgraded too without problem. NoVNC console is working if I newly start VMs, but after some time of running VMs appear the problem. So it doesnt...
  5. [SOLVED] Promox 6: problem with noVNC - failed to connect to server

    After yesterday backup many VMs error like this: VMs are running, but don't work noVNC console and backup. It look's like problem with qemu-server sockets, may be.
  6. [SOLVED] Promox 6: problem with noVNC - failed to connect to server

    I have some VM on LVM, some on LVM-thin. On both is this behaviour. Last backup was correctly on one VM which hasn't function with noVNC, but other VM backup with unfunction noVNC was failed.
  7. [SOLVED] Promox 6: problem with noVNC - failed to connect to server

    It looks, that VMs which have problem with noVNC, need more time for showing "Summary" in web interface. Usually is less than 1 second, but if noVNC is no working is more than 3 seconds.
  8. [SOLVED] Promox 6: problem with noVNC - failed to connect to server

    Hello, after upgrade to Promox 6, I have probem with noVNC console from webbrowser (Chrome,Firefox tested). After some time I cannot connect noVNC console to VM with error "failed to connect to server". After shutdown and start of VM everything work ok - for some time. Same problem is on VM...
  9. drbdmanage license change

    So I think, there is no problem include this in main repository of Promox. Thanks.
  10. drbdmanage license change

    I complain on right place. You removed DRBD by changing licence from GPL to another. Now is licence back to GPL and users ask why is not DRBD back in Proxmox. Because is better for administrate, support, actual updates/upgrades etc. Plugin is 3rd party workaround how get DRBD back to Proxmox...
  11. drbdmanage license change

    And this is why we want DRBD back in Promox. Proxmox 5.0 released month ago, no DRBD for it (http://packages.linbit.com/proxmox/dists/) Cannot upgrade, cannot install new one, cannot awaiting guaranted support in future = DRBD is dead in Proxmox
  12. drbdmanage license change

    DRBD manage is back GPL. Do you plan implement back directly into Proxmox ? https://www.linbit.com/en/drbd-manage-faq/
  13. Recommended solution for replace quorum disk

    Ok - thanks for your experience and help
  14. Recommended solution for replace quorum disk

    Thanks for reply I have 2node cluster with qdisk. If I change qdisk on first node to new and on secondary still connected old qdisk, I have shortly two different quorum data for cluster until I change secondary node. It isn't problem ?

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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!