UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
3136 views

OES2-SP3 -> OES11 migration got stuck

A couple of OES2SP3-32bit migrations to OES11 worked as expected as a Transfer-ID scenario with iprint and and file system services included.

Now doing the same on other well prepaired systems the migration gui tool got stuck when the file system service should be configured. Last entry in the debug.log file is

2012-08-29 14:04:18,304 DEBUG - 2> Information: ldapsearch command executed as "ldapsearch -LLL -s sub -H ldaps://<source-ip> -x -D "cn=admin,o=wfb" "(&(CN=SERV-Win-1_*)(objectClass=Volume))" linuxNCPMountPoint -W"

If I kill the corresponding process the file system configuration dialog comes up without showing the source volume.

Any ideas?

Ferdinand
Labels (1)
0 Likes
18 Replies
Absent Member.
Absent Member.

$(UHave you applied the April 2012 OES11 patch?


-Ramesh


>>> fgiese<fgiese@no-mx.forums.novell.com> 08/29/2012 06:06 PM >>>


A couple of OES2SP3-32bit migrations to OES11 worked as expected as a
Transfer-ID scenario with iprint and and file system services included.

Now doing the same on other well prepaired systems the migration gui
tool got stuck when the file system service should be configured. Last
entry in the debug.log file is

2012-08-29 14:04:18,304 DEBUG - 2> Information: ldapsearch command
executed as "ldapsearch -LLL -s sub -H ldaps://<source-ip> -x -D
"cn=admin,o=wfb""(&(CN=SERV-Win-1_*)(objectClass=Volume))"
linuxNCPMountPoint -W"

If I kill the corresponding process the file system configuration
dialog comes up without showing the source volume.

Any ideas?

Ferdinand


--
fgiese
------------------------------------------------------------------------
fgiese's Profile: http://forums.novell.com/member.php?userid=6127
View this thread: http://forums.novell.com/showthread.php?t=459425




0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Yes, source and target servers are fully patched.

Ferdinand
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

fgiese;2215971 wrote:
Yes, source and target servers are fully patched.

Ferdinand


We've run into issues with OES11 miggui as well where it won't see the OES2 SP3 NSS volume even when it DOES have the correct attribute AND when the LDAP search query (executed manually) returns the volume list properly.

We never found a fix, and ended up just manually copying the data over and manually restoring the trustee rights with the metamig.

Still have the SR open, but that was kinda after the fact.
0 Likes
Absent Member.
Absent Member.

$(UDid you try executing manually ldapsearch recorded in the logs from command prompt to see it hangs or not?

Probably you can try out workaround for miggui to display source volumes to configure. Here are the steps:

1. mount source volume using the below command:
ncpmount -A <sourceIP> -S <targetIP> -U <ndsAdminUserName> -P <ndsAdminPassword> -V <sourceVolumeName> <targetPath>

targetPath - Should be the projectfolder/fs/mnt/source/<sourceVolumeName>

Ex: ncpmount -A 10.1.1.10 -S 10.1.1.10 -U admin.org -P password -V VOL1 /var/opt/novell/migration/NewProj0/fs/mnt/source/VOL1

2. Launch miggui>configure>FileSystem. The mounted volume will be displayed.

3. Once FS migration is configured,close the UI (not miggui). Unmount the mounted volumes.

4. Start the file system migration.

These steps are documented in the admin guide at section 16.7.3.4 @ http://www.novell.com/documentation/oes11/mig_tools_lx/?page=/documentation/oes11/mig_tools_lx/data/bookinfo.html#bookinfo


-Ramesh


>>> fgiese<fgiese@no-mx.forums.novell.com> 08/29/2012 08:16 PM >>>


Yes, source and target servers are fully patched.

Ferdinand


--
fgiese
------------------------------------------------------------------------
fgiese's Profile: http://forums.novell.com/member.php?userid=6127
View this thread: http://forums.novell.com/showthread.php?t=459425




0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Thanks Ramesh for your support but after starting file system transfer, miggui get stuck as well.

In my despair, I decided to upgrade my target server to OES11-SP1 and SLES11-SP2. After successfull operation and starting miggui one more time the process stopped again during file system configuration. But now there is another message in the /var/opt/novell/migration/proj0/log/debug.log as listed below.

-------------------------
2012-09-06 16:14:14,327 DEBUG - MigrationProcess:Cleanup() called: null
2012-09-06 16:14:14,327 DEBUG - After cleanUp() .. this.enablePID= false this.pID = 0
2012-09-06 16:14:14,327 DEBUG - MigrationProcess:ExecuteProcess() returning 0
2012-09-06 16:14:14,327 DEBUG - rcnovell-xregd status return value: 0
2012-09-06 16:14:14,328 DEBUG - MigMount Command ruby /opt/novell/migration/sbin/volmount.rb -s 192.168.40.8 -a "cn=admin,o=wfb" -c Not Applicable -f "/var/opt/novell/migration/NewProj0/fs/mnt/source" -m -t OES20
2012-09-06 16:14:14,335 DEBUG - MigrationProcess:ReadStdOut:run() in the run method
2012-09-06 16:14:14,336 DEBUG - MigrationProcess:ReadStdErr:run() in the run method
2012-09-06 16:14:14,525 DEBUG - 2> Information: ncpmount using code page
2012-09-06 16:14:23,226 DEBUG - 2> Information: ldapsearch command executed as /opt/novell/eDirectory/bin/ldapsearch -x -h 192.168.40.8 -s base -b "" | grep 2.16.840.1.113719.1.513.7.1
2012-09-06 16:14:25,421 DEBUG - 2> Error: ldapsearch either failed to execute or return nil. Unable to identify 192.168.40.8 as DSfW server.
2012-09-06 16:14:25,421 DEBUG - 2> Information: ldapsearch command executed as "ldapsearch -LLL -s sub -H ldaps://192.168.40.8 -x -D "cn=admin,o=wfb" "(&(CN=SERV-Win-1_*)(objectClass=Volume))" linuxNCPMountPoint -W"
--------------------------------

Manually executing the ldapsearch command, listed above the error message returns no result. Perhaps this maybe a hint to solution.

--Ferdi
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

fgiese;2217628 wrote:
Thanks Ramesh for your support but after starting file system transfer, miggui get stuck as well.

In my despair, I decided to upgrade my target server to OES11-SP1 and SLES11-SP2. After successfull operation and starting miggui one more time the process stopped again during file system configuration. But now there is another message in the /var/opt/novell/migration/proj0/log/debug.log as listed below.

-------------------------
2012-09-06 16:14:14,327 DEBUG - MigrationProcess:Cleanup() called: null
2012-09-06 16:14:14,327 DEBUG - After cleanUp() .. this.enablePID= false this.pID = 0
2012-09-06 16:14:14,327 DEBUG - MigrationProcess:ExecuteProcess() returning 0
2012-09-06 16:14:14,327 DEBUG - rcnovell-xregd status return value: 0
2012-09-06 16:14:14,328 DEBUG - MigMount Command ruby /opt/novell/migration/sbin/volmount.rb -s 192.168.40.8 -a "cn=admin,o=wfb" -c Not Applicable -f "/var/opt/novell/migration/NewProj0/fs/mnt/source" -m -t OES20
2012-09-06 16:14:14,335 DEBUG - MigrationProcess:ReadStdOut:run() in the run method
2012-09-06 16:14:14,336 DEBUG - MigrationProcess:ReadStdErr:run() in the run method
2012-09-06 16:14:14,525 DEBUG - 2> Information: ncpmount using code page
2012-09-06 16:14:23,226 DEBUG - 2> Information: ldapsearch command executed as /opt/novell/eDirectory/bin/ldapsearch -x -h 192.168.40.8 -s base -b "" | grep 2.16.840.1.113719.1.513.7.1
2012-09-06 16:14:25,421 DEBUG - 2> Error: ldapsearch either failed to execute or return nil. Unable to identify 192.168.40.8 as DSfW server.
2012-09-06 16:14:25,421 DEBUG - 2> Information: ldapsearch command executed as "ldapsearch -LLL -s sub -H ldaps://192.168.40.8 -x -D "cn=admin,o=wfb" "(&(CN=SERV-Win-1_*)(objectClass=Volume))" linuxNCPMountPoint -W"
--------------------------------

Manually executing the ldapsearch command, listed above the error message returns no result. Perhaps this maybe a hint to solution.

--Ferdi


Check out TID #7008693

Usually if ldapsearch (manually) returns nothing it's because the source server volume object in eDir is missing the attribute.
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

After some vacation days, I started investigation with fresh brain and new ideas. Performing data migration with command line utilities should give me some hints for eliminating the error and perhaps it did.

After confirming the server requirement (source and target) I ran the mls command from the target server console (mls -s <ip-of-source-server> -V <NSS-Volume> > mls.yaml) and got same error posted above. Changing the ip to the local address of the target server resulted in same error. Everything worked well, if I executed same commands from the source server.

My conclusion points me to the target server to check services and configuration. But I have no idea where I must begin. Hope You can give any advice.

Thanks
--Ferdi
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Some new migration tests on the target server let me have a more exactly look on one the stucking mls command and its processes. When I do a "ps aux | grep mig" during mls process I got following output:

-------------
22346 0.0 0.1 12748 1404 pts/1 Ss+ Sep17 0:00 sh -c ldapsearch -LLL -s sub -H ldaps://192.168.60.8 -x -D "cn=admin,o=wfb" "(&(CN=SERV -w "xxxxxx"ar-1_*)(|(objectClass=Volume)(objectClass=ndsVolume)))" linuxNCPMountPoint -W 2>/tmp/mig-err.txt>&1
-------------

Killing this process will free the console. Having a look at the expression in brackets starting with CN=Serv there might be something wrong because the target server name is SERV-War-1. It seems that the password expression is included into the server's name and that might the cause of my problem. Not knowing where I can correct this expression, I need your help.

Thanks
--Ferdi
0 Likes
Absent Member.
Absent Member.

$(UHave you applied the OES11 oes11-April-2012-Hot-Patch from OES11-Updates catalog?
Looks like a ruby issue and this patch has the fix.

FYI: When you post install and upgrade OES11 on a fully patched SLES 11 SP1, you are likely to get ruby conflict error. Then in that case choose
Solution 3: break ruby-devel by ignoring some of its dependencies

and continue with installation.


-Ramesh


>>> fgiese<fgiese@no-mx.forums.novell.com> 09/18/2012 12:46 PM >>>


Some new migration tests on the target server let me have a more exactly
look on one the stucking mls command and its processes. When I do a "ps
aux | grep mig" during mls process I got following output:

-------------
22346 0.0 0.1 12748 1404 pts/1 Ss+ Sep17 0:00 sh -c
ldapsearch -LLL -s sub -H ldaps://192.168.60.8 -x -D "cn=admin,o=wfb"
"(&(CN=SERV -w
"xxxxxx"ar-1_*)(|(objectClass=Volume)(objectClass=ndsVolume)))"
linuxNCPMountPoint -W 2>/tmp/mig-err.txt>&1
-------------

Killing this process will free the console. Having a look at the
expression in brackets starting with CN=Serv there might be something
wrong because the target server name is SERV-War-1. It seems that the
password expression is included into the server's name and that might
the cause of my problem. Not knowing where I can correct this
expression, I need your help.

Thanks
--Ferdi


--
fgiese
------------------------------------------------------------------------
fgiese's Profile: http://forums.novell.com/member.php?userid=6127
View this thread: http://forums.novell.com/showthread.php?t=459425




0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

This issue appears after upgrading target server to SLES11-SP2 and OES11-SP1. I supposed that this hotfix is included in that service pack. But is it?

Perhaps I will get a chance to migrate without errors, if I install the April-Hotpatch and break dependences.

Thanks a lot
--Ferdi
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Now my confusion is complete. We got same issue after downgrading to the April-Hotpatch but we succeded in performing the mls process with another server of same patch level. The ps command gave the right syntax of ldapsearch as follows:

-------------
root 25511 0.0 0.1 12612 1520 pts/3 Ss+ 08:00 0:00 sh -c ldapsearch -LLL -s sub -H ldaps://192.168.90.8 -x -D "cn=admin,o=wfb" "(&(CN=SERV-Sel-1_*)(objectClass=Volume))" linuxNCPMountPoint -w xxxxxx 2>/tmp/mig-err.txt>&1
-------------

I haven't got any idea where to search for a solution.

--Ferdi
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.