The problem may be is caused by missing permissions that are necessary for the initial schema creation process. This part is completed when one runs through the installationProcess.sh script located in the /usr/local/Secunia/csi/install/ directory of the application server. It can also happen when an upgrade attempt fails and leaves the SVM in a "still upgrading" locked state.
-
Verify user database structure
- Check the private database associated with the server. This database follows the naming format ca_<customer_id>, where the value in angle brackets represents the customer identification number assigned to the server.
- If the database has no tables, it indicates that the Software Vulnerability Manager installation did not fully populate the private database schema.
-
Verify database user permissions
-
Ensure that the database user has sufficient privileges to create and modify the schema.
-
For local installations, it is recommended to use the root user for MySQL or MariaDB.
-
If remote access is required, create a record allowing access for the appropriate host.
-
Use the following commands to grant access privileges:
grant all privileges on *.* to 'root'@'hostname' identified by password 'password' with grant option; flush privileges;If short and fully qualified hostnames are both in use, create records for each name.
To allow access from all hosts (not recommended for all organizations for security reasons), run:grant all privileges on *.* to 'root'@'%' identified by password 'password' with grant option; flush privileges;
-
-
Check database status and patch level
-
If the issue persists and is unrelated to permissions, verify the status of the ca database:
select * from ca.csi_pdb_info; -
Review the patch level information. If it is outdated, manually run the upgrade to bring the instance to the current patch level.
-
-
Unlock the Software Vulnerability Manager database
-
If the database remains locked, look for the cust_id with the column Locked set to 1 in the ca.csi_pdb_info table.
-
To unlock it, execute the following command:
update ca.csi_pdb_info set locked = '0' where locked = '1'; -
Restart the MySQL or MariaDB service. Once restarted, the login process should succeed.
-
The Software Vulnerability Manager server becomes unlocked and the user can log in successfully.
Additional Information
Connect to a MySQL database remotely
https://mariadb.com/kb/en/mariadb/configuring-mariadb-for-remote-client-access/
Related Articles
SVM On-Prem Sync Failures [Can't Login SVM Account] 23Number of Views Configure SVM On-Prem Server with SSL/TLS1.2 14Number of Views Update your proxy settings for Software Vulnerability Manager On-premises 16Number of Views Managing SVM On-Prem Backups and Logs 9Number of Views Resolve error 0x800b0109 when installing third-party updates 11Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago