Server 'completed' while running query (aka crashed) #2249
Replies: 2 comments 1 reply
-
|
Sorry I don't understand what you wrote here, can you try to rephrase? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Closing. This works on the docker container tagged: adfreiburg/qlever:pr-2271 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We run a qlever (or three) in docker using portainer to manage the container stacks.ar
When server is started (and restarted), the server rebuilds itself (aka get-data, index, start)
Occasionally when running a query in the UI, it will say after a period, the UI says cannot connect to the server.
When we look into the portainer, the log says that the server 'completed' and a new instance is starting up.
The logs in the completed are terse. No idea why the server stopped.
Is there are way to up the logging so we can figure out how?
Same dataset as: #2243
tail of log from 'completed' container
sparql query that crashed it, this time.
Beta Was this translation helpful? Give feedback.
All reactions