Search results

My understanding of this thread is that there are/were 3 issues: - Corosync issues resolved with updated knetlib - Corosync crashing (segmentation fault) - Intermittent pauses, perhaps specific to bnx2 We manage 7 PVE 6 clusters which are now all stable, except for one that uses bnx2...

I'm not getting core dumps but things are less stable with the latest updates: [root@kvm1 log]# last | grep boot reboot system boot 5.0.21-1-pve Sun Sep 1 20:50 still running reboot system boot 5.0.21-1-pve Sat Aug 31 16:06 still running reboot system boot 5.0.21-1-pve...

It is indeed, many thanks for the quick response!

There appears to be a bug in the validation scripts when adding IPs or subnets to an IPSet. Entering either a single IP (eg 1.1.1.5), a host CIDR (eg 1.1.1.5/32) or a subnet (eg 1.1.1.0/24) results in the validation not allowing one to save the new entry:

kvm2: Aug 30 05:29:00 kvm1 systemd[1]: Starting Proxmox VE replication runner... Aug 30 05:29:01 kvm1 systemd[1]: pvesr.service: Succeeded. Aug 30 05:29:01 kvm1 systemd[1]: Started Proxmox VE replication runner. Aug 30 05:30:00 kvm1 systemd[1]: Starting Proxmox VE replication runner... Aug 30...

We have one cluster in particular where nodes loose quorum and are subsequently fenced. This behaviour was most definitely new since upgrading to PVE 6 but may relate to igb drivers. We upgraded and restarted corosync yesterday and had a repeat of all nodes loosing quorum simultaneously this...

The script above has been updated to work with Ceph 14 (Nautilus). The affected line, for Ceph 12 (Nautilus) was: $AWK '/^[0-9]+\.[0-9a-z]+/ { if($10 == "active+clean") { print $1,$23,$24 ; }; }' | \

Adding a node to an existing cluster results in all existing nodes being fenced and restarting. Also, this was with secauth: off and token: 10000 /etc/corosync/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: kvm7a nodeid: 1 quorum_votes: 1...

Most of our Proxmox clusters utilise Intel 82599ES 10GbE SFP+ NICs where TSO (TCP/IP Segmentation Offloading) works as expected for VMs where their VirtIO NIC then also has TSO enabled. We however have a cluster made up of 3 x Lenovo RD350 servers where Intel 82599ES 10GbE NICs are used for...

Hi, Eric Garver's post details examples on configuring QinQ ports on the OvS side so that the VM simply interacts with untagged packets. This is not something we currently have a requirement for and requires two rules to specifically configure ingress and egress operations for each VM...

And one of the nodes restarted at 13:18, I've uploaded the syslog entries matching 'coro' from all 3 nodes.

I'm also experiencing corosync issues on clusters we've upgraded to PVE 6.0. We tried changing protocol from UDP to SCTP, defining netmtu (which we subsequently discovered to no longer be used in Corosync 3). We've upgraded one cluster to using libknet1_1.10-pve2~test1_amd64.deb but still see...

Probably not without customising the GUI and script you've already edited. OvS does support having the host handling the double tag injection. We however haven't made patches as we treat OvS like any other standard switch. We trunk all or selective VLANs to a few virtual routers and attach...

Hi, We've been PXE booting the ISO for several years, it makes it substantially easier and faster to load equipment. We use the steps detailed in the following forum post and presume that it has Proxmox's blessings as the ISO is pre-prepared to search for the ISO image in the installation...

Everything works as expected, live migration, GUI management, etc... Tested and working in production with untagged (trunks all VLANs), selective trunking or specifying a tag, in which case the OvS port encapsulates all packets received from the VM. This is the same as connecting a firewall or...

Proxmox 6 now includes OvS 2.10, you simply need to patch /usr/share/perl5/PVE/Network.pm as detailed above (modify 3 lines). Thanks for upvoting though!

Thanks Alwin, I don't believe this records the source IP of the user though...

We had a node fence itself as the IPMI reset counter reached zero (Motherboard logs) but we can't locate logging information leading up to this event. Surely corosync or pvecm logs events such as losing quorum, occasional heartbeat messages being lost or discarded? We previously appear to have...

Where can we review Proxmox GUI logins, specifically source IP and user names? This information should Ideally replicate between nodes of a cluster but I can't find log entries on individual nodes either...

Hi Alwin, The 'mon compact on trim' appears to be enabled by default already. I can understand the monitor database growing during rebuild operations but the size of the database went from xx MB to 1600 MB after restarting nodes last week Friday. Cluster is virtually completely idle and mon...