You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am led to believe that sqlite doesn't support multiple concurrent access with it being file based and so presumably that's what the issue is (and, specifically, that Roundcube happens to have the database locked at the time)?
I could pipe all errors to /dev/null but I'd like to know about others ('genuine' ones, if you see what I mean) that might occur. Is there any way the sync-cli.sh script could detect a locked database and handle the situation differently - perhaps retrying or backing off momentarily, if that's what required?
The text was updated successfully, but these errors were encountered:
mjnewton
changed the title
Problems accessing locking database
Handling of locked databases
Apr 24, 2021
Since moving from mysql to sqlite3 I have been occasionally getting the following errors when running sync-cli.sh via cron:
I am led to believe that sqlite doesn't support multiple concurrent access with it being file based and so presumably that's what the issue is (and, specifically, that Roundcube happens to have the database locked at the time)?
I could pipe all errors to /dev/null but I'd like to know about others ('genuine' ones, if you see what I mean) that might occur. Is there any way the sync-cli.sh script could detect a locked database and handle the situation differently - perhaps retrying or backing off momentarily, if that's what required?
The text was updated successfully, but these errors were encountered: