Hey PF Users,
Our environment is PF 12.1 on Debian 11. It is in our lab. Our production
is still on 11.0.
We recently upgraded this lab from 11.0, right through to 12.1. We did
some light testing of our captive portal at each stage to make sure the
basic functions were working properly, and now that we have arrived at 12.1
we found some issues.
Its been a while since we debugged PF, so jumping in after a lot of
changes.
The first error we are dealing with is what looks like some sort of failure
to bind to port 1813.
Jan 11 14:03:15 pf4 radiusd-acct-docker-wrapper[1106167]: Wed Jan 11
14:03:15 2023 : Error: Failed binding to acct address * port 1813 bound to
server packetfence: Address already in use
Yet, we see that there is a localhost binding from process pfacct
pf4:/usr/local/pf/logs# netstat -tunap | grep 1813
udp 0 0 127.0.0.1:1813 0.0.0.0:*
1741/pfacct
It looks like the service endlessly respawns with a similar set of errors
shown in the logs below (removed the Info/Warn lines).
It seems like packetfence somehow interfering with its own radius binding,
or not detecting it properly, as it looks like pfacct is the packetfence
radiusd-acct instance, so its not clear to us what is going on here and why
it is respawning constantly.
Jan 12 18:03:57 pf4 radiusd-acct-docker-wrapper[54467]: Thu Jan 12 18:03:57
2023 : Error: Failed binding to acct address * port 1813 bound to server
packetfence: Address already in use
Jan 12 18:03:57 pf4 radiusd-acct-docker-wrapper[54467]: Thu Jan 12 18:03:57
2023 : Error: /usr/local/pf/raddb/acct.conf[8]: Error binding to port for
0.0.0.0 port 1813
Jan 12 18:07:13 pf4 radiusd-acct-docker-wrapper[5922]: Error: No such
container: radiusd-acct
Jan 12 18:07:13 pf4 radiusd-acct-docker-wrapper[5922]: Error: No such
container: 1
Jan 12 18:07:17 pf4 radiusd-acct-docker-wrapper[5936]: Failed to create
stream fd: No such file or directory
Browsing the journal for other error-level logs after startup, we found
some pfstats errors, that we do not think are related
pfstats.log:Jan 12 18:06:44 pf4 pfstats[1064]: t=2023-01-12T18:06:44-0500
lvl=eror msg="Error while creating statsd client: write udp 127.0.0.1:56358
->127.0.0.1:8125: write: connection refused" pid=1064
pfstats.log:Jan 12 18:06:46 pf4 pfstats[1064]: t=2023-01-12T18:06:46-0500
lvl=eror msg="Seek error on /usr/local/pf/logs/mariadb.log: seek
/usr/local/pf/logs/mariadb.log: invalid argument" pid=1064
pfstats.log:Jan 12 18:06:46 pf4 pfstats[1064]: t=2023-01-12T18:06:46-0500
lvl=eror msg="Error while processing metric config: Could not parse
duration: " pid=1064
pfstats.log:Jan 12 18:07:10 pf4 pfstats[1064]: t=2023-01-12T18:07:10-0500
lvl=eror msg="API error: Proxy Error" pid=1064
cheers,
Ian
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
