radiusd.service watchdog timeout
Hey, I’m using FR 3.0.12 on a CentOS 7 and while running as service the process runs into watchdog timeout: ——> systemd: radiusd.service watchdog timeout (limit 1min)! systemd: radiusd.service: main process exited, code=killed, status=6/ABRT systemd: Unit radiusd.service entered failed state. systemd: radiusd.service failed. <—— Here’s my Unit-File: ——> [Unit] Description=FreeRADIUS multi-protocol policy server After=network.target Documentation=man:radiusd(8) man:radiusd.conf(5) http://wiki.freeradius.org/ <http://wiki.freeradius.org/> http://networkradius.com/doc/ <http://networkradius.com/doc/> [Service] Type=simple WatchdogSec=60 NotifyAccess=all PIDFile=/usr/local/var/run/radiusd/radiusd.pid EnvironmentFile=-/etc/sysconfig/radiusd RuntimeDirectory=/usr/local/var/run/radiusd RuntimeDirectoryMode=0775 ExecStartPre=/usr/local/sbin/radiusd $FREERADIUS_OPTIONS -Cx -lstdout ExecStartPre=/usr/bin/chown radiusd:radiusd /usr/local/var/run/radiusd ExecStart=/usr/local/sbin/radiusd $FREERADIUS_OPTIONS Restart=on-failure RestartSec=5 [Install] WantedBy=multi-user.target <—— Any suggestions what could be wrong? Is more information for an analysis needed? Thanks a lot! Philipp —
On Thu, Jun 15, 2017 at 09:34:14AM +0200, Philipp Trenz wrote:
I’m using FR 3.0.12 on a CentOS 7 and while running as service the process runs into watchdog timeout:
——> systemd: radiusd.service watchdog timeout (limit 1min)! systemd: radiusd.service: main process exited, code=killed, status=6/ABRT systemd: Unit radiusd.service entered failed state. systemd: radiusd.service failed.
Well, yeah. FreeRADIUS 3 doesn't call sd_notify, so that will never work.
[Service] Type=simple WatchdogSec=60
Remove this line. And it should be type=forking as well. Simplest would be to just use the one shipped with the server: https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/redhat/radiusd.s... Matthew -- Matthew Newton, Ph.D. <mcn4@leicester.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
Hey Matthew, that was all I need to know. And the hint with the type is also helpful, many thanks! Philipp
Am 15.06.2017 um 12:04 schrieb Matthew Newton <mcn4@leicester.ac.uk <mailto:mcn4@leicester.ac.uk>>:
On Thu, Jun 15, 2017 at 09:34:14AM +0200, Philipp Trenz wrote:
I’m using FR 3.0.12 on a CentOS 7 and while running as service the process runs into watchdog timeout:
——> systemd: radiusd.service watchdog timeout (limit 1min)! systemd: radiusd.service: main process exited, code=killed, status=6/ABRT systemd: Unit radiusd.service entered failed state. systemd: radiusd.service failed.
Well, yeah. FreeRADIUS 3 doesn't call sd_notify, so that will never work.
[Service] Type=simple WatchdogSec=60
Remove this line. And it should be type=forking as well.
Simplest would be to just use the one shipped with the server:
https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/redhat/radiusd.s... <https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/redhat/radiusd.service>
Matthew
-- Matthew Newton, Ph.D. <mcn4@leicester.ac.uk <mailto:mcn4@leicester.ac.uk>>
Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk <mailto:ithelp@le.ac.uk>> - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>
—
participants (2)
-
Matthew Newton -
Philipp Trenz