Search results

The block was at Cloudflare. By default, application port 8443 is blocked. Thanks for you help

We have an palo FW and cloudflare vpn, from my laptop don't work but from server inside our network it is works fine. I close the issue. The probleme is FW configuration Thx and sorry for the the wrong issue

Hello, I want to try proxmox datacenter manager and I have installed the stable version on vm proxmox (Ve 9) with the latest ISO. No problem during the installation. I can t access to web interface, I have an TLS error. I test with different navigator (firefox chrome and safari). Also I test...

Yes, the next step is to separate link for corosync but at this time is not possible

I fixed my problem with this parameter in corosync: token_retransmit: 200 on first DC 17/17 nodes and senconde DC 16/16 nodes Thanks for your help

all nodes are the same version 6.3.3 kern: 5.4.78-2-pve ssh ok between all nodes date synchronise with time-sync and I checked the date In another data center I have the exact same problem. The latency is a little better I can have 15 nodes out of 16. But as soon as I try to add a 16 here is...

Hi the output of all nodes: 10.123.1.188 : unicast, xmt/rcv/%loss = 9014/9005/0%, min/avg/max/std-dev = 0.067/0.176/22.110/0.755 10.123.1.188 : multicast, xmt/rcv/%loss = 9014/7584/15% (seq>=1471 0%), min/avg/max/std-dev = 0.068/18.251/1715.497/173.905 10.123.1.179 : unicast, xmt/rcv/%loss =...

ok, thanks for the answer i didn't understand how omping works. First only 3 nodes omping -c 10000 -i 0.001 -F -q 10.123.1.179 10.123.1.132 10.123.1.188 10.123.1.132 : waiting for response msg 10.123.1.188 : waiting for response msg 10.123.1.132 : waiting for response msg 10.123.1.188 ...

omping don't respond root@xinfvirtrc15b:~# omping -c 10000 -i 0.001 -F -q 10.123.1.132 10.123.1.188 10.123.1.179 10.123.1.188 : waiting for response msg 10.123.1.179 : waiting for response msg 10.123.1.188 : waiting for response msg 10.123.1.179 : waiting for response msg 10.123.1.188 : waiting...

mtu setting is 1500. You can see in the log that udp packet never exceed 1397

I haven't made any configuration changes yet, just activated debug mode and reproduced the problem. addition of host 4 But in the log I do not see any indication that could help me with the issue.

Hi, thanks for your reply, my corosync connection: the same interfaces that vm storage/gui, only 1 link in 1G. cat /etc/network/interfaces: auto vmbr0 iface vmbr0 inet static address 10.123.1.83/24 gateway 10.123.1.254 bridge-ports eno1.470 bridge-stp off bridge-fd 0...

Before I had a cluster of 13 nodes. I added 3 other nodes and within 5 minutes I lost the whole cluster. After restarting corosync 1 by 1 but when I start a 15th node I have this message: corosync[29232]: [TOTEM ] Token has not been received in 380 ms then after a few minutes the cluster...