Search results

Hello There are not set quotas on rpool or rpool/data Iam running proxmox VE 6.3-6, details bellow Iam planning upgrade to 6.4-x at friday, but i dont expect it to fix this problem.

Hello, we are having problem with host replication. The host have 16GB disk, which is about 25% full. But when replication starts,after 2GB trasnfered it ends with an error cannot receive incremental stream: destination rpool/data/subvol-150-disk-0 space quota exceeded The error is about space...

Some of them do have same problems (problems happens 100% on servers which contain logs about blocked tasks from previous post). And some have even same hardware. Disks are mostly in hotswap front positions, but some of the servers does not have hotswap positions, so its connected internally...

Hi, here are details you asked for. On another servers we have similar issues with blocked tasks with different Samsung disks Samsung_SSD_860_PRO_1TB and Samsung_SSD_860_EVO_1TB About resources, nothing looks unusual...on server with 80%+ RAM and 50-70% CPU wearout there are no errors but...

Hello, we are having problems with proxmox servers, our server sometimes freeze or something and does not work for like 2-10 minutes until he unfreeze and continue work...our monitoring system is reporting these freezes, because the server does not respond to ping. In log we found "INFO: task...

Hello and thank you for response. I compared snapshots on main host and replicated host, both are the same, but new replication already did ran, so its probably pointless to compare it right now, when it works...i try it when it "fails". What do you mean by "compare on both sides with list"?

Hello, we are facing problems with replication. Like once a month, our container replication is doing "full sync" instead of "incremental sync". The container have few hundreds of GB so its really annoying. Why it is doing full sync when initial full sync already happened. Thanks for any advice.

libknet1 1.16-pve1 update fixed problem with nodes not connecting into cluster after restart/network failure Problems with restarting nodes still persists.

knet 1.16 slightly improved stability of the cluster New info - we have restarted 1 node, but another 3 nodes fall down and restarted...on all 3 nodes, i found (around time of the restart - 12:57) some watchdog messages. Is it possible, that watchdog is causing some panic and restarting the...

We are probably going to wait until knet update is released in proxmox repositories and give it a try. Maybe it can help the situation. For info - we have nodes in 3 different cities and they are connected via VPN.

Why we can not have nodes in multiple subnets, could you please refer us to some relevant documentation? We understand, that corosync problems (cluster falling apart) can be caused by multiple subnets, but is it possible, that our present problem (ethernet adapter fails) is caused by multiple...

Hello, we have switched to sctp and set token to 10000, because the cluster was all the time falling apart...few times a day. We found this fix on forum and after applying to our cluster, it fixed our problem and cluster now keeps together...

Hello, we are facing pretty curios troubles in Proxmox cluster. When we restart node or corosing on some host (systemctl restart corosync), then on some other nodes ethernet adapter crashes and does not recover himself. Yesterday we performed a test - we restarted server "backup" and in few...

Hello, unfortunatelly, we are facing problem again. Today morning the node started making mess and eventually restarted, after that, he did not connected to the cluster, even after manually restarting corosync on all nodes. The problem started at 07:28 and continued until the node restarted at...

Thank you, now i understand the system about two corosync.conf files and how to edit. Appreciate it.

So, i changed names to IP addresses and ringnumber to linknumber. Everything now works perfect. Node connects to the cluster in a moment. Opening /etc/pve/corosync.conf still shows the error message. [ Error reading lock file /etc/pve/.corosync.conf.swp: Not enough data read ] Is it a problem...

Hello, we had a long time issues with cluster stability, the cluster was falling apart few times a week. We found this thread on forum, post #5 https://forum.proxmox.com/threads/a-lot-of-cluster-fails-after-upgrade-5-4-to-6-0-4.56425/post-260570 So we set knet_transport to sctp and token to...

Hello, iam facing an issue with cluster/corosync. If one node in cluster is unavailable for like 30 minutes, because of lost internet connection, HW maintenance or something else, the node wont rejoin cluster after starting/connecting. The solution i found is to restart corosync on all nodes...

Yes, Windows was updated (but some of the windows virtuals was not able to proceed the update because the virtual died when updating) and VirtIO drivers installed. There was bunch of BSOD IDs, almost every time different one. But as i said, after installing pve-kernel-5.4 and restarting nodes...

Hello there. Past 3 days we have hard times with Windows 10 virtual machines. We are runnich cluster with 8 nodes, eveything is up to date and the problem occurs on every node. BSOD is showing all the time, sometimes when booting, sometimes after few minutes of fresh started VM. I will be...