Restart the Cryptshare service during update process

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 starting an update of the Cryptshare Server (see Updating Cryptshare).

Solution/Workaround

  • Log in as root on the Cryptshare Appliance
  • Check the output of the log using the following command:
tail -f /opt/cryptshare-3/log/cryptshare.log
  • Additionally, you can check if the database file is still being worked on by looking at the contents and file sizes of the 'db' directory in the cryptshare installation directory.
watch du -sh /opt/cryptshare-3/db/*

If there are temporary files listed, or the database size changes from time to time, the update of the database is still ongoing.


If the update process is still running, please be patient and do not interrupt it, as doing so may cause corruption.

Only stop the Cryptshare Server if you are certain that something went wrong, or the update runs for much longer than normal (e.g. running for more than 10 minutes). In this case, please restore the backup from before the update was installed, as the Cryptshare Server may be in an inconsistent state.

    • Related Articles

    • 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 ...

    • Updating Cryptshare manually

      Applies to: Cryptshare Server from version 4.2.x Purpose: This is an example of the possibilities for updating Cryptshare manually. Note that manual updates should only be done if a regular update is not possible! Please make sure you have a working ...

    • Cryptshare doesn't start after rollback to previous version

      Applies to: All versions of Cryptshare Server Symptom: After rolling back to a previous version the Cryptshare Server is not available. Cause: The Java installation folder has not been restored. Solution: There are three approaches to restore Java: ...

    • Checking process on operating system upgrade

      Applies to: All Cryptshare Appliances Purpose: As long the operating system is upgraded, all web based interfaces aren't reachable. Solution: For observing the upgrade procedure you can open an SSH connection and check one of the following logs: 1. ...

    • Running Cryptshare in headless mode

      Applies to: All versions of Cryptshare Server Symptom: Cryptshare fails to send/generate emails and reports an error related to the java.awt.Color class. cryptshare.log java.lang.NoClassDefFoundError: Could not initialize class java.awt.Color Cause: ...