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)...
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...
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...
Hello Fabian,
I got a ticket yes but... How can I test if it is valid?
{
"data": {
"CSRFPreventionToken": "62BBFFEF:S5YlV5THZubNj6*****",
"ticket": "****",
"username": "root@pam"
}
}
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:~#...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.