Invalid vendor name in attribute name "0"
Hello, Seeking assistance troubleshooting the following error when running radiusd via Systemd. Error is: EXIT(1) CALLED src/main/mainconfig.c[955]. Last error was: Invalid vendor name in attribute name "0" Fresh install of FreeRADIUS 3.0.20. Compiled with "--localstatedir=/var --sysconfdir=/etc --with-rlm_sql_freetds --with-systemd" Operating System: Ubuntu 16.04.6 LTS Kernel: Linux 4.4.0-150-generic Architecture: x86-64 All configuration is default (aside from changing the user it is to run as to "Radiusd" in radiusd.conf). Running "radiusd -X" as root works as expected. Running "radiusd -X" as radiusd user manually works as expected. Only receive the error when running via Systemd. Systemd unit file is: [Unit] Description=FreeRADIUS multi-protocol policy server After=network-online.target Documentation=man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ http://networkradius.com/doc/ [Service] Type=notify WatchdogSec=60 NotifyAccess=all PIDFile=/var/run/radiusd/radiusd.pid EnvironmentFile=-/etc/default/radiusd # FreeRADIUS can do static evaluation of policy language rules based # on environmental variables which is very useful for doing per-host # customization. # Unfortunately systemd does not allow variable substitutions such # as %H or $(hostname) in the EnvironmentFile. # We provide HOSTNAME here for convenience. Environment=HOSTNAME=%H # Limit memory to 2G this is fine for %99.99 of deployments. FreeRADIUS # is not memory hungry, if it's using more than this, then there's probably # a leak somewhere. MemoryLimit=2G RuntimeDirectory=radiusd RuntimeDirectoryMode=0775 ExecStartPre=/usr/sbin/radiusd $FREERADIUS_OPTIONS -Cx -lstdout ExecStartPre=/bin/chown radiusd:radiusd /var/run/radiusd ExecStart=/usr/sbin/radiusd $FREERADIUS_OPTIONS Restart=on-failure RestartSec=5 # Don't elevate privileges after starting NoNewPrivileges=true # Allow binding to secure ports, broadcast addresses, and raw interfaces. CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW # Private /tmp that isn't shared by other processes PrivateTmp=true # cgroups are readable only by radiusd, and child processes ProtectControlGroups=true # don't load new kernel modules ProtectKernelModules=true # don't tune kernel parameters ProtectKernelTunables=true # Only allow native system calls SystemCallArchitectures=native # We shouldn't be writing to the configuration directory ReadOnlyDirectories=/etc/raddb/ # We can read and write to the log directory. ReadWriteDirectories=/var/log/radius/ [Install] WantedBy=multi-user.target Please let me know if there is any additional information that may help. Thank you. -- *Kyle Parrish* KyleParrish.com *living life to the fullest*
Please, report the issue in https://github.com/FreeRADIUS/freeradius-server/issues/new?template=bug_repo... On Fri, Jun 7, 2019 at 9:40 AM Kyle Parrish <arnydo@gmail.com> wrote:
Hello,
Seeking assistance troubleshooting the following error when running radiusd via Systemd.
Error is: EXIT(1) CALLED src/main/mainconfig.c[955]. Last error was: Invalid vendor name in attribute name "0"
Fresh install of FreeRADIUS 3.0.20. Compiled with "--localstatedir=/var --sysconfdir=/etc --with-rlm_sql_freetds --with-systemd" Operating System: Ubuntu 16.04.6 LTS Kernel: Linux 4.4.0-150-generic Architecture: x86-64 All configuration is default (aside from changing the user it is to run as to "Radiusd" in radiusd.conf).
Running "radiusd -X" as root works as expected. Running "radiusd -X" as radiusd user manually works as expected.
Only receive the error when running via Systemd.
Systemd unit file is: [Unit] Description=FreeRADIUS multi-protocol policy server After=network-online.target Documentation=man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ http://networkradius.com/doc/
[Service] Type=notify WatchdogSec=60 NotifyAccess=all PIDFile=/var/run/radiusd/radiusd.pid EnvironmentFile=-/etc/default/radiusd
# FreeRADIUS can do static evaluation of policy language rules based # on environmental variables which is very useful for doing per-host # customization. # Unfortunately systemd does not allow variable substitutions such # as %H or $(hostname) in the EnvironmentFile. # We provide HOSTNAME here for convenience. Environment=HOSTNAME=%H
# Limit memory to 2G this is fine for %99.99 of deployments. FreeRADIUS # is not memory hungry, if it's using more than this, then there's probably # a leak somewhere. MemoryLimit=2G
RuntimeDirectory=radiusd RuntimeDirectoryMode=0775 ExecStartPre=/usr/sbin/radiusd $FREERADIUS_OPTIONS -Cx -lstdout ExecStartPre=/bin/chown radiusd:radiusd /var/run/radiusd ExecStart=/usr/sbin/radiusd $FREERADIUS_OPTIONS Restart=on-failure RestartSec=5
# Don't elevate privileges after starting NoNewPrivileges=true
# Allow binding to secure ports, broadcast addresses, and raw interfaces. CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW
# Private /tmp that isn't shared by other processes PrivateTmp=true
# cgroups are readable only by radiusd, and child processes ProtectControlGroups=true
# don't load new kernel modules ProtectKernelModules=true
# don't tune kernel parameters ProtectKernelTunables=true
# Only allow native system calls SystemCallArchitectures=native
# We shouldn't be writing to the configuration directory ReadOnlyDirectories=/etc/raddb/
# We can read and write to the log directory. ReadWriteDirectories=/var/log/radius/
[Install] WantedBy=multi-user.target
Please let me know if there is any additional information that may help.
Thank you.
-- *Kyle Parrish* KyleParrish.com *living life to the fullest* - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Just added https://github.com/FreeRADIUS/freeradius-server/issues/2734 Thank you. Regards On Fri, Jun 7, 2019 at 9:12 AM Jorge Pereira <jpereira@freeradius.org> wrote: > Please, report the issue in > > https://github.com/FreeRADIUS/freeradius-server/issues/new?template=bug_report.md > > On Fri, Jun 7, 2019 at 9:40 AM Kyle Parrish <arnydo@gmail.com> wrote: > > > Hello, > > > > Seeking assistance troubleshooting the following error when running > radiusd > > via Systemd. > > > > Error is: > > EXIT(1) CALLED src/main/mainconfig.c[955]. Last error was: Invalid > vendor > > name in attribute name "0" > > > > Fresh install of FreeRADIUS 3.0.20. > > Compiled with "--localstatedir=/var --sysconfdir=/etc > > --with-rlm_sql_freetds --with-systemd" > > Operating System: Ubuntu 16.04.6 LTS > > Kernel: Linux 4.4.0-150-generic > > Architecture: x86-64 > > All configuration is default (aside from changing the user it is to run > as > > to "Radiusd" in radiusd.conf). > > > > Running "radiusd -X" as root works as expected. > > Running "radiusd -X" as radiusd user manually works as expected. > > > > Only receive the error when running via Systemd. > > > > Systemd unit file is: > > [Unit] > > Description=FreeRADIUS multi-protocol policy server > > After=network-online.target > > Documentation=man:radiusd(8) man:radiusd.conf(5) > > http://wiki.freeradius.org/ > > http://networkradius.com/doc/ > > > > [Service] > > Type=notify > > WatchdogSec=60 > > NotifyAccess=all > > PIDFile=/var/run/radiusd/radiusd.pid > > EnvironmentFile=-/etc/default/radiusd > > > > # FreeRADIUS can do static evaluation of policy language rules based > > # on environmental variables which is very useful for doing per-host > > # customization. > > # Unfortunately systemd does not allow variable substitutions such > > # as %H or $(hostname) in the EnvironmentFile. > > # We provide HOSTNAME here for convenience. > > Environment=HOSTNAME=%H > > > > # Limit memory to 2G this is fine for %99.99 of deployments. FreeRADIUS > > # is not memory hungry, if it's using more than this, then there's > probably > > # a leak somewhere. > > MemoryLimit=2G > > > > RuntimeDirectory=radiusd > > RuntimeDirectoryMode=0775 > > ExecStartPre=/usr/sbin/radiusd $FREERADIUS_OPTIONS -Cx -lstdout > > ExecStartPre=/bin/chown radiusd:radiusd /var/run/radiusd > > ExecStart=/usr/sbin/radiusd $FREERADIUS_OPTIONS > > Restart=on-failure > > RestartSec=5 > > > > # Don't elevate privileges after starting > > NoNewPrivileges=true > > > > # Allow binding to secure ports, broadcast addresses, and raw interfaces. > > CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE > CAP_NET_BROADCAST > > CAP_NET_RAW > > > > # Private /tmp that isn't shared by other processes > > PrivateTmp=true > > > > # cgroups are readable only by radiusd, and child processes > > ProtectControlGroups=true > > > > # don't load new kernel modules > > ProtectKernelModules=true > > > > # don't tune kernel parameters > > ProtectKernelTunables=true > > > > # Only allow native system calls > > SystemCallArchitectures=native > > > > # We shouldn't be writing to the configuration directory > > ReadOnlyDirectories=/etc/raddb/ > > > > # We can read and write to the log directory. > > ReadWriteDirectories=/var/log/radius/ > > > > [Install] > > WantedBy=multi-user.target > > > > > > Please let me know if there is any additional information that may help. > > > > Thank you. > > > > -- > > *Kyle Parrish* > > KyleParrish.com > > *living life to the fullest* > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html -- *Kyle Parrish* KyleParrish.com *living life to the fullest*
On Jun 7, 2019, at 8:39 AM, Kyle Parrish <arnydo@gmail.com> wrote:
Seeking assistance troubleshooting the following error when running radiusd via Systemd.
Error is: EXIT(1) CALLED src/main/mainconfig.c[955]. Last error was: Invalid vendor name in attribute name "0"
Something is going wrong when the server is changing UIDs. I've pushed a fix so that it prints out the actual error message, instead of "invalid vendor name". Please grab the latest code and re-build. The error message should be clearer. Alan DeKok.
Thank you for the followup. The new error is: *Application and libfreeradius-radius magic number (commit) mismatch. application: ba62e22 library: bceabf5* On Sat, Jun 8, 2019 at 3:09 AM Alan DeKok <aland@deployingradius.com> wrote:
On Jun 7, 2019, at 8:39 AM, Kyle Parrish <arnydo@gmail.com> wrote:
Seeking assistance troubleshooting the following error when running radiusd via Systemd.
Error is: EXIT(1) CALLED src/main/mainconfig.c[955]. Last error was: Invalid vendor name in attribute name "0"
Something is going wrong when the server is changing UIDs.
I've pushed a fix so that it prints out the actual error message, instead of "invalid vendor name".
Please grab the latest code and re-build. The error message should be clearer.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- *Kyle Parrish* KyleParrish.com *living life to the fullest*
On Jun 10, 2019, at 6:11 PM, Kyle Parrish <arnydo@gmail.com> wrote:
Thank you for the followup.
The new error is: Application and libfreeradius-radius magic number (commit) mismatch. application: ba62e22 library: bceabf5
You installed two different versions of the server on the same machine. Don’t do that. You can’t mix & match server binaries and libraries from different versions.
Do you have any tips on removing the “other” version? There only appears to be one version currently installed. Maybe something lingering from a previous install? On Mon, Jun 10, 2019 at 3:04 PM Alan DeKok <aland@deployingradius.com> wrote:
On Jun 10, 2019, at 6:11 PM, Kyle Parrish <arnydo@gmail.com> wrote:
Thank you for the followup.
The new error is: *Application and libfreeradius-radius magic number (commit) mismatch. application: ba62e22 library: bceabf5*
You installed two different versions of the server on the same machine. Don’t do that. You can’t mix & match server binaries and libraries from different versions.
-- *Kyle Parrish* KyleParrish.com *living life to the fullest*
On Jun 10, 2019, at 3:51 PM, Kyle Parrish <arnydo@gmail.com> wrote:
Do you have any tips on removing the “other” version?
They're just libraries on disk. Remove the rlm_*.so files.
There only appears to be one version currently installed. Maybe something lingering from a previous install?
Yes. Make sure that *all* remnants of FreeRADIUS are wiped from the system. Then, do a fresh install. Alan DeKok.
participants (3)
-
Alan DeKok -
Jorge Pereira -
Kyle Parrish