Hi Barry,Could it be possible to share your error log (/var/log/dirsrv/slapd-ID/errors) with us? We are interested in what happened in "yum upgrade 389-ds-base", in which dn2rdn should be generated and DB upgrade should have finished.
Also, what does your yum.log store about 389-ds? # grep 389-ds /var/log/yum.log Thanks, --noriko On 10/19/2010 10:28 PM, Barry Sitompul wrote:
Hi Guys, I'm having problems upgrading from 1.2.5 Here's what I did: # yum upgrade 389-ds-base -runs fine # setup-ds-admin.pl -u -error encountered: The server 'ldap://myldapserver.com:389/o=NetscapeRoot' is not reachable. Error: unknown error It turns out that the 389-DS is not running because of these errors in its error log: 389-Directory/1.2.6.1 B2010.272.2313 myldapserver.com:389 (/etc/dirsrv/slapd-myldapserver) [20/Oct/2010:14:35:41 +1000] - 389-Directory/1.2.6.1 B2010.272.2313 starting up [20/Oct/2010:14:35:42 +1000] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [20/Oct/2010:14:35:42 +1000] - nsslapd-subtree-rename-switch is on, while the instance userRoot is in the DN format. Please run dn2rdn to convert the database format. [20/Oct/2010:14:35:42 +1000] - nsslapd-subtree-rename-switch is on, while the instance Root1 is in the DN format. Please run dn2rdn to convert the database format. [20/Oct/2010:14:35:42 +1000] - nsslapd-subtree-rename-switch is on, while the instance Root2 is in the DN format. Please run dn2rdn to convert the database format. [20/Oct/2010:14:35:42 +1000] - nsslapd-subtree-rename-switch is on, while the instance Root3 is in the DN format. Please run dn2rdn to convert the database format. [20/Oct/2010:14:35:42 +1000] - nsslapd-subtree-rename-switch is on, while the instance NetscapeRoot is in the DN format. Please run dn2rdn to convert the database format. [20/Oct/2010:14:35:42 +1000] - nsslapd-subtree-rename-switch is on, while the instance Root4 is in the DN format. Please run dn2rdn to convert the database format. [20/Oct/2010:14:35:42 +1000] - start: Failed to start databases, err=-1 Unknown error: -1 [20/Oct/2010:14:35:42 +1000] - Failed to start database plugin ldbm database [20/Oct/2010:14:35:42 +1000] - WARNING: ldbm instance userRoot already exists [20/Oct/2010:14:35:42 +1000] - WARNING: ldbm instance Root1 already exists [20/Oct/2010:14:35:42 +1000] - WARNING: ldbm instance Root2 already exists [20/Oct/2010:14:35:42 +1000] - WARNING: ldbm instance Root3 already exists [20/Oct/2010:14:35:42 +1000] - WARNING: ldbm instance NetscapeRoot already exists [20/Oct/2010:14:35:42 +1000] - WARNING: ldbm instance Root4 already exists [20/Oct/2010:14:35:42 +1000] binder-based resource limits - nsLookThroughLimit: parameter error (slapi_reslimit_register() already registered) [20/Oct/2010:14:35:42 +1000] - start: Resource limit registration failed [20/Oct/2010:14:35:42 +1000] - Failed to start database plugin ldbm database [20/Oct/2010:14:35:42 +1000] - Error: Failed to resolve plugin dependencies [20/Oct/2010:14:35:42 +1000] - Error: preoperation plugin 7-bit check is not started [20/Oct/2010:14:35:42 +1000] - Error: accesscontrol plugin ACL Plugin is not started [20/Oct/2010:14:35:42 +1000] - Error: preoperation plugin ACL preoperation is not started [20/Oct/2010:14:35:42 +1000] - Error: object plugin Class of Service is not started [20/Oct/2010:14:35:42 +1000] - Error: preoperation plugin deref is not started [20/Oct/2010:14:35:42 +1000] - Error: preoperation plugin HTTP Client is not started [20/Oct/2010:14:35:42 +1000] - Error: database plugin ldbm database is not started [20/Oct/2010:14:35:42 +1000] - Error: object plugin Legacy Replication Plugin is not started [20/Oct/2010:14:35:42 +1000] - Error: preoperation plugin Linked Attributes is not started [20/Oct/2010:14:35:42 +1000] - Error: object plugin Multimaster Replication Plugin is not started [20/Oct/2010:14:35:42 +1000] - Error: object plugin Roles Plugin is not started [20/Oct/2010:14:35:42 +1000] - Error: preoperation plugin Simple Kerberos 5 Auth is not started [20/Oct/2010:14:35:42 +1000] - Error: object plugin Views is not started - I wanted to do the dn2rdn or just switch off the subtree-rename- switch, so... - I looked at the instance's dse.ldif and I can't find the: dn: cn=config,cn=ldbm database,cn=plugins,cn=config [...] nsslapd-subtree-rename-switch: on - But nsslapd-subtree-rename-switch exists is in this file: /usr/ share/dirsrv/data/template-dse.ldif. I tried changing the value to 'off' but I still got the same errors. - I also can't find the the dn2rdn tool in the slapd instance directory. I did a locate and only found it here: /usr/share/dirsrv/ script-templates/template-dn2rdn -So I got really confused and thought maybe I should do this: # setup-ds.pl -u -d = = = = = = ======================================================================== This program will update the 389 Directory Server. It is recommended that you have "root" privilege to perform the update. Tips for using this program: - Press "Enter" to choose the default and go to the next screen - Type "Control-B" or the word "back" then "Enter" to go back to the previous screen - Type "Control-C" to cancel the update Would you like to continue with update? [yes]: = = = = = = ======================================================================== The update process can work in one of two modes: - Online: The changes are made to the running directory servers using LDAP. The operations must be performed as an administrative user. You must provide the name and password, for each instance if there is more than one instance of directory server. Some operations may require a directory server restart to take effect. The update script will notify you if you need to restart the server. - Offline: The changes are made to the server configuration files. The servers MUST FIRST BE SHUTDOWN BY YOU. The script will not shutdown the servers for you. You MUST shutdown the servers in order to use this mode. A username and password are not required to use Offline mode. If the servers are not shutdown, CHANGES WILL BE LOST. To summarize: Online - servers remain running - you must provide admin name and password for each server - servers may need to be restarted Offline - servers must be shutdown - no username or password required Which update mode do you want to use? [quit]: offline +Running stage pre update /usr/share/dirsrv/updates/ 50addchainingsaslpwroles.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50bitstringsyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50deliverymethodsyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/50derefplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50disableurisyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50enhancedguidesyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/50entryusnindex.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50faxnumbersyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50faxsyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50guidesyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50linkedattrsplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/50memberofindex.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50memberofplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50nameuidsyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50numericstringsyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50printablestringsyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50retroclprecedence.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50schemareloadplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50smd5pwdstorageplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50syntaxvalidplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50teletexterminalidsyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/ 50telexnumbersyntaxplugin.ldif +Running stage pre update /usr/share/dirsrv/updates/50usnplugin.ldif Could not open the script template file '1/bak2db'. Error: No such file or directory Error: could not update the directory server. Exiting . . . - What is that '1/bak2db' script template file and why can't the setup- ds.pl find it ? I see on the http://directory.fedoraproject.org/wiki/Release_Notes stating that there is no problem upgrading from 1.2.5..Am I doing something completely wrong here? Any help is much appreciated! Thanks! Bazza -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
<<attachment: smime.p7s>>
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
