Hi Jake,This shouldn't have happened as pf.conf values override the ones in pf.conf.defaults.
Can you post your broken pf.conf, its likely just that the db host config is misplaced.
Otherwise you'll have to change pf.conf.defaults every time you upgrade because it will get overwritten.
Cheers ! - Julien
-------- Forwarded Message -------- Subject: [PacketFence-users] Possible bug: Clustering with PF6.3.0 Date: Fri, 21 Oct 2016 03:19:12 +0000 From: Sallee, Jake <[email protected]> Reply-To: [email protected] To: packetfence <[email protected]> I am not 100% sure of this but there may be a bug concerning clustering in PF6.3.0. The clustering guide says to change the database section in the pf.conf file to include "host=127.0.0.1". However for some reason when I am trying to start the PF services I get an error about the user pf is not able to connect using user pf@localhost. I searched everywhere I could and stumbled across the host entry in the pf.conf.defaults file. It was set to localhost, when I changed it to "127.0.0.1" the error went away. Can anyone reproduce this? Jake Sallee Godfather of Bandwidth System Engineer University of Mary Hardin-Baylor WWW.UMHB.EDU 900 College St. Belton, Texas 76513 Fone: 254-295-4658 Phax: 254-295-4221 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org!http://sdm.link/slashdot _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
