On 01/08/2014 10:52 AM, Paul Whitney wrote:
Hi Rich, thank you for the quick response.

I ran the script as you suggested and after the interview process (server, credentials, etc) the update stops on error:

Error adding entry 'cn=PAM Pass Through Auth,cn=plugins,cn=config'. Error: Already exists.

Can you provide the output of running
setup-ds-admin.pl -u -ddd




I did not run this setup-ds-admin script on the other servers in my development environment, but they were able to update successfully with just the setup-ds.pl -u script.

Note that rpm/yum runs setup-ds.pl -u during the post-install phase.  You should never have to run setup-ds.pl -u manually.  setup-ds-admin.pl -u cannot be run automatically because it has to contact the (possibly) remote machine with o=NetscapeRoot, and you have to provide the admin password.


Also, as a test, I created a new instance on the server and the new instances does show that it is using version 9.1.

Right.  New instances will work fine.  The problem is in upgrading existing instances.

Paul M. Whitney
E-mail: paul.whitney@mac.com





On Jan 08, 2014, at 12:31 PM, Rich Megginson <rmeggins@redhat.com> wrote:

On 01/08/2014 10:31 AM, Paul Whitney wrote:
Hi,

I recently updated RHDS 9.0 servers to 9.1.  I am getting mixed results with the update.  Steps taken:

1.  Stop all dirsrv and dirsrv-admin services
2.  Executed yum localupdate *.rpm
3.  After the yum completes.  Execute setup-ds.pl --debug --update (no errors generated, status is databases updated successfully.
4.  Reinstall openldap (based on  RHBA-2013-0778).
5. Reboot system.  (I do this because restarting the dirsrv-admin service still generates the NSS error in the error log, but with a reboot it does not.)
6. connect to system and see jars have not loaded. I select Admin and an error states I do not have 9.0jar and cannot install.

You have to run setup-ds-admin.pl -u to update the version information used by the .jar file locator.


I checked the master and it no longer has the 9.0 jar, but rather the 9.1  But for some reason the admin server is still looking for 9.0 jars.

I tried to change the /etc/dirsv/admin-serv/local.conf file to look like a working 9.1 local.conf file, but it seems that file is ignored. 

That is a read-only file.  It is basically just a "cache" of the information stored under o=NetscapeRoot, used for bootstrap purposes, or if the directory server is down.


Looking for ideas on what else I can do "upgrade" the directory server.

Paul M. Whitney
E-mail: paul.whitney@mac.com






--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users