Search results

I have only enabled ceph dashboard on our DEV cluster so far to play around with it a bit. Even though I already know the dashboard from plain ceph installations. But I see it very similar to you, I will probably not use ceph dashboard in our production environment together with proxmox.

I just ran into the same prollem. After doing a systemctl reset-failed ceph-mgr@%YOUR-NODE-NAME-HERE%.service i was able to start the managers again I'm on Ceph pacific 16.2.9 & Proxmox 7.3-3

I just ran into the same prollem. After doing a systemctl reset-failed ceph-mgr@%YOUR-NODE-NAME-HERE%.service i was able to start the managers again I'm on Ceph pacific 16.2.9 & Proxmox 7.3-3

The method worked exactly as described without any problems.

Great, thank you! And yes, its a 3X replication :-)

Hi We are running a Ceph cluster with 3 nodes and 2 OSDs per node on SSD drives. One of the nodes has recently been causing problems and both OSDs in this node sporadically report "log_latency_fn slow operation observed for _txc_committed_kv" in the log and the write performance is also poor in...

Sure: Node 1: root@proxmox-c1-n1:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128...

Local version of /etc/corosync/corosync.conf (on all 3 nodes) and /etc/pve/corosync.conf all look exactly the same while I never changed anything manually on the local config files in /etc/corosync/corosync.conf I just moved/copied the modified version of corosync.conf to /etc/pve/corosync.conf...

/etc/hosts on node1: 127.0.0.1 localhost.localdomain localhost 172.30.8.41 proxmox-c1-n1.proxmox.mydomain.com proxmox-c1-n1 pvelocalhost 172.30.8.42 proxmox-c1-n2.proxmox.mydomain.com proxmox-c1-n2 172.30.8.43 proxmox-c1-n3.proxmox.mydomain.com proxmox-c1-n3 10.55.1.1...

I'm trying to seperate the corosync network in our 3 node cluster (Proxmox 5.3-11) as described in https://pve.proxmox.com/wiki/Separate_Cluster_Network After copying the new corosync.conf to /etc/corosync/corosync.conf I'm getting the following error: Mar 19 10:22:57 proxmox-c1-n3...

Ah yeah, got it now. My set request would update an existing CIDR entry inside the the IPset instead of adding a new one.

That worked, thank you Dietmar! So is the documentation wrong or do I just not read it correctly?

I'm trying to add a subnet to an existing IPSet of an existing VM via the API. According to the docs (https://pve.proxmox.com/pve-docs/api-viewer/index.html) the correct command would be: pvesh set /nodes/{node}/qemu/{vmid}/firewall/ipset/{name}/{cidr} But this command doesn't work (node and...