Key Manager Server migration appears to hang after logging 'Migrating AUTH_INTERNAL...' in migrate.log
2 years ago
Originally Published: 2010-10-22
Article Number
000048145
Applies To
RSA Key Manager Server Migration Utility 2.7.1.1
Redhat Linux
Issue
Key Manager Server migration appears to hang after logging "Migrating AUTH_INTERNAL..." in migrate.log
The last few lines in migrate.log are as follows:

2010-10-14 12:42:44,149 INFO Main Thread - Client : Internal, testCipher
2010-10-14 12:42:44,150 INFO Main Thread - Client : Internal, generateKey() - About to get key
2010-10-14 12:42:45,572 INFO Main Thread - Client : Internal, generateKey() - Obtained key
2010-10-14 12:42:45,707 INFO Main Thread - Client : Internal, Migrating database objects...
2010-10-14 12:42:45,707 INFO Main Thread - Client : Internal, Migrating IDENTITY_GROUP...
2010-10-14 12:42:46,047 INFO Main Thread - Client : Internal, Migrated 6 IDENTITY_GROUP objects.
2010-10-14 12:42:46,047 INFO Main Thread - Client : Internal, Migrating IDENT...
2010-10-14 12:42:46,052 INFO Main Thread - Client : Internal, Migrated 22 IDENT objects.
2010-10-14 12:42:46,053 INFO Main Thread - Client : Internal, Migrating IDENT...
2010-10-14 12:42:46,056 INFO Main Thread - Client : Internal, Migrated 1 IDENT object.
2010-10-14 12:42:46,056 INFO Main Thread - Client : Internal, Migrating ROLE_MEMBERSHIP...
2010-10-14 12:42:46,060 INFO Main Thread - Client : Internal, Migrated 22 ROLE_MEMBERSHIP objects.
2010-10-14 12:42:46,060 INFO Main Thread - Client : Internal, Migrating ROLE_MEMBERSHIP...
2010-10-14 12:42:46,061 INFO Main Thread - Client : Internal, Migrated 1 ROLE_MEMBERSHIP object.
2010-10-14 12:42:46,061 INFO Main Thread - Client : Internal, Migrating AUTH_INTERNAL...
Cause
The migration tool, migrate.sh, was run from command shell as a background process so the password prompt for 'migrator' user that should show up on the command shell did not appear.
Resolution
Delete 'output' folder under the migration tool folder and run migrate.sh again on the command shell, ensuring that it is not run as a background process.  The following prompt should show up on the command shell right after logging "Migrating AUTH_INTERNAL..." in migrate.log:

Select password for 'migrator' administrator:

Provide a password on the prompt for 'migrator' user to carry on with the migration process.
Workaround
Migrating RSA Key Manager Server from version 2.1.2 to 2.7SP1 using RSA Key Manager Server Migration Utility 2.7.1.1