We have a docker-compose setup including OntoWiki but our outdated tenforce/virtuoso:1.2.0-virtuoso7.2.4 was crashing all the time, so we updated it to the more up to date openlink/virtuoso-opensource-7:7 (right now pointing to version 7.2.6).
While the Virtuoso SPARQL endpoint now runs again, hopefully more stable than before, this seems to have killed our included OntoWiki docker container.
I'm a Docker beginner so I'm sorry if that is the wrong information, I'm happy to supply more.
The docker-compose.yml is given below.
Strangely, docker-compose logs ontowiki does not show any errors:
And docker-compose logs phpserver does not help much either (the problem occurred the last time after 14:00):
# docker-compose logs phpserver
Attaching to sniktoolset_phpserver_1
phpserver_1 | [22-Jun-2021 12:00:20] NOTICE: fpm is running, pid 1
phpserver_1 | [22-Jun-2021 12:00:20] NOTICE: ready to handle connections
phpserver_1 | [22-Jun-2021 12:00:20] NOTICE: systemd monitor interval set to 10000ms
phpserver_1 | [22-Jun-2021 12:47:00] NOTICE: Terminating ...
phpserver_1 | [22-Jun-2021 12:47:00] NOTICE: exiting, bye-bye!
phpserver_1 | [22-Jun-2021 12:47:02] NOTICE: fpm is running, pid 1
phpserver_1 | [22-Jun-2021 12:47:02] NOTICE: ready to handle connections
phpserver_1 | [22-Jun-2021 12:47:02] NOTICE: systemd monitor interval set to 10000ms
phpserver_1 | 172.23.11.5 - 22/Jun/2021:12:53:07 +0000 "GET /ontowiki/index.php" 500
So it seems like the log files are not linked to the docker logs.
Anyways, one of the problems was, that virtodbc.so seems to not be included in the new Virtuoso version, so I copied the one of the other version (hoping they are compatible) and the only way to see the logs of the resulting problems is to go into the PHP container via docker exec -it sniktoolset_phpserver_1 /bin/bash and then cat /var/www/html/logs/ontowiki.log shows:
2021-06-22T14:53:08+02:00 EMERG (0): Erfurt_Store_Adapter_Exception: Unable to connect to Virtuoso Universal Server via ODBC:
odbc_connect(): SQL error: [unixODBC][OpenLink][Virtuoso iODBC Driver]CL034: Bad login, SQL state 28000 in SQLConnect -> /var/www/html/vendor/aksw/erfurt/library/Erfurt/Store/Adapter/Virtuoso.php@290
However I didn't change any login data, only increased the virtuoso version and kept the virtuoso.db so all the login data should be the same, so I'm not sure how to fix this.
This is probably a too complicated situation to fix quickly but maybe I as a Docker newbie missed something obvious here that you can see at a glance.
Issue can be closed, it seems like it wasn't a Virtuoso problem after all. The docker pull seems to have overwritten the config.ini from the OntoWiki so that the password needed to be set again.
We have a docker-compose setup including OntoWiki but our outdated
tenforce/virtuoso:1.2.0-virtuoso7.2.4
was crashing all the time, so we updated it to the more up to dateopenlink/virtuoso-opensource-7:7
(right now pointing to version 7.2.6).While the Virtuoso SPARQL endpoint now runs again, hopefully more stable than before, this seems to have killed our included OntoWiki docker container. I'm a Docker beginner so I'm sorry if that is the wrong information, I'm happy to supply more. The docker-compose.yml is given below.
Strangely,
docker-compose logs ontowiki
does not show any errors:And
docker-compose logs phpserver
does not help much either (the problem occurred the last time after 14:00):So it seems like the log files are not linked to the docker logs.
Anyways, one of the problems was, that
virtodbc.so
seems to not be included in the new Virtuoso version, so I copied the one of the other version (hoping they are compatible) and the only way to see the logs of the resulting problems is to go into the PHP container viadocker exec -it sniktoolset_phpserver_1 /bin/bash
and thencat /var/www/html/logs/ontowiki.log
shows:However I didn't change any login data, only increased the virtuoso version and kept the virtuoso.db so all the login data should be the same, so I'm not sure how to fix this.
This is probably a too complicated situation to fix quickly but maybe I as a Docker newbie missed something obvious here that you can see at a glance.
docker-compose.yml