Hi all, We have recently started to experience an issue on 13.0 in which the radiusd-auth goes down and we cannot start it via the GUI. Several attempts are needed until we are able to restart it.
At the time the service goes down we see the following: Jul 18 05:31:54 VPPACKETFENCE01 pfacct-docker-wrapper[8697]: t=2024-07-18T05:31:54+0200 lvl=dbug msg="Pinged DB" pid=7 ... Jul 18 05:32:35 VPPACKETFENCE01 systemd[1]: packetfence-radiusd-auth.service: Watchdog timeout (limit 10s)! Jul 18 05:32:35 VPPACKETFENCE01 systemd[1]: packetfence-radiusd-auth.service: Killing process 103415 (radiusd) with signal SIGABRT. Don't really know if there is any relation between the pfacct and packetfence-radiusd-auth.service. We found that by disabling on the GUI the pfacct service we could start radiusd-auth. Could anyone provide some guidelines for better troubleshooting or let know if experiencing that same issue ? Regards Gonçalo Contente Senior Network & Security engineer Devoteam goncalo.conte...@devoteam.com [image: Infinite Hyper Automation] [image: Devoteam at Linkedin] <https://www.linkedin.com/company/devoteam> [image: Devoteam at Twitter] <https://twitter.com/devoteam>
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
