000035030 - Upgrade of RSA Identity Governance and Lifecycle from earlier versions to 7.0.2 fails during WildFly configuration phase.

Document created by RSA Customer Support Employee on May 1, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035030
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.2
Platform: WildFly 
 
IssueThe upgrade fails during the WildFly server configuration process when upgrading to RSA Identity Governance and Lifecycle 7.0.2 from a lower version.
The following events will be recorded in the /tmp/aveksa-install.log:
 
[Mon Apr 3 12:20:35 CDT 2017] Configure Wildfly Server...
Configure Wildfly...
[Mon Apr 03 12:20:56 CDT 2017]: checkIfWildflyRunning debug message. Outcome result - starting
[Mon Apr 03 12:21:00 CDT 2017]: Terminate session
[Mon Apr 03 12:21:00 CDT 2017]: Connecting to check connection
[Mon Apr 03 12:21:00 CDT 2017]: Authenticating against security realm: ManagementRealm
Authenticating against security realm: ManagementRealm
Username: 
[Mon Apr 03 12:21:00 CDT 2017]: JBREM000200: Remote connection failed: javax.security.sasl.SaslException:
Authentication failed: the server presented no authentication mechanisms
[Mon Apr 03 12:21:00 CDT 2017]: Terminate session
[Mon Apr 03 12:21:00 CDT 2017]: Failed to connect to server. Error message -
Unable to connect to controller.org.jboss.as.cli.CommandLineException: Unable to authenticate against controller at localhost:9990
[Mon Apr 03 12:21:00 CDT 2017]: Wildfly server is not running
[Mon Apr 03 12:21:00 CDT 2017]: Failed to configure data sources. Error message - Wildfly server is not running
[Mon Apr 03 12:21:00 CDT 2017]: Exception when configuring WildFly Wildfly server is not running
Failed to configure Wildfly
Step failed! See /tmp/aveksa-install.log for more information.

Digging deep inside the logs you will notice database errors: 
PRCR-1079 : Failed to start resource ora.avdb.db
CRS-2501: Resource 'ora.avdb.db' is disabled
Database is not running.
CauseThe cause for this error is unknown.  However, the error means WildfFy is unable to connect to the datasource, possibly because the database has been disabled from the Oracle grid.
 
Resolution
  1. Login to the server via SSH as the oracle user.
  2. Check the status of database operations.The status below shows that the database is not running :
oracle:~> acm statusoracle
1030
CRS-4638: Oracle High Availability Services is online
Database is not running.

  1. Enable the database using srvctl (Server Control Utility):
oracle@acm:~> srvctl enable database -db AVDB

  1. Start the database:
oracle@acm:~> acm startoracle

  1. Verify the database is running:
oracle@acm:~> acm statusoracle
CRS-4622: Oracle High Availability Services autostart is enabled.
CRS-4640: Oracle High Availability Services is already active
CRS-4000: Command Start failed, or completed with errors.
CRS-4638: Oracle High Availability Services is online
Database is running.

  1. Switch to root user ,cd to staging directory and resume the upgrade :
root@acm:/tmp/aveksa/staging # ./install.sh

  1. The upgrade should now complete successfully.

 
NotesImportant note:  In this case we noticed the issue with the database and provided the resolution accordingly.  However there are other scenarios or reasons that can affect the upgrade  : 
Error: 

Failed to connect to server. Error message - Unable to connect to controller.org.jboss.as.cli.CommandLineException: Unable to authenticate against controller at localhost:9990


Cause: 

The localhost entry missing from the /etc/hosts file. Trying to ping localhost would fail:
acm:~ # ping localhost
ping: unknown host localhost

Resolution:
  1. Add localhost to /etc/hosts file, using vi or another text editor:
127.0.0.1       localhost

  1. Save file.
  2. Make sure localhost is resolvable now:
acm:~ # ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.017 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.028 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.044 ms

Attachments

    Outcomes