Troubleshooting

The following information may be helpful in the unlikely case that an issue occurs.

The System Is Temporarily Locked For Changes

This system allows simultaneous changes. However, there are certain actions - for example, synchronisation - that require exclusive access to ensure data integrity is maintained. This consideration is particularly relevant when the system is configured to store audio files on disk.

When an action that requires exclusive access is in progress, other actions may be denied or delayed until the action completes. For example:

• Attempting to initiate a synchronisation while another synchronisation is already in progress will be denied.
• When audio files are stored on disk, audio file upload, audio file deletion, snapshot creation, and synchronisation may be delayed if any of those actions are already in progress.

Exclusive access is guaranteed using a locking mechanism. Normally the locking mechanism should function transparently and delays should be minimal. In exceptional circumstances actions may consistently fail with the message “The system is temporarily locked for changes”.

In that scenario:

1. Navigate to the “administration” section “database locking” tab.
2. Confirm that the “file_system_sync” lock is locked.
3. Note the lock holder and timestamp.
   • The associated action is likely to have acquired the lock, failed, and also neglected to release the lock, leaving the system locked.
   • Report these details to the system administrator.
4. Unlock the lock.
5. If appropriate, reattempt any failed actions.