-
Notifications
You must be signed in to change notification settings - Fork 803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nextCloudCmd throws error 'Sqlite exec statement error: 5 "database is locked"' #3840
Comments
Is your nextcloud client running? You probably need to stop it. The database gets locked exclusively by it. |
No, nextCloudClient is not running on this machine. |
This comment was marked as outdated.
This comment was marked as outdated.
I get the same problem, and with 10+ folders to sync, this means my sync takes approx 10min when I used selective sync. Also commenting so this issue won't be closed like the two others :( |
I also have this issue with:
|
Same problem with:
I observed that this only happens together with option --unsyncedfolders. Logging output shows:
After this, syncing resumes quite normally - but a change in my --unsyncedfolders -file is not obeyed. This is not surprising since the above "warning"-Message tells "SQL error when inserting into selective sync" (in that case i added the line "weitereDOTX" to my --unsyncedfolders -file, which before had only one line: "Archiv"). So fixing this bug is not only necessary to avoid the "database locked" -delay (which takes about five minutes), but also to bring any change in --unsyncedfolders -file to work. |
This comment was marked as outdated.
This comment was marked as outdated.
Problem still exists on 3.4.1 fa32c10
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
I get the error for
With
|
Also effecting me. ps. auto closing tickets is such a false economy. |
I have the same problem with:
Additional Info: I run nextcloudcmd twice in the last 24 hours, this is the output from the commands (I have deleted the sync file in between):
Interesting that in both invocations, the timelag between the last info message and the first warning about Sqlite prepare statement error is exactly the same, 2h 7m and 4s... And the second waring after 2h 7m almost the same... |
This comment was marked as outdated.
This comment was marked as outdated.
I noticed that the error happen, when the local dir is on a NFS4 mounted directory from another machine. On the local filesystem, all went well. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
I do not understand why this issue does get closed automatically all the time even if there clearly are people being affected. I also am afffected, running Nextcloud 23.0.4 running on Ubuntu 20.04.4 LTS, using mysql 8.0.28 as database and apache 2.4.53 as webserver. For sync i use nextcloudcmd version 3.4.4.
I also have several nextcloudcmd syncs running per hour so this takes up quite some time, so it would be good to see this fixed. |
This comment was marked as resolved.
This comment was marked as resolved.
I had the same issue on one of my linux clients after migration from owncloud (auto import parameters)... |
Were you running before the oc 4.2 desktop client? Or the previous version? |
Could you try the fix for this in: |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
Duplicate of #3422 |
How to use GitHub
Expected behaviour
nextCloudCmd shoud start and work.
Actual behaviour
I get the error 'Sqlite exec statement error: 5 "database is locked" (see screenshot) and somtimes after a long waitingtime the synchronisation starts.
Steps to reproduce
My call:
"C:\Program Files (x86)\appdir\nextcloudcmd.exe" --trust --path "sellify_documents_dev/sellifyontoursync" --non-interactive -u myuser -p mypassword --unsyncedfolders "C:\Program Files (x86)\IgnoreLists\default_ignore.txt" C:\sellify_documents https://myserver/nextcloud
Client configuration
Client version:
Nextcloud version 3.3.2stable-Win64 (build 20210826)
Git revision 50453d9
Using Qt 5.12.9, built against Qt 5.12.9
Using 'OpenSSL 1.1.1g 21 Apr 2020'
Running on Windows Server 2016 (10.0), x86_64
Operating system:
Windows Server 2019 Standard 64bit
OS language:
German
Installation path of client:
Storage backend (external storage):
Networkdrive
The text was updated successfully, but these errors were encountered: