OperationalError at / unable to open database file

[WolfgangFahl]

https://qlever.wikidata.dbis.rwth-aachen.de/ currently shows this error message.

       at /</h1>
  <pre class="exception_value">unable to open database file</pre>
  
Request Method: | GET
-- | --
http://qlever.wikidata.dbis.rwth-aachen.de/
5.0.3
OperationalError
unable to open database file
/env/lib/python3.12/site-packages/django/db/backends/sqlite3/base.py, line 181, in get_new_connection
backend.views.index
/env/bin/python
3.12.4
['/app',  '/env/bin',  '/usr/local/lib/python312.zip',  '/usr/local/lib/python3.12',  '/usr/local/lib/python3.12/lib-dynload',  '/env/lib/python3.12/site-packages',  '/env/lib/python3.12/site-packages/odf',  '/env/lib/python3.12/site-packages/odf',  '/env/lib/python3.12/site-packages/odf',  '/env/lib/python3.12/site-packages/odf',  '/env/lib/python3.12/site-packages/odf',  '/env/lib/python3.12/site-packages/odf',  '/env/lib/python3.12/site-packages/odf']
Fri, 18 Jul 2025 06:06:42 +0000

with an elaborate debug output. I am surprised about the message and confused about the main information missing: What file can not be opened and why?

How can this problem be mitigated?

[WolfgangFahl]

The context of the problem is https://wiki.bitplan.com/index.php/Wikidata_Import_2025-07-13

For months i have been trying to automated the process of rotating WikiData copy updates on 4 SSD disks that we have for that purpose. Unforunately the devil is in the details and while the process parts seem to get ever more stable, quicke and better the whole is getting less reliable recently. E.g. i get

Building the index failed: docker: Error response from daemon: Conflict. The container name "/qlever.index.wikidata" is already in use by container "443e563e69bd2fe2fbc5e1b953a4836cb1e76e6a66225d2ce9dfe36da2c4100e". You have to remove (or rename) that container to be able to reuse that name.  Run 'docker run --help' for more information

althought i explicitly stopped and remove the culprit container and restarted the whole process including the download.

I had to remove the "old" directory which explains why currently there is no service available. But the hope was that a few hours later thing would automatically work again. Unfortunately that is not the case.

pip install -U qlever
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: qlever in /home/wf/.local/lib/python3.10/site-packages (0.5.23)
Requirement already satisfied: psutil in /home/wf/.local/lib/python3.10/site-packages (from qlever) (5.9.4)
Requirement already satisfied: termcolor in /home/wf/.local/lib/python3.10/site-packages (from qlever) (2.4.0)
Requirement already satisfied: argcomplete in /home/wf/.local/lib/python3.10/site-packages (from qlever) (3.4.0)
Requirement already satisfied: pyyaml in /home/wf/.local/lib/python3.10/site-packages (from qlever) (6.0.1)
wf@wikidata:/hd/beta/qlever/wikidata_20250714$ qlever stop --kill-existing-with-same-port

To enable autocompletion, run the following command, and consider adding it to your `.bashrc` or `.zshrc`:

eval "$(register-python-argcomplete qlever)" && export QLEVER_ARGCOMPLETE_ENABLED=1

usage: qlever [-h] [--version] [--qleverfile QLEVERFILE]
              {warmup,clear-cache,ui,settings,system-info,stop,extract-queries,cache-stats,start,add-text-index,status,index-stats,get-data,index,query,setup-config,example-queries,log}
              ...
qlever: error: unrecognized arguments: --kill-existing-with-same-port

[WolfgangFahl]

Just stopped the docker containers manually and restarted the indexing without another download. The automation seems currently broken - i assume a version incompatibility problem between the qlever script and qlever ui and qlever.