000028135 - KB-1242 - Migration Required / No Authentication Source Error

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000028135
Applies ToAffected Versions: All Versions
ResolutionPlease check the following items to resolve the Migration Required error, these are the most common reasons in order of occurrence.
1. Check for two copies of the Aveksa server running
A. Stop the server
 
sudo service aveksa_server stop
 

B. On 3.X systems also stop the agent
 
sudo service aveksa_agent stop
 

C. Check for another server instance running using the command:
ps -ef | grep jboss (version 4.X)
ps -ef | grep tomcat (version 3.X)
D. If step C produces output with a running process as root kill the process:
 
kill -9 <pid>

E. Restart the aveksa_server, and on version 3.X the agent
 
sudo service aveksa_server start
sudo service aveksa_agent start (version 3.X only)

F. If still and issue continue with the steps below
2. No space on device
A. Check root partition with "df" command
B. On Aveksa built appliances check the ASM partition with following commands:
export ORACLE_SID=+ASM

asmcmd lsdg
This will provide the FREE_MB and Total_MB if you have less than 10%
free run the cleanup script /home/oracle/database/DBA/AVDB/scripts/ASM_Cleanup.sh (note not required on 4.1 and above, if you are out of space contact Aveksa)
C. Stop the aveksa_server / agent
 
sudo service aveksa_server stop
sudo service aveksa_agent stop (version 3.X only)
 

D. Stop and restart the database
 
sudo service dbora restart

E. Restart the aveksa_server / agent
 
sudo service aveksa_server start
sudo service aveksa_agent start (version 3.X only)

3. Corrupted test authentication provider.
If using the "TestAuth" provider to allow access to the appliance without valid passwords, this can become corrupted and cause the errors on the login page. The easiest thing to do is to delete the TestAuthProvider in the database. Assuming you have only 1 TestAuth provider
A. delete the provider using this SQL:
 
delete from T_AUTH_CONFIGURATIONS where AUTH_PROVIDER_NAME='TestAuthProvider';

commit;

B. Restart the aveksa_server / agent
 
sudo service aveksa_agent stop (version 3.X only)
sudo service aveksa_server restart
sudo service aveksa_agent start (version 3.X only)

4. Mismatch in versions (you may be able to log-in)
A. Determine the version of the software installed on the machine by looking in the version.properties file and determine the Build and Version.
3.6.X Location:
/usr/bin/tomcat/webapps/aveksa/WEB-INF/classes/version.properties

4.0 locations:
/home/oracle/database/version.properties

/home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/classes/version.properties
WAS - 3.X location:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/<node>Node01Cell/aveksa.ear/aveksa.war/WEB-INF/classes/version.properties
B. Start SQL*Plus and run the queries below to fine the database version and buid
sqlplus avuser/secret
 
SQL> SELECT * FROM T_SYSTEM_SETTINGS WHERE PARAMETER='productVersion';
SQL> SELECT * FROM T_SYSTEM_SETTINGS WHERE PARAMETER='Build';

C. if there is a miss-match change the dB using the update command, for example:
 
UPDATE T_SYSTEM_SETTINGS set VALUE =('xxxxx') where PARAMETER='Build';

5. Duplicate tasks in T_SCHEDULED_TASKS (usually after an upgrade)
The system will not start if there are tasks duplicated in the database, the following sql can be used to determine if there are any dupes:
 
SELECT ID,NAME from T_SCHEDULED_TASKS where NAME NOT LIKE '%CR %' OR NAME NOT LIKE '%Escalate%' OR NAME NOT LIKE '%Review%' OR NAME NOT LIKE '%Activity%' ORDER BY NAME;

Usually the "gatherDatabaseStatistics" task is duplicated because some patches don't check and just install another row. Remove the latest one and restart the server.


6. The Correct patches are missing

This usually happens after a database restore and or reboot. There is a mismatch between
what patches the system thinks are installed and what really is installed. - Just
re-apply the current or latest patch.


7. Plugins.jar files is missing
If you use a special plug-in and it's referenced in the restored dump but it's not available on the system where you did the restore, the places to install the jar files are:
 
3.X /usr/bin/tomcat/common/lib

4.X /home/oracle/jboss/server/default/lib/

8. Corrupted packages
Usually after a restart of a system that has been up and running, patches may have been installed or packages added removed.Look in the server.log / catalina.out - you may see NPE (null pointer exception) for logins but the login is successful but you still get the log-in screen with the error. Try this:
A. Change directories to /home/oracle/database
B. Start SQL*Plus
sqlplus avuser/secret
C. Run these commands (dont type the "SQL>")
 
SQL> @Rebuild_Packages.sql
SQL> @Recompile_Invalid_Views.sql
SQL> execute Report_Views_Pkg.Create_AV_Report_Views
SQL> @Rebuild_Packages.sql
SQL> @Recompile_Invalid_Views.sql

D. Manually recompile any triggers needed
 
ALTER TRIGGER <trigger name> COMPILE;
 

E. Restart the server / agent
 
sudo service aveksa_agent stop (version 3.X only)

sudo service aveksa_server restart
sudo service aveksa_agent start (version 3.X only)
 



9. Run the migration script
Try re-running the migration script which can be found in
 
/home/oracle/deploy/migrate.sh

 

10. None of the above work
If there are still problems, please tail the application server log during a log-n attampt, the logs can be found at:


 


3.X /usr/bin/tomcat/logs/catalina.out


4.X /home/oracle/jobss/server/default/log/server.log


 


Take the output and open a case with Aveksa Support. 

Attachments

    Outcomes