|
Hi again,
I'm on linux with a calibre database in my home directory. I just booted the machine and tried to run "calibredb list" and got - after a very long pause -
Traceback (most recent call last):
File "runpy.py", line 194, in _run_module_as_main
File "runpy.py", line 87, in _run_code
File "site.py", line 45, in <module>
File "site.py", line 41, in main
File "calibre/db/cli/main.py", line 251, in main
File "calibre/db/cli/main.py", line 41, in run_cmd
File "calibre/db/cli/cmd_list.py", line 315, in main
File "calibre/db/cli/cmd_list.py", line 148, in do_list
File "calibre/db/cli/main.py", line 184, in run
File "calibre/db/cli/main.py", line 171, in db
File "calibre/db/legacy.py", line 188, in __init__
File "calibre/db/legacy.py", line 45, in create_backend
File "calibre/db/backend.py", line 470, in __init__
File "calibre/db/schema_upgrades.py", line 19, in __init__
File "calibre/db/backend.py", line 937, in execute
apsw.BusyError: BusyError: database is locked
AFIK there is NO networking involved in accessing my local db on my local machine. Nevertheless, this error message is almost identical to to one I got when my db was in dropbox (my initial question).
I'm sorry, but I'm now totally confused. I was prepared to accept your explanation that networking was the culprit but since the problem also occurs with no networking, it makes me wonder if there isn't something else going on.
|