Bug 1289849

Summary:	FreeRadius should start after ldap, ipa and krb5kdc
Product:	Red Hat Enterprise Linux 7	Reporter:	wibrown <wibrown>
Component:	freeradius	Assignee:	Nikolai Kondrashov <nikolai.kondrashov>
Status:	CLOSED ERRATA	QA Contact:	Jaroslav Aster <jaster>
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.1	CC:	dpal, jaster, mmarusic, peljasz, pkis
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 20:36:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description wibrown@redhat.com 2015-12-09 07:14:54 UTC

Description of problem:
If freeradius is installed on the same machine as an ipa master, 389-ds master, or kdc, radius will often start before the other services are ready to handle queries. As a result, this causes freeradius to be fail to connect to ldap / krb and will not start or will fail to server authentication events.

The radiusd.service file should be altered to contain the following "After" line:

[Unit]
Description=FreeRADIUS high performance RADIUS server.
After=syslog.target network.target ipa.service dirsrv.target krb5kdc.service

This does not affect the radius start up on systems that don't have any of these three services installed.

Comment 4 Nikolai Kondrashov 2016-06-09 18:22:27 UTC

*** Bug 1344408 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2017-08-01 20:36:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1954