Problem with Migration
Hi Jay,
I am attempting to migrate from iMS5.2 to 6.2Q4. DS 5.2 is on same box as iMS.
There is a problem with my DS5.2 in that I cannot restore backups that it creates. Support has been unable to solve this as it is a holdover from the 4.16 migration. Anyway, the solution was to create a second instance of DS.
I ran dss_setup.pl against the second instance. Exported my users from the first instance to the second. Same with my PAB. I also exported and imported the o=netscaperoot. No errors or problems.
Ran the 6.2 configure script and pointed it to the new instance for both users/groups and config. No errors reported.
When I try to start the new 6.2 mail I get an error that it can't find the configuration server.
I opened a ticket on this almost 2 weeks ago and have had no suggestions made at all. In fact, I can't even get calls or email returned. It was my initial call back (and only) that told me to also export the netscaperoot and point the mail configuration script to it for config. My suspicion is that I messed something up with that as on my test servers the other exports worked just fine and I didn't do the netscaperoot in my test environment.
Have you got any suggestions?
Thanks
Don
[1273 byte] By [
carlgren1] at [2007-11-26 8:59:59]
# 1
Hm....
well, there're two ways to "back up" a directory server.
export to ldif is one way
export to .bak is the other.
I can't imagine why you would not be able to restore a backup, taken either way.
for your config problem.
Check what you see (or do not see) in the ldap access log when you try to start messaging.
Also, check configutil settings for "local.ldap" settings, and make sure they're pointed correctly.
I vaguely remember an install issue, where you couldn't specify different config and user/group ldap on install, but not what you were doing.
the config stuff lives in the o=NetscapeRoot area. Check that your BINDs are successful, and see if you're finding stuff when it SEARCHes.
# 2
Thanks for the info Jay,
Here is what I have.
access log:
[24/Jul/2006:13:37:32 -0600] conn=0 op=-1 msgId=-1 - fd=37 slot=37 LDAP connection from 192.168.0.12 to 192.168.0.12
[24/Jul/2006:13:37:32 -0600] conn=0 op=0 msgId=1 - BIND dn="cn=msg-config, cn=Sun ONE Messaging Suite, cn=Server Group, cn
=onyx.mydomain.ab.ca, ou=mydomain.ab.ca, o=NetscapeRoot" method=128 version=2
[24/Jul/2006:13:37:32 -0600] conn=0 op=0 msgId=1 - RESULT err=32 tag=97 nentries=0 etime=0
[24/Jul/2006:13:37:32 -0600] conn=0 op=-1 msgId=-1 - closing - B1
[24/Jul/2006:13:37:32 -0600] conn=0 op=-1 msgId=-1 - closed.
[24/Jul/2006:13:37:32 -0600] conn=1 op=-1 msgId=-1 - fd=37 slot=37 LDAP connection from 192.168.0.12 to 192.168.0.12
[24/Jul/2006:13:37:32 -0600] conn=1 op=0 msgId=1 - BIND dn="cn=msg-config, cn=Sun ONE Messaging Suite, cn=Server Group, cn
=onyx.mydomain.ab.ca, ou=mydomain.ab.ca, o=NetscapeRoot" method=128 version=2
[24/Jul/2006:13:37:32 -0600] conn=1 op=0 msgId=1 - RESULT err=32 tag=97 nentries=0 etime=0
[24/Jul/2006:13:37:32 -0600] conn=1 op=-1 msgId=-1 - closing - B1
[24/Jul/2006:13:37:32 -0600] conn=1 op=-1 msgId=-1 - closed.
Startup Error Reported:
[24/Jul/2006:13:37:32 -0600] onyx [2279]: General Error: func=_configdrv_pset_fetch;error=could not access server's configuration in ldap: func=psetRealCreate; error=Entry does not exist
NO configmsg_init error
[24/Jul/2006:13:37:32 -0600] onyx [2281]: General Error: func=_configdrv_pset_fetch;error=could not access server's configuration in ldap: func=psetRealCreate; error=Entry does not exist
ERROR: Could not initialize config system
local.ldaphost=onyx.mydomain.ab.ca
local.ldapport=391
local.ldapbasedn=o=NetscapeRoot
local.ldapsiedn="cn=msg-config, cn=Sun ONE Messaging Suite, cn=Server Group, cn=onyx.mydomain.ab.ca,
ou=mydomain.ab.ca, o=NetscapeRoot"
local.ldapsiecred="[Dq;nkh=vm"
local.ugldaphost=onyx.mydomain.ab.ca
local.ugldapport=391
local.ugldapbasedn="dc=mydomain,dc=ab,dc=ca"
local.ugldapdeforgdn="o=mydomain.ab.ca,dc=mydomain,dc=ab,dc=ca"
local.ldapusessl=False
local.defdomain=mydomain.ab.ca
You may have pointed out the problem though. I tried doing an ldapsearch and I don't get any errors but I also don't get any results. I even tried a search on the entire objectclass and didn't get a return.
This is the search I used:
ldapsearch -h onyx.mydomain.ab.ca -p 391 -b "dc=mydomain,dc=ab,dc,ca" -s sub "objectclass=*"
Port 391 is the port I assigned to the new instance I created.
Don
Don
# 3
[24/Jul/2006:13:37:32 -0600] conn=0 op=0 msgId=1 - BIND dn="cn=msg-config, cn=Sun ONE Messaging Suite, cn=Server Group, cn
=onyx.mydomain.ab.ca, ou=mydomain.ab.ca, o=NetscapeRoot" method=128 version=2
[24/Jul/2006:13:37:32 -0600] conn=0 op=0 msgId=1 - RESULT err=32 tag=97 nentries=0 etime=0
err=32 means, "object class violation".
sounds like this ldap server doesn't have the path to the user, even.
Either configure messed up, or something of that order. You might want to re-run the configure step.
# 4
Hi Jay,
Thanks, I have rerun the configure script many times trying different things and I always get the same result.I am thinking that the problem may be in the netscaperoot. Do you know what to look for in that for where it points to the users/groups?
I didn't have any of this kind of trouble with my test setup but for it I didn't try to export/import the netscaperoot and told configure to use the old instance for config and the new instance for usrs/group.
I am thinking I may open a new support case but for directory instead.
One question though...can I run the dss_setup.pl script against the original directory without messing up the schema for iMS 5.2? If this will work then I might go that route so I can get this running.
BTW...the error I get when I try to restore a backup on the original instance of the directory is that something in the directory has changed and then it would crater. Support was never able to come up with a solution.
Thanks again,
Don
# 5
running dssetup against your old DS should not affect your current installation. It won't remove anything.
Most sites use db2ldif for backup, honestly.
I would NOT restore an o=netscapeRoot over an install. Since DS keeps configuration data there, restorin such can certainly cause a DS to refuse to start.
Bit of a safety tip...
Stop the DS. Back up the files.
that's also a valid backup. you do need to stop the DS, first, though, or it may not start....
# 6
Hi Jay,
I do use db2ldif. The problem of not being able to restore a backup started after I migrated from 4.16. Once support gave up on it I made a cronjob that tars the entire serverroot every night in addition to using db2ldif.
If I had my way I would blow the whole thing away and start from scratch but my boss was less than impressed with this idea!
The suggestion of exporting and importing the o=netscaperoot was from tech support. He figured that once we got the new system running we could remove the old instance, change the port and then all would be good. I was pretty sure I had read before that you couldn't do that with the netscaperoot but he said it was a piece of cake!
I think I will look into running the dss_setup against the old instance and then open a new case for the backup issue.
Another question. When I run the migration tools with 6.2, does that not mess up the old 5.2? Just curious since one of the tools does something with the mailstore so I am wondering if it makes it unusable for 5.2 Just being careful that I still have a server if something else goes wrong with my 6.2 install.
Thanks
Don
# 7
Well, I never claimed to be a Directory expert. . .
If you're pointing the 6.2 instance to the old 5.2 store, then, yes. The store will become incompatible with the old 5.2. We've revved the database.. ..
Other than that, I'm not exactly sure what you mean by "migration tools".
# 8
Hi Jay,I'm refering to the steps in the post install where you run the UpgradeMsg5toMsg6.pl script One of the subscripts in there deals with the mboxlist database.Don
# 9
basically a reconstruct -m.Yes, that makes the store incompatible with 5.2
