login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
Article ID: 239175
Updated On:
Products
Issue/Introduction
AAI JAWS version: 6.4.1-2
In jaws.log file we see following messages repeated
Line 18400: 2022-02-22 16:25:50,719 INFO [JawsRestApiCaller] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
Line 18716: 2022-02-22 16:32:14,552 INFO [JawsRestApiCaller] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
Line 18760: 2022-02-22 16:37:37,773 INFO [JawsRestApiCaller] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
Line 18806: 2022-02-22 16:42:51,894 INFO [JawsRestApiCaller] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
'admin' userid exists
Server.log will show the following 24 hours after either changing the admin password or upgrading from a 5.x release.
ERROR [org.jboss.as.controller.OperationContextImpl] WFLYCTL0348: Timeout after [86400] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
("core-service" => "management"),
Environment
Release : 6.4.1-2
Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE
Resolution
servicePass parameter and the admin password are out of sync.
Change the admin password to something by going to File -> Change Password from the thick client while logged in as admin
Or if logged in as another user with admin rights, edit the admin password form the Admin->User Management section.
Then open the configuration tool, go to Parameters->Hidden Parameters->Show Hidden Parameters.
Enter "servicePass" and enter the password you just changed the admin password to.
Additional Information
Note this error may be okay if the AAI system is still initializing. If there message persists after the first jammer cycle completes this likely needs attention.
Feedback
