Updated RHEL 4 to 5, ldap won't start now

[Frank DiPrete]

Not a definitivie answer, but the RH convention for a config file change
is to include a <conf_file>.rpmnew file with the rpm. If present you can
check the conf file against it to find the parameter change ...


On Wed, 2007-09-05 at 20:25 -0400, Dan Coutu wrote:
> I'm a bit stumped. I've been banging my head against the wall with this 
> all day now. I've upgraded a RHEL 4 system to version 5. It runs ldap 
> and does login authentication against the ldap server. When the system 
> booted after the upgrade it failed to start the ldap server and 
> displayed the amazingly informative error message:
> 
> slaptest: bad configuration file!
> 
> Wow. I'd bet there's a problem with the configuration file. But of 
> course there isn't. I found note indicating that this message can happen 
> if the files that are 'include'd within the configuration file are owned 
> by root rather than by ldap. Sure enough, the included files were owned 
> by root. Aha! says I and merrily changes the ownership of the files to 
> be ldap.
> 
> Sad to say this didn't resolve the problem. I've tried every variation 
> of the debug and verbose switches associated with slaptest and slapd but 
> get no insight into the real problem. Running slaptest with debug on 
> gives me something like this:
> 
> slaptest init: initiated tool.
> slap_sasl_init: initialized!
> bdb_back_initialize: initialize BDB backend
> bdb_back_initialize: Sleepycat Software: Berkeley DB 4.4.20: (January 
> 10, 2006)
> hdb_back_initialize: initialize HDB backend
> hdb_back_initialize: Sleepycat Software: Berkeley DB 4.4.20: (January 
> 10, 2006)
> bdb_db_init: Initializing BDB database
>  >>> dnPrettyNormal: <dc=snowy-owl,dc=com>
> <<< dnPrettyNormal: <dc=snowy-owl,dc=com>, <dc=snowy-owl,dc=com>
>  >>> dnPrettyNormal: <cn=Manager,dc=snowy-owl,dc=com>
> <<< dnPrettyNormal: <cn=Manager,dc=snowy-owl,dc=com>, 
> <cn=manager,dc=snowy-owl,dc=com>
> slaptest: bad configuration file!
> 
> I don't understand that dnPrettyNormal nonsense but the rest seems to 
> make sense.
> 
> Is there a way I get better detail as to exactly what is wrong so that I 
> can fix this?
> 
> Thanks,
> 
> Dan
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> 
>