Search results

Yes, you are correct. But why Proxmox would want to publish the lib without the program, Maybe it will integrate into the existing backup feature.

Yes I saw that, but I'll wait for the documentation to get updated and other users to report any possible bugs :) But it is an extremely interesting and long-awaited feature on backups. It will eliminate the need to have a third party backup solutions. To be honest, having to take a full backup...

Why can't we install it? It is available for update.

I also have this issue pve-cluster: 6.1-8 ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 773525 max locked memory...

I also had this issue on PVE 6.2 I realized it happens only on Windows 2016 and not in 2019 and only when I have my CPU Type to "Host" and try to distribute the cores among more than one CPU Socket. For example, I had this setting on one of my machines: CPU Type: Host Socket: 2 Cores: 3 total...

Thanks for your response. The cluster was working fine before that. but we couldn't add that node to the cluster yet, as the cluster has been acting weird ever since. We had a reboot and corosync hung the next day without us touching anything. We 've been working with your support to find the...

I'm still trying to figure out the issue, even though the business is at risk, but I don't want to give up Proxmox so easily, but I might have to. regarding multicast, It is said that proxmox 6 and corosync 3 don't use multicast anymore, so that possibility is out. I've told that corosync is...

We also have the same issue with 15 nodes. We were adding the 16th node and suddenly all 15 nodes reboot themself. Since they were also running ceph, we had a massive data corruption. Imagine the disaster. Still I don't understand how HA works, it supposed to protect the cluster from failing by...

Last night we tried to add a new node to the cluster, it stuck on joining showing the below messages: can't create shared ssh key database '/etc/pve/priv/authorized_keys' (re)generate node files generate new node certificate unable to create directory '/etc/pve/priv' - Permission denied We...

Anyone please?

Hi I have 15 nodes running proxmox VE 6 and CEPH. Recently we've been experiencing unexpected reboot in one or two nodes and logs showed that their corosync couldn't communicate with each other, therefore the node decided to fence itself and do a reboot automatically. Even though we had two...

Both private and public, we didn't have any issue on ceph eversince, The issue is on Corosync which is on 10GB networks

Thanks for your response. We have 2 x 100GB NIC for ceph with separated pair of switches The thing is we cannot find any bottleneck in the entire setup, no high CPU load on the switches, no very high traffic on the ports. So it 's really a mystery for me. And yes I know its an old thread, but I...

Hi guys I'm having the same issue, on my Proxmox 6 and corosync 3 Almost all of nodes are throwing this error "corosync[2175]: [TOTEM ] Retransmit List " Today morning one of them got unresponsive after many of this and rebootet it self. I see that libknet1 is upgraded to libknet1: 1.15-pve1...

Thank you all for the helpful tips. I believe mulitcases are gone in Proxmox 6, however we have a 15 node cluster running on Proxmox 6 and corosync 3, but we are having these "corosync [TOTEM ] Retransmit List: XXXX " all over our nodes. any idea what it could be ? each node is connected to the...

I have the same issue. and the service file exists at this path, what should I do remove it? /etc/systemd/system/ceph-mon.target.wants

If the nodes some got failed and is not online anymore, how can we do this? I have done ceph mon remove NODEID and then remove it from /etc/ceph/ceph.conf, but as you mentioned it is still in the GUI as Uknown

Hi We've had these issues that one node caused the whole cluster nodes to get rebooted. We've been advised to upgrade to corosync 3 to get rid of multicasts and the issues it might bring it with it. We have successfully upgraded all 14 nodes to corosync 3. And now I've been started to upgrade...

We have now upgraded the to Corosync version 3, so, fortunately, no more multi-tasks. Surprisingly, today while I was adding a new node to the cluster, the node that previously made the whole cluster to reboot (mentioned in this post) got rebooted automated. While looking at the logs I found...

This is still happening and it is actually defeats the whole purpose of having Live migration. 2020-01-29 18:28:31 ERROR: tunnel replied 'ERR: resume failed - VM 180 qmp command 'query-status' failed - client closed connection' to command 'resume 180' 2020-01-29 18:28:40 ERROR: migration...