16.7 Troubleshooting

16.7.1 Same Tree Scenario

The Migration Tool File System GUI, Volume Information Tab Displays Empty Boxes for Non-English Directory Names.

In the Migration Tool file system GUI, the Volume Information tab displays empty boxes for non-English directory names.This issue occurs if the corresponding language is not installed on the source server.To install fonts for non-English languages, run yast2 language, then select languages in the Secondary Languages pane. After installing the required languages, restart the migration project.

Error nbackup: open file

Open files on the source server are not migrated. If files are open, they are not migrated because this causes data inconsistencies.

Close the files and then perform the migration.

Error nbackup: execute only files

nbackup encountered files with the Execute-only bit set. By default, these files are not copied.

If you want to copy the Execute-only files, use the tsafs /ExcludeExecuteOnly=0 setting on the source NetWare server.

Error nbackup: A file cannot be read and nbackup: Failed to read dataset

Source volumes or the target volumes are unavailable or are renamed during migration.

Do not rename volumes when migration is in progress. If migration stops because a volume is unavailable, ensure that the volume is properly activated and mounted, then restart the migration project.

16.7.2 Different Tree Scenario

Ownership Information Is Changed when Migrating from NSS to NCP

If the ownership information is changed when migrating from NSS to NCP, ensure that you LUM-enable the users that are migrated into the target eDirectory tree before you run the migfiles command.

If you LUM-enabled the users that were migrated into the target eDirectory tree and still don’t see the proper ownership information (for example, the owner is nobody as viewed in POSIX, or the server name as viewed by the Novell Client), try the following:

  1. At the OES 11 server terminal prompt, enter namcd cache_refresh.

  2. Synchronize the eDirectory replicas by using DSREPAIR.

  3. Enter nsscon /resetidcache.

  4. To verify the information of the owner, enter:

    ls -l /usr/novell/NCP1

16.7.3 General Issues

Migration GUI Throws Java Null Pointer Exception on Completion of File System Migration or Sync

The java null pointer exception has no impact on the functionality, you can ignore this exception.

File System Migration Fails with FATAL error: nbackup command failed to complete

There might be two admin users in the system (local admin user and eDirectory admin user). The failure was caused because the local admin user, which does not have permission, was trying to perform file system migration.

To resolve this issue, delete or rename the local admin user, then perform file system migration.

File System Migration Fails When TSAFS Is Set to Netware Mode on a OES 11 Server

To resolve this issue, set the parameter tsamode to Linux in the /etc/opt/novell/sms/tsafs.conf file.

When You Configure the File System GUI, an Error Is Displayed that the Volumes on the Source Server (NetWare 6.0 or Later) Are Not Mapped

If the Novell Client fails, the volumes on the source server are not mapped. The file system migration does not depend on the Novell Client commands, but it uses nwmap to map the source volumes. The details of the error is logged are /var/opt/novell/migration/<project name>/log/filesystem.log.

To troubleshoot this issue, perform the following:

  1. Verify the status of the Novell Client by entering the following command:

    rcnovfsd status

    1. If the service is running, restart the service by entering the following command:

      rcnovfsd restart

      or

      If the service is not running, start the service by entering the following command:

      rcnovfsd start

    2. To configure the file system, select the file system and click Configure.

  2. (Conditional) If the error is displayed again, verify the status of the novell-xregd service by entering the following command:

    rcnovell-xregd status

    1. If the status is running, restart the service by entering the following command:

      rcnovell-xregd restart

      or

      If the status is not running, start the service by entering the following command:

      rcnovell-xregd start

    2. Restart the Novell Client by entering the following command:

      rcnovfsd restart

    3. To configure the file system, select the file system, then click Configure.

  3. (Conditional) If the error is displayed after restarting the novfsd and novell-xregd services, refer to the log file to verify whether the Novell Client has failed to resolve the IP address.

    1. If the IP address was not resolved, create a /etc/opt/novell/ncl/protocol.conf file and add the following line: Name_Resolution_Providers=NCP,SLP,DNS

    2. Restart the Novell Client by entering the following command:

      rcnovfsd restart

    3. To configure the file system, select the file system, then click Configure.

When You Start Migration, an Error Is Displayed and Migration Fails

When you click Start in the main migration window, migration fails and you receive the error that no data sets are found.

Source Server is OES 1

Migration might fail if smszapi is not loaded on the source server. To troubleshoot this issue, perform the following:

  1. Verify that smszapi is loaded on the source server by executing the following command:

    lsmod | grep smszapi

  2. (Conditional) If smszapi is displayed in the list, update the smszapi.

  3. (Conditional) If smszapi is not displayed in the list, restart SMDR.

    novell-smdrd restart

  4. Click Migrate to start the migration.

Source Server is OES 2 or OES 11

Migration might fail if there is a problem during the setup and zapi is not loaded on the source server. To troubleshoot this issue, perform the following:

  1. Verify that zapi is loaded on the source server by executing the following command:

    lsmod | grep zapi

  2. (Conditional) If zapi is displayed in the list, then update the zapi.

  3. (Conditional) If zapi is not displayed in the list, restart SMDR.

    novell-smdrd restart

  4. Click on Start, to begin the migration.

Migration Fails Due to Failure of the migtrustees Command

The migtrustees command fails with a fatal error, which is recorded in the filesystem.log file.

The migtrustees command takes input from the maptrustees.yaml file, which includes various attributes. Some special characters are included in the loginScript attribute of the maptrustees.yaml file, which is not recognized by the migtrustees command causing a failure in the migration.

To troubleshoot this issue, perform the following:

  1. Open the iManager page on the source server.

  2. Click Users > Modify Users.

  3. Select the user name that has special characters in the login script.

    For example, if you see the error for cn=testuser,ou=users,o=novell in the filesystem.log file, select testuser from the user list.

  4. Click General > loginScript.

  5. Remove the special characters from the login script.

  6. Click apply > > ok.

  7. Remove the migtrustees.session, maptrustees.session and maptrustees.yaml files from the /var/opt/novell/migration/<Project name>/fs/ folder of the target server.

    This ensures that the maptrustees command is re-executed when continuing the migration process.

  8. Click Start on the main Migration Tool window of the target server to continue the migration.

Not Getting the Code Page and Non-English Characters

Migrating from NetWare 6.5 or Later

The language pack is not installed on the target server, so the code page and the non-English characters are not displayed.

You need to install the language pack of the source server on the target server before starting the Migration Tool.

Source Cluster Volumes Are Not Displayed

This issue occurs because the Is Cluster Resource option is not selected in Source Server Authentication or because the cluster resource is down.

If the Is Cluster Resource option is not selected, select the option from Source Server Authentication, then reconfigure.

or

If the Is Cluster Resource option is selected and the cluster volumes are not displayed, verify the list of cluster volumes by executing the following command:

/opt/novell/sms/bin/smstool --list-cluster-volumes -R <resourceIP> -U <admin_credentials>

Files or Trustees Are Not Synchronized

If files are open on the source server during synchronization, those files are not synchronized with the files on the target server. If trustees are deleted on the source server during or before synchronization, the trustees are not migrated. Ensure that you verify the following before synchronizing, then click Sync.

  • No application or user is accessing the source volumes that are being copied.

  • Select disable login in the file system GUI to restrict access to the source volumes.