Dear PacketFence Community, On a cluster with two nodes and an arbitrator, I upgraded PacketFence from version 13.2 to 14.0.
Following the procedures provided for clusters documented in the manuals, I started the installation process using the script /usr/local/pf/addons/ upgrade/do-upgrade.sh, choosing to perform operating system upgrades as well. I immediately encountered an initial problem with the netdata dependency (I had redone the same procedure in late September and everything had gone smoothly), which, probably due to a recent RPM update on the EPEL repository, causes packetfence to be uninstalled without a reported error. Not giving up, I manually installed the packetfence 14 RPM having first taken care to uninstall netdata, put the configuration files back in and fixed the permissions and re-enabled the pervised systemd target for the cluster. All services restarted without errors and it would appear that the systems are fully operational, I noticed, however, that the ntlm-auth-api service was only active on one node in the cluster. I realized that with the upgrade the domain.conf file had been modified in which the Active Directory domain section name prefix the hostname of the first upgraded node (and from which I did the sync with the command /usr/local/pf/ bin/cluster/sync) had been altered and this was causing only on that node the service had started and the domain was visible in the GUI. Upon investigating, I saw that the same fact was present in the old test VMs that had been updated with the procedure and had had no problems. To solve this I duplicated the domain section in the domain.conf file with the same data except for the prefix in which I changed the hostname to that of the node not included but present in the cluster. Having done this, on the node where it was needed, I sequentially executed the commands: /usr/local/pf/bin/pfcmd configreload hard /usr/local/pf/bin/pfcmd service ntlm-auth-api updatesystemd and did the reboot. I resynchronized the nodes and also did the same on the node that had the service active. Have you also experienced the same problems recently? Is the procedure I followed correct? Best regards _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
