On 06.03.22 09:51, P.Thirunavukkarasu wrote:
*Hi Team,* *Greetings..* *I am getting the message for radiusd -X as "-bash command not found"*
*How to do the radiusd -X to identify the issues?*
Please check if freeradius (or radiusd) is in your path. the -X option swithces on the debug level. It does NOT identify issues. You have to read and understand the debug output.
*root@packetfence:~# /etc/init.d/freeradius status● freeradius.service - FreeRADIUS multi-protocol policy server Loaded: loaded (/lib/systemd/system/freeradius.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ <http://wiki.freeradius.org/> http://networkradius.com/doc/ <http://networkradius.com/doc/>----------------------*
*root@packetfence:~# /etc/init.d/freeradius startStarting freeradius (via systemctl): freeradius.serviceJob for freeradius.service failed because the control process exited with error code.See "systemctl status freeradius.service" and "journalctl -xe" for details.*
*failed!* *----------------------*
*root@packetfence:~# systemctl status freeradius.service● freeradius.service - FreeRADIUS multi-protocol policy server Loaded: loaded (/lib/systemd/system/freeradius.service; disabled; vendor p> Active: activating (auto-restart) (Result: exit-code) since Sun 2022-03-06> Docs: man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ <http://wiki.freeradius.org/> http://networkradius.com/doc/ <http://networkradius.com/doc/> Process: 3947 ExecStartPre=/bin/chown freerad:freerad /var/run/freeradius (> Process: 3948 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -ls> Process: 3949 ExecStart=/usr/sbin/freeradius -f $FREERADIUS_OPTIONS (code=e> Main PID: 3949 (code=exited, status=1/FAILURE) CPU: 176msMar 06 19:31:00 packetfence systemd[1]: freeradius.service: Main process exited>Mar 06 19:31:00 packetfence systemd[1]: freeradius.service: Failed with result >Mar 06 19:31:00 packetfence systemd[1]: Failed to start FreeRADIUS multi-protoc>lines 1-16/16 (END)...skipping...● freeradius.service - FreeRADIUS multi-protocol policy server Loaded: loaded (/lib/systemd/system/freeradius.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sun 2022-03-06 19:31:00 IST; 2s ago Docs: man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ <http://wiki.freeradius.org/> http://networkradius.com/doc/ <http://networkradius.com/doc/> Process: 3947 ExecStartPre=/bin/chown freerad:freerad /var/run/freeradius (code=exited, status=0/SUCCESS) Process: 3948 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -lstdout (code=exited, status=0/SUCCESS) Process: 3949 ExecStart=/usr/sbin/freeradius -f $FREERADIUS_OPTIONS (code=exited, status=1/FAILURE) Main PID: 3949 (code=exited, status=1/FAILURE) CPU: 176msMar 06 19:31:00 packetfence systemd[1]: freeradius.service: Main process exited, code=exited, status=1/FAILUREMar 06 19:31:00 packetfence systemd[1]: freeradius.service: Failed with result 'exit-code'.Mar 06 19:31:00 packetfence systemd[1]: Failed to start FreeRADIUS multi-protocol policy server.* *--------------------*
*root@packetfence:~# journalctl -xeMar 06 19:32:58 packetfence freeradius[4676]: Starting - reading configuration files ...Mar 06 19:32:58 packetfence freeradius[4676]: Ignoring "response_window = 20.000000", forcing to "response_window = >Mar 06 19:32:58 packetfence freeradius[4676]: Ignoring "response_window = 30.000000", forcing to "response_window = >Mar 06 19:32:58 packetfence freeradius[4676]: Ignoring "response_window = 30.000000", forcing to "response_window = >Mar 06 19:32:58 packetfence freeradius[4676]: /usr/local/pf/raddb/proxy.conf.inc[20]: Duplicate home server address >Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Control process exited, code=exited, statu>░░ Subject: Unit process exited░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ An ExecStartPre= process belonging to unit packetfence-radiusd-auth.service has exited.░░░░ The process' exit code is 'exited' and its exit status is 1.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Failed with result 'exit-code'.░░ Subject: Unit failed░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ The unit packetfence-radiusd-auth.service has entered the 'failed' state with result 'exit-code'.Mar 06 19:32:58 packetfence systemd[1]: Failed to start PacketFence FreeRADIUS authentication multi-protocol authent>░░ Subject: A start job for unit packetfence-radiusd-auth.service has failed░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ A start job for unit packetfence-radiusd-auth.service has finished with a failure.░░░░ The job identifier is 37980 and the job result is failed.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Consumed 3.214s CPU time.░░ Subject: Resources consumed by unit runtime░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ The unit packetfence-radiusd-auth.service completed and consumed the indicated resources.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Scheduled restart job, restart counter is
░░ Subject: Automatic restarting of a unit has been scheduled░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ Automatic restarting of the unit packetfence-radiusd-auth.service has been scheduled, as the result for░░ the configured Restart= setting for the unit.Mar 06 19:32:58 packetfence systemd[1]: Stopped PacketFence FreeRADIUS authentication multi-protocol authentication >░░ Subject: A stop job for unit packetfence-radiusd-auth.service has finished░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ A stop job for unit packetfence-radiusd-auth.service has finished.░░░░ The job identifier is 38364 and the job result is done.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Consumed 3.214s CPU time.░░ Subject: Resources consumed by unit runtime░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ The unit packetfence-radiusd-auth.service completed and consumed the indicated resources.Mar 06 19:32:58 packetfence systemd[1]: Starting PacketFence FreeRADIUS authentication multi-protocol authentication>░░ Subject: A start job for unit packetfence-radiusd-auth.service has begun execution░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ A start job for unit packetfence-radiusd-auth.service has begun execution.░░░░ The job identifier is 38364.lines 2663-2724/2724 (END)Mar 06 19:32:58 packetfence freeradius[4676]: Starting - reading configuration files ...Mar 06 19:32:58 packetfence freeradius[4676]: Ignoring "response_window = 20.000000", forcing to "response_window = 10.000000"Mar 06 19:32:58 packetfence freeradius[4676]: Ignoring "response_window = 30.000000", forcing to "response_window = 10.000000"Mar 06 19:32:58 packetfence freeradius[4676]: Ignoring "response_window = 30.000000", forcing to "response_window = 10.000000"Mar 06 19:32:58 packetfence freeradius[4676]: /usr/local/pf/raddb/proxy.conf.inc[20]: Duplicate home server address (already in use by eduroam_server2): 144.16.140.190:UDP/1812Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Control process exited, code=exited, status=1/FAILURE░░ Subject: Unit process exited░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ An ExecStartPre= process belonging to unit packetfence-radiusd-auth.service has exited.░░░░ The process' exit code is 'exited' and its exit status is 1.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Failed with result 'exit-code'.░░ Subject: Unit failed░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ The unit packetfence-radiusd-auth.service has entered the 'failed' state with result 'exit-code'.Mar 06 19:32:58 packetfence systemd[1]: Failed to start PacketFence FreeRADIUS authentication multi-protocol authentication server.░░ Subject: A start job for unit packetfence-radiusd-auth.service has failed░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ A start job for unit packetfence-radiusd-auth.service has finished with a failure.░░░░ The job identifier is 37980 and the job result is failed.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Consumed 3.214s CPU time.░░ Subject: Resources consumed by unit runtime░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ The unit packetfence-radiusd-auth.service completed and consumed the indicated resources.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Scheduled restart job, restart counter is at 107.░░ Subject: Automatic restarting of a unit has been scheduled░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ Automatic restarting of the unit packetfence-radiusd-auth.service has been scheduled, as the result for░░ the configured Restart= setting for the unit.Mar 06 19:32:58 packetfence systemd[1]: Stopped PacketFence FreeRADIUS authentication multi-protocol authentication server.░░ Subject: A stop job for unit packetfence-radiusd-auth.service has finished░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ A stop job for unit packetfence-radiusd-auth.service has finished.░░░░ The job identifier is 38364 and the job result is done.Mar 06 19:32:58 packetfence systemd[1]: packetfence-radiusd-auth.service: Consumed 3.214s CPU time.░░ Subject: Resources consumed by unit runtime░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ The unit packetfence-radiusd-auth.service completed and consumed the indicated resources.Mar 06 19:32:58 packetfence systemd[1]: Starting PacketFence FreeRADIUS authentication multi-protocol authentication server...░░ Subject: A start job for unit packetfence-radiusd-auth.service has begun execution░░ Defined-By: systemd░░ Support: https://www.debian.org/support <https://www.debian.org/support>░░░░ A start job for unit packetfence-radiusd-auth.service has begun execution.░░░░ The job identifier is 38364.lines 2663-2724/2724 (END)* *--------------* root@packetfence:~# /etc/init.d/freeradius status ● freeradius.service - FreeRADIUS multi-protocol policy server Loaded: loaded (/lib/systemd/system/freeradius.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sun 2022-03-06 19:37:08 IST; 2s ago Docs: man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ http://networkradius.com/doc/ Process: 6189 ExecStartPre=/bin/chown freerad:freerad /var/run/freeradius (code=exited, status=0/SUCCESS) Process: 6191 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -lstdout (code=exited, status=0/SUCCESS) Process: 6192 ExecStart=/usr/sbin/freeradius -f $FREERADIUS_OPTIONS (code=exited, status=1/FAILURE) Main PID: 6192 (code=exited, status=1/FAILURE) CPU: 176ms
Thanks and Regards Thirunavukkarasu - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Mit freundlichen Grüßen, -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein