Server unreachable after restart or update Web UI Code 500
Inhaltsverzeichnis
Applies to:
Cryptshare Appliance version 4.7.0
Symptom:
If the Cryptshare Appliance does not respond after updating your system or not automatically loads its service after reboot, you have to restore your system manually. and the following message in the logs
ERROR 2021-05-07 08:02:15 HikariPool - springHikariCP - Exception during pool initialization.
org.h2.jdbc.JdbcSQLNonTransientException: General error: "java.lang.IllegalStateException: Chunk 156871 not found [1.4.200/9]" [50000-200]
Cause:
The source for the issues is that the database was not terminated properly.
Solution:
To solve this, an empty database must first be used to access the admin interface again. Afterwards you have to restore the last backup. Another option is to import an existing snapshot of your machine. Please perform the update again.
Solution
# Log in as root on your appliance (ssh e.g. with Putty)
Execute the following commands:
# systemctl stop cryptshare
# Rename the database:
mv /opt/cryptshare-3/db /opt/cryptshare-3/db.bak
# sytemctl start cryptshare
# Open the administration interface of your new appliance and login.
# Navigate to the restore dialog in "Backup/Restore".
# Check your backup directory path
# Check all restore options in "CONTENT AVAILABLE FOR RESTORING" and click "Restore Backup".
# Your new appliance will automatically reboot and recover your data.
Please log in with the restored "Administrator" credentials.
Execute the following commands:
# systemctl stop cryptshare
# Rename the database:
mv /opt/cryptshare-3/db /opt/cryptshare-3/db.bak
# sytemctl start cryptshare
# Open the administration interface of your new appliance and login.
# Navigate to the restore dialog in "Backup/Restore".
# Check your backup directory path
# Check all restore options in "CONTENT AVAILABLE FOR RESTORING" and click "Restore Backup".
# Your new appliance will automatically reboot and recover your data.
Please log in with the restored "Administrator" credentials.
Related Articles
Error code 5000
Applies to: All versions of Cryptshare for Notes Situation: Error code 5000 in Cryptshare for Notes application Cause: This error code occurs, if the Domino Server and the Cryptshare Server cannot establish a connection. Solution: Check Firewall, ...Restart the Cryptshare service during update process
Applies To All versions of the Cryptshare Server Problem During the Cryptshare update it is unclear whether the update process is still running. Cause This can happen if the database is large and the update process makes changes to the database after ...Failed to prepare update
Inhaltsverzeichnis 1 Applies To 2 Problem 3 Cause 4 Solution Applies To In case that you initiate an update from version 6.2.x and encounter problems while preparing the update Problem ERROR UpdateController - Failed to prepare update. ...Cryptshare service is not starting on Linux server
Applies to: Cryptshare Server version 4.0.0.0 to 4.1.3.0 Symptom: The Cryptshare Service doesn't start after updating Cryptshare Server from version 4.0.0.0 to 4.1.x.x . Cause: The upgrade process cannot adjust the custom configuration during the ...The Cryptshare Server becomes unresponsive under high load.
Applies to: All versions of Cryptshare Server Symptom: The Cryptshare Server responds slowly when it is used by a large amount of users at a time. Cause: The Cryptshare Server tries to respond to all requests but cannot answer the requests faster ...