On RSA Via Lifecycle and Governance the aveksa_server start returns message: Cannot connect to the database, but the DB is up
Originally Published: 2016-05-24
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0 and higher
Issue
$ service aveksa_server start
Cannot connect to the database. The watchdog will start the server when it can connect to the database.
However, the database can be successfully connected to from SQL*Plus and is showing as up with the aveksa_server statusdb option:
$ service aveksa_server statusdb 15817 Database is running.
Cause
Resolution
Related Articles
Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201… Number of Views How to connect to SQL in RSA Authentication Manager 8.x Number of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' Number of Views AFX Server Fails to Start with 'Could Not Build a Validated Path' and 'Timed Out Waiting for AFX Applications to Start' in… Number of Views RSA Authentication Manager - License Installation Fails with 'License/Serial Number Does Not Match' Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide Module "SecurIDModule" could not be found message displayed in the web browser
Don't see what you're looking for?
