Richard Megginson wrote: > Darren Fulton wrote: > >> We've been running FDS beta in production for a while now. I'd like >> to upgrade to 1.0 and then get current, especially because after the >> last reboot, the admin-serv won't run anymore. >> > What's the problem? Note that ns-slapd must be up and running and > accepting connections before admin-serv will start. > >> The only upgrade instructions that I've been able to find are at the >> bottom of the 1.0 Release Notes: >> >> Unfortunately, rpm -U (rpm upgrade install) is not supported. You >> must perform a migration from the old version. Steps: >> >> 1. Backup your data, using the console or the db2bak command >> line (or Export to LDIF) >> 2. Make a copy of your server configuration - the >> slapd-instance/config/dse.ldif file >> 3. Backup your key/cert/module information - the >> /opt/fedora-ds/alias .db files (you can ignore the .so file) >> 4. Uninstall the previous version (e.g. rpm -e fedora-ds) >> 5. Install the new version (e.g. rpm -ivh >> fedora-ds-1.0-2.platform.i386.opt.rpm) >> 6. Add back your configuration to the new instance e.g. do a >> diff between your saved dse.ldif and the new one >> 7. Add back your saved key/cert/module .db files to >> /opt/fedora-ds/alias >> 8. Restore your saved data (or import from LDIF) >> >> These notes aren't enough detail for me to get the job done. Is >> there a detailed procedure somewhere or can one of you good people >> help me? I've looked through the mailing list archives, FDS docs, >> RHDS docs, and googled. I'd like something like this: >> >> mkdir /var/backup/fds >> cd /opt/fedora-ds/slapd-host2 >> ./db2bak /var/backup/fds >> blah blah >> rpm -e fedora-ds >> etc etc >> >> >> Specific things in the upgrade steps from the release notes that I >> don't feel good about are: >> Step 1 - I don't know how to do that, but I think I might have done >> it correctly. >> >> > Yes, you are correct. > >> Step 4 - after rpm -e, it says some files may not have been removed >> and to remove them manually. Do you do rm -Rf /opt/fedora-ds? >> >> > Yes. > >> Step 6 - I don't know how to do that >> >> > cd /opt/fedora-ds/slapd-host2 > ./stop-slapd > diff -U 8 dse.ldif.saved config/dse.ldif > diffs > # where dse.ldif.saved is the one you saved in step 2 above > # now, take a look at the file diffs, and edit your config/dse.ldif > with any pertinent changes in diffs > ./start-slapd > >> Step 8 - I don't know how to do that >> >> > cd /opt/fedora-ds/slapd-host2 > ./stop-slapd > ./bak2db /var/backup/fds > ./start-slapd > >> Thanks in advance! >> >> >> >------------------------------------------------------------------------ > Awesome. I'll try that and report back. As to why the admin-serv on the current install won't work anymore, I don't know. Nothing interesting in the logs, except that once upon a time, the log would include somthing about using IBM Java, but now that isn't showing. Probably not a big deal, because the upgrade will get it running via apache, so hopefully it is a non-issue. If you want more info for whatever reason, I'll be glad to provide it. -- Best Regards, Darren Fulton -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
