While trying to troubleshoot some radius CoA issues, I saw a lot of errors
in the /usr/local/pf/logs/radius-acct.log file:
Dec 16 17:49:00 serv01 radiusd-acct-docker-wrapper[231160]: Sat Dec 16
17:49:00 2023 : Error: Failed binding to acct address * port 1813 bound to
server packetfence: Address already in use
Dec 16 17:49:00 serv01 radiusd-acct-docker-wrapper[231160]: Sat Dec 16
17:49:00 2023 : Error: /usr/local/pf/raddb/acct.conf[8]: Error binding to
port for 0.0.0.0 port 1813
Netstat shows docker proxy hogging the port:
root@serv01:/usr/local/pf/logs# netstat -tulpn | grep 1813
udp 0 0 192.168.1.8:1813 0.0.0.0:*
3307/docker-proxy
And "docker ps" shows the culprit to be pfacct:
root@serv01:/usr/local/pf/logs# docker ps | grep 1813
2ef25c5badfc packetfence/pfacct:maintenance-13-0
"/bin/sh -c /usr/loc…" 5 minutes ago Up 5 minutes
192.168.1.8:1813->1813/udp,
0.0.0.0:2056->2056/udp, :::2056->2056/udp
pfacct
Of course, this now eliminates the ability to live tail the
/usr/local/pf/logs/radius-acct.log file, since nothing will be written to
the log when you disable the radiusd-acct service. So curious if this is a
bug or if I somehow unknowingly borked a fresh PF install, and whether
there's a workaround.
Mike
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
