Search results

See, it is mostly the network cause my problem. Do you know how to change the corosync network, since the cluster is in use. I am going to add nodes up to 100 nodes. You can see that my Vmware vsan is ok in the same network, So i think proxmox could change if I divide them into 2 vlan.

I have 2 vsan cluster in the same cisco 4506 switch, Vsan is really stable, I think network is ok. May be the problem is the Network problem, I am wondering the different with vsan is : All node is only a 10G trunk port, but vsan is using vlan to separate the client and vsan storage. Is...

Can I disable pve-ha-lrm service in all nodes? But the strange things is that only 2 node reboot but make the whole cluster die. So in your experiments corosync is not good enough to manage 30-40 nodes? Proxmox is really good with ceph in Hyper-converged infrastructure, but not stable enough.

In the Deamon show the same, a lot of ceph osd error message then reboot root@g8kvm02:~# vi /var/log/daemon.log Sep 7 00:12:10 g8kvm02 ceph-osd[2292]: 2020-09-07 00:12:10.885 7fa29b6fa700 -1 osd.8 96815 heartbeat_check: no reply from 10.0.141.37:6810 osd.307 since back 2020-09-07...

Sep 7 00:10:49 g8kvm01 pmxcfs[1635]: [status] notice: cpg_send_message retry 50 Sep 7 00:10:50 g8kvm01 pmxcfs[1635]: [status] notice: cpg_send_message retry 60 Sep 7 00:10:51 g8kvm01 pmxcfs[1635]: [status] notice: cpg_send_message retry 70 Sep 7 00:10:52 g8kvm01 pmxcfs[1635]: [status]...

Other node log: Sep 7 00:02:01 g8kvm01 pvesr[3114968]: trying to acquire cfs lock 'file-replication_cfg' ... Sep 7 00:02:02 g8kvm01 systemd[1]: pvesr.service: Succeeded. Sep 7 00:02:02 g8kvm01 systemd[1]: Started Proxmox VE replication runner. Sep 7 00:03:00 g8kvm01 systemd[1]: Starting...

I had close HA already, but the HA web interface show quorum OK, master g8kvm31 idle, all other node are idle. They told just remove HA groups the HA will stop, does it right? Still the HA problem ? And the reboot log has nothing about the die node info, just told disconnect

My cluster have 38 nodes with ceph, yesterday, I added the 39th node, the hole cluster die!!!! I don't have HA enabled, I think the node should not reboot, but my cluserter has 2 node reboot, and the cluster spit to different cluster quorum, like node 1, 3, 5, 7 , another is 2,4, 6,8...

I had figure out , add pbs to another cluster, then can see the backup file, choose one to restore. It works.

I have 2 cluster, using the same PBS to backup everyday, here is my question: 1. Why only see one snapshot? root@pbsg8:~# proxmox-backup-client snapshots --repository 10.0.142.0:pbs-data-g8...

After reboot the node, everything ok. Thank you !

here you are: root@kvm17:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve) pve-manager: 6.2-11 (running version: 6.2-11/22fb4983) pve-kernel-5.4: 6.2-5 pve-kernel-helper: 6.2-5 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.55-1-pve: 5.4.55-1 pve-kernel-5.3.18-3-pve: 5.3.18-3...

When I choose ZSTD for backup job, it shows below error, but job still can continue, choose LZO, GZIP have no error. Some errors have been encountered: kvm17: Parameter verification failed. (400) compress: value 'zstd' does not have a value in the enumeration '0, 1, gzip, lzo' kvm07...

Thank you ! Slove! Check and found this node is not update !

My cluster has 18 nodes, all update to 6.2-11, but while I backup the vm in node 17, show the following error, other nodes ok! TASK ERROR: could not get storage information for 'pbs-backup-server': can't use storage type 'pbs' for backup What I try: 1. Reboot service: pvedaemon pveproxy...

I'm using the sandisk common usb 3.0 32G u key:oops:. I want to prepare to add/delete node form cluster, in cases to key data save and make a backup cluster to backup data. Is there necessary to backup proxmox ? Like data/config/database ext. And is ceph config need to backup ?

Really thank you! Why I am using a usb key for I can't boot the system for HP DL380 Gen8 in HBA mode can not start with one of the harddisk. I am using EXT3, make swap 0. So I think this could make the write less In my cluster I make over 5 ceph mon, I think if no luck, 2 node die, my...

I don't expect any more except the cluster not reboot just ok. Is it the corosync is work for proxmox cluster data sync ? And corosync is not any connect with HA ? so, if I stop HA, can slove my reboot problem ? Actually, I have two cluster, onther cluster is 18 node with a new model...