Yes, I did systemctl set-default packetfence-cluster
Before performing these next steps on the new cluster. systemctl stop packetfence-mariadb /usr/local/pf/bin/pfcmd generatemariadbconfig /usr/local/pf/sbin/pf-mariadb --force-new-cluster I am going to wipe the 4 servers and retry again from the beginning to create a cluster as stated in the cluster guide. I did the same <systemctl set-default packetfence-cluster> on the populated single installation when I changed it over to a cluster. It ran fine besides the issue with iptables. I had rebooted each server without issue while all three were in the cluster. NOTE: I reverted the first server back to a single installation to a point in time before I started to reconfigure and it has been humming along as it did. ________________________________ From: Ludovic Zammit <lzam...@inverse.ca> Sent: Friday, January 15, 2021 7:43 AM To: packetfence-users@lists.sourceforge.net <packetfence-users@lists.sourceforge.net> Cc: Chuck Gentry <gen...@torc.ai> Subject: Re: [PacketFence-users] Issue with iptables and cllustering Hello chuck, Did you change the target of the system back to cluster? https://github.com/inverse-inc/packetfence/blob/devel/docs/PacketFence_Upgrade_Guide.asciidoc#rebooting-after-services-have-been-stopped systemctl set-default packetfence-cluster.target Thanks, Ludovic Zammit lzam...@inverse.ca<mailto:lzam...@inverse.ca> :: +1.514.447.4918 (x145) :: www.inverse.ca<http://www.inverse.ca> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence (http://packetfence.org) On Jan 14, 2021, at 1:06 PM, Chuck Gentry via PacketFence-users <packetfence-users@lists.sourceforge.net<mailto:packetfence-users@lists.sourceforge.net>> wrote: So this was a cluster of three. I decided to revert it back to a single server. I will say that I setup the cluster from an already in use single installation. Is that an issue? It pulled all of the data from the first and had no issue besides the iptables issue. I also decided to do a cluster from a blank slate following the instructions from the cluster guide. I ran into an issue with the first server where you get to the point of running /usr/local/pf/sbin/pf-mariadb --force-new-cluster When running this, the DB does not run on the 127.0.0.1 address even though setting the config files from the guide. Since it does not run on local, I cannot continue. Thank you for your response. I was out for a while. ________________________________ From: Durand fabrice via PacketFence-users <packetfence-users@lists.sourceforge.net<mailto:packetfence-users@lists.sourceforge.net>> Sent: Friday, January 8, 2021 9:33 PM To: packetfence-users@lists.sourceforge.net<mailto:packetfence-users@lists.sourceforge.net> <packetfence-users@lists.sourceforge.net<mailto:packetfence-users@lists.sourceforge.net>> Cc: Durand fabrice <fdur...@inverse.ca<mailto:fdur...@inverse.ca>> Subject: Re: [PacketFence-users] Issue with iptables and cllustering Hello Chuck, is it a cluster of 3 ? Because the line 313 refer to @ha_ints which is used for a cluster of 2 (old cluster config). Did you defined ha interfaces in pf.conf ? Regards Fabrice Le 21-01-04 à 09 h 14, Chuck Gentry via PacketFence-users a écrit : Every since I have configured a cluster, I am unable to start the iptables module. Error that I am receiving in the journal. Can't locate object method "STORE" via package "pfconfig::cached_array" at /usr/local/pf/lib/pf/iptables.pm line 313. (pf::iptables::generate_filter_if_src_to_chain) PF version 10.2.0, ZEN deployment Things to note, I have 3 VLAN interfaces configured, type: other, portal, registration. I am not using any of these interfaces at the moment. I was just playing around with them. They are in the cluster.conf Thank you in advance. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net<mailto:PacketFence-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/packetfence-users CAUTION: This email originated from outside of TORC's email system. DO NOT click links or open attachments unless you recognize the sender and know the content is safe. Email is NOT a secure means of communication. Handle potentially sensitive information with care. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net<mailto:PacketFence-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/packetfence-users CAUTION: This email originated from outside of TORC's email system. DO NOT click links or open attachments unless you recognize the sender and know the content is safe. Email is NOT a secure means of communication. Handle potentially sensitive information with care. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users