Payment System locked

Explanation

The Payment System service starts but it does not communicate with the rest of system (e.g. users are unable to deposit money, users are unable to make copy operation that requires credit/quota).

payment-system.log may contain e.g. this:
Caused by: liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by PS-Server (10.10.3.121) since 2022/02/15 4:30 AM

Such an issue could occur for example after an unexpected shutdown of the server. The Payment System creates a lock in the database for some operations and if the DB connectivity gets lost or there is unexpected server shutdown before the operation completes, the lock is not removed. This may prevent further operations.

Resolution

To release the lock, please take the following steps:

  1. Stop all the YSoft SafeQ services.

  2. Run the SQL query on the Payment System database:
    UPDATE databasechangeloglock SET locked = 'false' WHERE id=1

  3. Start all YSoft SafeQ services.

  4. Verify that Web Interface of Payment System is working and that the situation is resolved.