Search results

Hi guys! Today I noticed a problem with displaying the list of disks. I got error rbd error: rbd: listing images failed: (2) No such file or directory (500) ceph -s: cluster: id: 77161c77-31b0-4f07-a29d-d65f7bd6e18e health: HEALTH_OK services: mon: 3 daemons, quorum...

Dont forget about quorum, 3 nodes in cluster. This way you can create 1 virtual node, after adding new node delete VM

@Volker Lieder I migrated VM's from the inaccessible node ,but you have to know that process stop your VM's You need to login in working node and move config file of VM mv /etc/pve/nodes/node05/qemu-server/VM_ID.conf /etc/pve/nodes/node04/qemu-server/ And your VM will be migrated

@fiona OMG! It was realy my mistake, I tried editing wrong file I'm sorry for disturbing

I've replaced /etc/corosync/corosync.conf.bak to /etc/corosync/corosync.conf on node 1, but without result. Then I've tried reboot failed node and nothing changed. Via web I can access to node but I can't migrate VM's from this node, telling me that cluster is not quorate

Then I tried restart corosync on my node 2 and node is down. There's output root@ala924bf02pve12:~# journalctl -u corosync | tail -25 Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1) Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]...

@fiona my previous success was on second test cluster. But I tried to repeat steps on my production, and there I got a trouble. I edited corosync.conf file, but changes didn't applied on nodes. There is output when I already changed corosync.conf on node 1 Sep 01 11:14:07 ala220pve01 systemd[1]...

Thank you. It was my mistake bcause I forgot to change version. I reset all my changes and then tried to change step-by-step by documentation and everything works fine

I edited .conf file without copying to temp and then replacing original file. Then I tried to edit config_version in original file, and have no result.

Hi guys! I stucked and need help. I have cluster (8 nodes) and tried add vLAN for corosync. When I modified corosync.conf file on non-master node, new file not modified on another nodes, but when I modified corosync.conf on master node, and restarted corosync service system rewrite file (delete...

No, I use 2 link 10G in bond (LACP enabled) this is my network configuration

What do you mean "separate link" for corosync? Because I use separate vLAN's (cluster and management) And could you tell me more details about HA rules?

Thank you for your response! 1) 2) No 3) Yes

Hi! In upgrade process to v7.2, looks like it is corrupted. Because node gone in offline mod and on display I can see block device error (screenshot added) But after rebooting node starts normally. I dont know how does it affect on Proxmox

Hi guys! I faced a problem when adding a node to the cluster. The cluster consists of 7 nodes, and when adding a new node, a failure occurred, most likely corosync, and all cluster virtual machines were turned off. PVE version of all nodes in cluster 7.1-10, PVE version of new node 7.2-4...

Hello everyone! I'm trying to setup mail notifications of backup process. I attached main.cf. I have Exchange as mail server withous tls. Am I right that I have to disable all tls parameters? When I'm trying to send test mail I get error root@pve01:~# echo "Test mail from postfix" | mail -s...

Hello guys! I have manually deployed Proxmox (Installing Debian+Proxmox) and set postfix 'Local only'. At the moment I would like to receive e-mail notifications about backups. How could I setup this? Or I need to do that on PBS?

It was expected that the server would not boot after a reboot. Since I had a free node in the cluster, I decided to migrate all VM's to another node and reinstall the OS.

I tried this, but unfortunately output root@pve04:~# apt list --installed | grep kernel WARNING: apt does not have a stable CLI interface. Use with caution in scripts. pve-kernel-5.13/stable,now 7.1-9 all [installed,automatic] pve-kernel-5.4.103-1-pve/now 5.4.103-1 amd64 [installed,local]...

Hi guys! I'm trapped... It was my first node with Proxmox and I incorrect sized boot partition to 256MB. I forgot about it and starting to upgrade to Proxmox 7, which one was broken. At the moment host is switched on, but boot partition used 100% space. and pve-kernel-5.13 can not install and...