Hello Hubert, How did you upgrade ? If you did not use the /usr/local/pf/addons/upgrade/do-upgrade.sh
You will need to run those scripts: root@packetfence:/usr/local/pf# ls -ltr /usr/local/pf/addons/upgrade/to-12* -rwxr-xr-x 1 pf pf 1576 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.2-firewallsso.pl -rwxr-xr-x 1 pf pf 1836 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.1-move-rolebyname-to-vpnbyname-fortigate.pl lrwxrwxrwx 1 root root 34 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.1-move-logos-to-profile-templates.pl -> move-logos-to-profile-templates.pl -rwxr-xr-x 1 pf pf 3418 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.1-eduroam-migration.pl -rwxr-xr-x 1 pf pf 1888 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.0-use-proxysql.pl -rwxr-xr-x 1 pf pf 2438 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.0-rename-log-files.pl -rwxr-xr-x 1 pf pf 2780 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.0-remove-tenant.pl -rwxr-xr-x 1 pf pf 2655 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-12.0-authentication.pl root@pf21-3:/usr/local/pf# ls -ltr /usr/local/pf/addons/upgrade/to-13* -rwxr-xr-x 1 pf pf 3214 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-13.0-remove-provisioner.pl -rwxr-xr-x 1 pf pf 1845 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-13.0-convert-switch-types.pl -rwxr-xr-x 1 pf pf 3089 Oct 20 13:54 /usr/local/pf/addons/upgrade/to-13.0-authentication-conf.pl My guess is that the problem comes from of the tenant config. Run all those scripts and restart packetfence: /usr/local/pf/bin/pfcmd service pf restart Thanks, Ludovic Zammit Product Support Engineer Principal Lead Cell: +1.613.670.8432 Akamai Technologies - Inverse 145 Broadway Cambridge, MA 02142 Connect with Us: <https://community.akamai.com/> <http://blogs.akamai.com/> <https://twitter.com/akamai> <http://www.facebook.com/AkamaiTechnologies> <http://www.linkedin.com/company/akamai-technologies> <http://www.youtube.com/user/akamaitechnologies?feature=results_main> > On Oct 16, 2023, at 6:07 AM, Hubert Kupper via PacketFence-users > <packetfence-users@lists.sourceforge.net> wrote: > > Hi, > > > after upgrade packetfence 12.0 to 13.0 the radiusd-auth is not starting. > Syslog shows the following message: > > root@packetfence:/var/log# tail syslog > Oct 16 12:02:52 packetfence freeradius[16268]: > /usr/local/pf/raddb/sites-enabled/packetfence[31]: Please verify that the > configuration exists in > /usr/local/pf/raddb/mods-enabled/packetfence-set-tenant-id. > Oct 16 12:02:52 packetfence freeradius[16268]: > /usr/local/pf/raddb/sites-enabled/packetfence[14]: Errors parsing authorize > section. > Oct 16 12:02:52 packetfence systemd[1]: packetfence-radiusd-auth.service: > Control process exited, code=exited, status=1/FAILURE > Oct 16 12:02:52 packetfence systemd[1]: packetfence-radiusd-auth.service: > Failed with result 'exit-code'. > Oct 16 12:02:52 packetfence systemd[1]: Failed to start PacketFence > FreeRADIUS authentication multi-protocol authentication server. > Oct 16 12:02:52 packetfence systemd[1]: packetfence-radiusd-auth.service: > Consumed 3.891s CPU time. > Oct 16 12:02:52 packetfence systemd[1]: packetfence-radiusd-auth.service: > Scheduled restart job, restart counter is at 98. > Oct 16 12:02:52 packetfence systemd[1]: Stopped PacketFence FreeRADIUS > authentication multi-protocol authentication server. > Oct 16 12:02:52 packetfence systemd[1]: packetfence-radiusd-auth.service: > Consumed 3.891s CPU time. > Oct 16 12:02:52 packetfence systemd[1]: Starting PacketFence FreeRADIUS > authentication multi-protocol authentication server... > root@packetfence:/var/log# > > In 12.0 all works fine. > > Regards, Hubert > > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
