Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-07 Thread Christian McDonald via PacketFence-users
Seems that I had my nose on a bug. https://github.com/inverse-inc/packetfence/issues/5667 /closing Thanks all! On Tue, Jul 7, 2020 at 12:16 PM Christian McDonald wrote: > I've also discovered what appears to be an issue in haproxy-admin.conf > > https://pastebin.com/GpFQCtJD > > This line is

Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-07 Thread Christian McDonald via PacketFence-users
The only obvious issue I see in packetfence.log related to haproxy-admin is: Jul 7 11:47:08 pf1 packetfence: -e(6841) WARN: Use of uninitialized value $portal_preview_ip in concatenation (.) or string at /usr/local/pf/lib/pf/services/manager/haproxy_admin.pm line 219. (pf::services::manager::hap

Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-07 Thread Christian McDonald via PacketFence-users
Still getting the 'could not write namespace ... L2 cache' errors. On Tue, Jul 7, 2020 at 7:49 AM Nicolas Quiniou-Briand via PacketFence-users wrote: > If I was you, I will: > - break the `--force-new-cluster` command > - completely stop any MariaDB service > - restart at this step: > > #v+ > sy

Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-07 Thread Christian McDonald via PacketFence-users
Seems that the galera side is operational and replicating...I see all three nodes in incoming_addresses and operational status is 'synced' on all three nodes too. keepalive seems to be working fine too. Only problem is that haproxy-admin isn't starting on the primary node. https://pastebin.com/Vs

Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-07 Thread Christian McDonald via PacketFence-users
I've also discovered what appears to be an issue in haproxy-admin.conf https://pastebin.com/GpFQCtJD This line is missing an argument, which is preventing haproxy-admin from starting. http-request set-header Host On Tue, Jul 7, 2020 at 11:50 AM Christian McDonald wrote: > The only obvious iss

Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-07 Thread Nicolas Quiniou-Briand via PacketFence-users
If I was you, I will: - break the `--force-new-cluster` command - completely stop any MariaDB service - restart at this step: #v+ systemctl stop packetfence-mariadb /usr/local/pf/bin/pfcmd generatemariadbconfig /usr/local/pf/sbin/pf-mariadb --force-new-cluster #v- -- Nicolas Quiniou-Briand n...@i

Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-06 Thread Christian McDonald via PacketFence-users
Here is my setup: 1. 3 x CentOS 7 (fully up-to-date) w/ SELinux *disabled *+ firewalld *disabled *and *masked *+ IPv6 *disabled *(via sysctl.conf and /etc/defaults/grub ipv6.disable=1). I also have net.ipv4.ip_nonlocal_bind = 1 in sysctl.conf. Xtrabackup is also installed. Each box is

Re: [PacketFence-users] Clustering Guide Sanity Check

2020-07-06 Thread Durand fabrice via PacketFence-users
Hello Christian, in which step do you have an issue ? Regards Fabrice Le 20-07-06 à 18 h 49, Christian McDonald via PacketFence-users a écrit : Greetings, I've been pulling my hair out trying to get a 3-node PF Cluster running. Has anyone recently followed the clustering guide running the

[PacketFence-users] Clustering Guide Sanity Check

2020-07-06 Thread Christian McDonald via PacketFence-users
Greetings, I've been pulling my hair out trying to get a 3-node PF Cluster running. Has anyone recently followed the clustering guide running the latest PF version? I'm usually pretty good at following instructions, but there is something very broken about the clustering guide. Anybody have any