Search Documentation
-
Deployment
-
Administrative Guide
-
- AWS S3 Storage Configuration using Access and Secret keys
- AWS S3 Storage Configuration using IAM role
- Google Storage Configuration using JSON Authentication Key
- Azure Blob/File Storage Configuration using Access Keys
- Backblaze B2 Storage Configuration using Access and Secret Keys
- DigitalOcean Storage Configuration using Access and Secret Keys
- Oracle Storage Configuration using Access and Secret Keys
-
-
Tutorials
- Quick Start
- AWS S3 File Sharing With Password Protection
- Google Cloud Storage Integration
- SSO for Admin Console using IAM Identity Center
- SSL and Load balancer for NirvaShare on AWS
- SSO for AdminConsole using Azure ActiveDirectory
- SSL Using Nginx Proxy Manager
- How to Share and Manage File Access from AWS S3, Azure Blob with Salesforce Users
- Configure SSO for Admin Console using Google Workspace as Identity Provider
- Share Azure Blob Files with ActiveDirectory Users using SSO
- S3 File Sharing with Okta Users
-
Troubleshoot
Table of Contents
< All Topics
Admin Console Server not coming up due to database lock
Behavior and Error messages
Admin Console not starting up and the error log have below errors. To get the error log, check HERE
Invocation of init method failed;
LockException: Could not acquire change log lock. Currently locked by
Cause
This happens when the server is restarted or shut down manually during the schema initialization is in progress. This is a rare scenario that occurs when the database is in a locked condition.
Solution
- SSH to Linux terminal where NirvaShare is installed, create a file with the below path and filename. Make sure you login as root user. In case if you already have this file in that location, please edit the same to add the entry.
/var/nirvashare/config.properties
- Add the below entry in to the file and save it.
ns_reset_db_lock=true
- Restart Admin Console service using below command
docker restart nirvashare_admin
- After Admin Console starts successfully, please delete the entry in the file and once again restart the Admin Console.