Red Hat Bugzilla – Bug 829237
/etc/raddb/modules/ldap.rpmnew will be created by an update leading to unexpected ldap module configurtaion
Last modified: 2013-11-01 13:52:03 EDT
Description of problem:
There was an update of freeradius2-ldap. During the update process, /etc/raddb/modules/ldap.rpmnew was created which was evaluated after a restart of radiusd. ldap.rpmnew was evaluated after ldap which overwrites the site specific configuration.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. update to freeradius2-ldap.x86_64 2.1.12-3.el5
There will be a new ldap module config file named /etc/raddb/modules/ldap.rpmnew which overrides the configuration defined in /etc/raddb/modules/ldap.
- No change in the existing configuration
My solution was to delete /etc/raddb/modules/ldap.rpmnew.
One could exclude /etc/raddb/modules/*.rpmnew from the radius configuration loading process to avoid this kind of problem in the future.
this is a duplicate of 804932
Please see the additional discussion in bug #804932.
This issue is fixed in FreeRADIUS versions >= 2.2.0, the server will ignore certain well known files (including .rpmnew and .rpmsave as well as Debian package files, ~ appended files, etc.).
In general we suggest after applying updates the admin should check for the presence of .rpmnew and .rpmsave files and resolve them.
This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore will be closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide sufficient business