Recent content by DamienB

Hello, Unfortunately I come back again for the same reason: Since 11 hours this morning, I got this: I checked the corosync and pveproxy services, and the syslog but this time no issue/warning detected. $ corosync-cfgtool -n Local node ID 5, transport knet nodeid: 1 reachable LINK: 0...

Today, I tried again to connect in the web UI of px4-pra and ... it works. This situation is frustrated. It give me the feelings that I could got the same problem and I wouldn't know how to correct it. From the log I no longer have the error message "The proxy detected a missing client...

I found something: The IP used by PX4-pra in /etc/pve/.members was different than the other server(wrong subnet). I change this by updating /etc/hosts and I restarted the host. For now it works but I still cannot loggin the web UI of PX4-pra.

Ooops. My bad! I just correct my latest post(192.168.199.15 192.168.199.14). Yes the IP is the same in /etc/pve/corosync.conf After restarting the corosync service: ● corosync.service - Corosync Cluster Engine Loaded: loaded (/lib/systemd/system/corosync.service; enabled; preset: enabled)...

Again, thanks for helping me. $ corosync-cfgtool -n Local node ID 5, transport knet nodeid: 1 reachable LINK: 0 udp (192.168.199.14->192.168.199.11) enabled connected mtu: 1397 nodeid: 2 reachable LINK: 0 udp (192.168.199.14->192.168.199.13) enabled connected mtu: 1397 nodeid: 4...

When I try to log in the px-pra web UI, I got this log message(pveproxy.service): proxy detected vanished client connection

Thanks for replying. Currently I have a good latence but nothing change in the web UI: $ ping -c 200 -i 0.2 px1 64 bytes from 192.168.199.11: icmp_seq=194 ttl=64 time=1.74 ms 64 bytes from 192.168.199.11: icmp_seq=195 ttl=64 time=1.89 ms 64 bytes from 192.168.199.11: icmp_seq=196 ttl=64...

From syslog: $ grep -i px4-pra syslog|grep -v postfix 2024-09-05T08:20:58.121241+00:00 px4-pra pmxcfs[1584]: [dcdb] notice: members: 1/1752, 2/2007, 4/1993, 5/1584 2024-09-05T08:20:58.121512+00:00 px4-pra pmxcfs[1584]: [dcdb]...

The corosync config file: logging { debug: off to_syslog: yes } nodelist { node { name: px1...

Hello everyone, Thanks by advance for reading my post. I have a cluster of 4 hosts(pve v8.2.3): PX1|2|3 in OVH DC( Gravelines) PX4-PRA in OVH DC (Roubaix) The last one is seen in the web UI as degraded: I was looking for the problem when I saw an error in corosync service: [KNET ] host...

Thank you for your help Fabian. You right I miss the correct value 'GET'. Did anyone succeeded to integrate pbs in prometheus ?

Hello Fabian, I got a ticket yes but... How can I test if it is valid? { "data": { "CSRFPreventionToken": "62BBFFEF:S5YlV5THZubNj6*****", "ticket": "****", "username": "root@pam" } }

Log details: * Trying 176.31.0.227:8007... * TCP_NODELAY set * Connected to pbs.dawan.fr (176.31.0.227) port 8007 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs *...

Hello, I'm using a PBS(2.1-5) for more than year and I try to integrate it to my supervision(prometheus) via the blackbox exporter(http's probe). To do this I have to interact with the API and here is the problem: the documentation is very poor about details. Here is my script to try to...

Hello, I have upgrade my nodes 2 weeks ago and today, after rebooting, one of my 3 nodes have a serious problem. The VMs can't reboot because they disappeared of the storage. I'm using DRBD. First, I notice that the volumes wasn't sync. I had this message on all of the nodes. root@px3:~#...