Recent content by Aminuxer

Nowtime Proxmox updated to 6.4 But our two smaller clusters working separated - we avoid build one big cluster again. Does exists any news/comments about this bug ? Does it really fixed in 6.3 / 6.4 version ?

I catch long-time login in Debian-11@LXC too. New container was created from downloaded template as unprivileged. systemctl mask systemd-logind solve issue without edit container config; Thank you very much.

Nowtime we switched to SCTP and increase timeouts. Also we setting up sysctl option: net.core.netdev_max_backlog = 50000 Working over SCTP produce more readable and useful logs, we remain with this option's set. We trying stay updated at actual versions too, but not ready install test version...

At node vps1 with sctp: root@vps1:~# corosync-cmapctl -m stats | grep -E "(latency_ave|time_since_token_last_received)" stats.knet.node1.link0.latency_ave (u32) = 0 stats.knet.node2.link0.latency_ave (u32) = 254 stats.knet.node3.link0.latency_ave (u32) = 141 stats.knet.node4.link0.latency_ave...

In progress of recovery and try understanding issue we perform this steps: 0. Check errors on switch ports and option like storm control - this correct; 1. disable encryption for traffic analyze; crypto_cipher: none crypto_hash: none and found this; Sep 21 10:20:32 vps4 corosync[9641]: [TOTEM...

Flood can appear after restart corosync/pve-cluster random time delay, even 2-3 days after restart. No. We have before 22 nodes in cluster, and after stop corosync and repeated restarts one-by-one some split-brains exists, some nodes view only self - no quorum and blocked activity. But when we...

1. Yes, we try stop pve-cluster and pkill pmxcfs. This stop flood only for short time; After restart service some times later flood appear again. In normal time logs not contain retransmits; Retransmits appear only under storm or shaper overload. We continue diagnostics and try understand of...

I avoid touch /etc/pve/corosync.conf. But at one node with problems i stopped corosync, enable debug in /etc/corosync/corosync.conf and start corosync again. I collect logs from journalctl -f and attach this. Some interesting logs: Sep 17 11:12:59 vps4 corosync[24235]: [KNET ] link...

No, nic was not saturated or overloaded before. Some nodes transmit up to 80 Mbps (maximum) of traffic - it so far from 1G link saturation/ When storm occur we exhaust only routing hardware and links; Only apply iptables script restrict flood level and allow continue work and resurvive...

corosync in status active (running) cluster splitted; Total votes is 1 or 5 on nodes, not 22 as usually; Some nodes have 13 votes and stay quorumed; pvecm status answered with lag; servive pve-cluster at nodes in status active / running; but in status of some nodes present rows like this: Sep...

Nowday we catch udp-impact again; I simple remove some old VMs, this removed correctly without problems; and after 30-40 minutes we catch udp-impact spontaneously; I apply OUTPUT hashlimit rules for supress udp-flood from corosync at each node in cluster: iptables -P OUTPUT ACCEPT iptables...

Does inter-vlan routing enable on router for corresponding vlan's ? Check firewall on border / gateway or similar security solution ? Try install : - tcpdump on proxmox node (NOT IN VM !!) - wireshark on workstation Catch some traffic by tcpdump at node with problem VM/CT. Copy pcap-file to...

I can't reproduce this bug; I catch this twice, but without correlations to any manipulations. I try tune OUTPUT firewall; Thank you for help;

At some nodes we don't install this updates: bind9-host dnsutils libbind9-161 libdns-export1104 libdns1104 libirs161 libisc-export1100 libisc1100 libisccc161 libisccfg163 liblwres161 libproxmox-acme-perl libproxmox-backup-qemu0 libpve-common-perl libpve-guest-common-perl libzmq5...

Yes, we have split too. We stop corosync at all nodes, and run again one-by-one consequently with 2 seconds pause before run on next node. After this cluster restore quorum correctly. But we badly surprise too many UDP-flood traffic - we realy have some nodes in flood tsunami. At early version...