You have two copies of FreeRADIUS installed on the same machine. Don't do that.
I do agree, that is very strange, because this was never intended. The upgrade path lately was like this: FR 3.2.5 —> FR 3.2.6 (git #a69627989) by compiling out of the git repository (make) —> FR 3.2.7 via apt packet manager I also executed "apt autoremove“ after upgrading from FR 3.2.7. When I check the source of the radiusd command, I get: root@id-radiustest1:~# which radiusd /usr/local/sbin/radiusd root@id-radiustest1:~# radiusd -v radiusd: FreeRADIUS Version 3.2.5 (git #67e58e67f), for host x86_64-pc-linux-gnu, built on Jun 21 2024 at 22:22:48 FreeRADIUS Version 3.2.5 Copyright (C) 1999-2023 The FreeRADIUS server project and contributors There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License For more information about these matters, see the file named COPYRIGHT Compared to freeradius: root@id-radiustest1:~# which freeradius /usr/sbin/freeradius dpkg looks like this: root@id-radiustest1:~# dpkg -l | grep radius ii freeradius 3.2.7-1 amd64 high-performance and highly configurable RADIUS server ii freeradius-common 3.2.7-1 all FreeRADIUS common files ii freeradius-config 3.2.7-1 amd64 FreeRADIUS default config files ii freeradius-dbg 3.2.7-1 amd64 debug symbols for the FreeRADIUS packages ii freeradius-dhcp 3.2.7-1 amd64 DHCP module for FreeRADIUS server ii freeradius-freetds 3.2.7-1 amd64 FreeTDS support for FreeRADIUS ii freeradius-krb5 3.2.7-1 amd64 kerberos module for FreeRADIUS server ii freeradius-ldap 3.2.7-1 amd64 LDAP module for FreeRADIUS server ii freeradius-memcached 3.2.7-1 amd64 Memcached module for FreeRADIUS server ii freeradius-mysql 3.2.7-1 amd64 MySQL module for FreeRADIUS server ii freeradius-perl-util 3.2.7-1 amd64 FreeRADIUS Perl utilities ii freeradius-postgresql 3.2.7-1 amd64 PostgreSQL module for FreeRADIUS server ii freeradius-python2 3.2.7-1 amd64 Python2 module for the FreeRADIUS server ii freeradius-python3 3.2.7-1 amd64 Python3 module for the FreeRADIUS server ii freeradius-redis 3.2.7-1 amd64 Redis module for FreeRADIUS server ii freeradius-rest 3.2.7-1 amd64 REST module for FreeRADIUS server ii freeradius-unbound 3.2.7-1 amd64 Unbound module for FreeRADIUS server ii freeradius-unixodbc 3.2.7-1 amd64 unixODBC module for FreeRADIUS server ii freeradius-utils 3.2.7-1 amd64 FreeRADIUS client utilities ii freeradius-yubikey 3.2.7-1 amd64 Yubikey module for FreeRADIUS server ii libfreeradius-dev 3.2.7-1 amd64 FreeRADIUS shared library development files ii libfreeradius3 3.2.7-1 amd64 FreeRADIUS shared library I think this is because I installed it initially by compiling the git sources, correct? I would like to clean this mess up, can I just go ahead and delete the following files under /usr/local/sbin? - checkrad - raddebug - radiusd - radmin - rc.radiusd - raddb root@id-radiustest1:~# ls -la /usr/local/etc/ total 12 drwxr-xr-x 3 root root 4096 Jun 21 2024 . drwxr-xr-x 11 root root 4096 Jun 21 2024 .. drwxr-xr-x 9 freerad freerad 4096 Apr 17 13:51 raddb root@id-radiustest1:~# ls -la /usr/local/sbin/ total 3228 drwxr-xr-x 2 root root 4096 Jun 21 2024 . drwxr-xr-x 11 root root 4096 Jun 21 2024 .. -rwxr-xr-x 1 root root 38414 Jun 21 2024 checkrad -rwxr-xr-x 1 root root 3626 Jun 21 2024 raddebug -rwxr-xr-x 1 root root 2291552 Jun 21 2024 radiusd -rwxr-xr-x 1 root root 944128 Jun 21 2024 radmin -rwxr-xr-x 1 root root 2548 Jun 21 2024 rc.radiusd -rwxr-xr-x 1 root root 4181 Feb 17 2023 unminimize Or what is the best way to have a clean installation again; download the 3.2.5 git repository again and execute „make uninstall“? Regards Dominic
Am 19.04.2025 um 19:44 schrieb Alan DeKok <aland@deployingradius.com>:
On Apr 19, 2025, at 1:26 PM, Dominic Stalder <dominic.stalder@bluewin.ch> wrote:
2. but I also sent the respective output of "radiusd -fxx -l stdout“ in my email before and got the following error instead (see full output below), as recommended in the „freeradius -X“ output:
Failed opening auth address :: port 1812 bound to server default: Address family not supported by protocol /usr/local/etc/raddb/sites-enabled/default[246]: Error binding to port for :: port 1812
That's very odd. But likely explained by the next issue:
_EXIT(1) CALLED src/main/process.c[6325]. Last error was: /usr/local/lib/proto_auth.so: cannot open shared object file: No such file or directory
3. At the same time, I just recognized, that when I started the debug output with "radiusd …“, it shows me output of FR 3.2.5:
root@id-radiustest1:/etc/freeradius/sites-enabled# radiusd -fxx -l stdout FreeRADIUS Version 3.2.5 …
BUT I have FR 3.2.7 in place and started it with „freeradius -fxx -l stdout“ instead and now the correct FR instance is trying to start:
You have two copies of FreeRADIUS installed on the same machine. Don't do that.
Thanks for somehow showing the right direction, even I don’t understand, why FR 3.2.5 is still in place when starting with „freerad -fxx -l stdout“ instead of „freeradius -fxx-l stdout“,
See the local configuration on your machine. i.e. PATH variable, and whatever else you've configured.
any idea how I can cleanup this version situation on our freeradius server?
Use your local OS tools to remove one of versions of FreeRADIUS.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html