Installation problem: container skosmos-fuseki not responding

Christian C. Schouten

unread,

Nov 3, 2021, 8:04:38 AM11/3/21

to Skosmos Users

Hi all,

I'm trying to install skosmos using the docker containers but am running into difficulties. Hope you can help.

Server is a ubuntu 20.04 machine with 16G ram.

My steps:

$ cd /var/www

$ sudo git clone https://github.com/NatLibFi/Skosmos.git

Cloning into 'Skosmos'...

remote: Enumerating objects: 21371, done.

remote: Counting objects: 100% (1569/1569), done.

remote: Compressing objects: 100% (650/650), done.

remote: Total 21371 (delta 915), reused 1288 (delta 717), pack-reused 19802

Receiving objects: 100% (21371/21371), 61.63 MiB | 8.14 MiB/s, done.

Resolving deltas: 100% (14844/14844), done.

$ cd Skosmos/dockerfiles

$ sudo docker-compose up -d

Creating skosmos-fuseki ... done

Creating skosmos-fuseki-cache ... done

Creating skosmos-web ... done

Containers seem healthy:

$ sudo docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

65f3de452796 dockerfiles_skosmos "/usr/sbin/apache2ct…" About an hour ago Up 51 minutes (healthy) 0.0.0.0:9090->80/tcp, :::9090->80/tcp skosmos-web

6aa6bb90c967 varnish "/usr/local/bin/dock…" About an hour ago Up About an hour 8443/tcp, 0.0.0.0:9031->80/tcp, :::9031->80/tcp skosmos-fuseki-cache

cace370cb623 stain/jena-fuseki "/docker-entrypoint.…" About an hour ago Up About an hour 0.0.0.0:9030->3030/tcp, :::9030->3030/tcp skosmos-fuseki

No error messages are logged during startup of the containers:

$ sudo docker logs skosmos-fuseki

###################################

Initializing Apache Jena Fuseki

###################################

[2021-11-03 10:42:11] Server INFO Apache Jena Fuseki 3.14.0

[2021-11-03 10:42:11] Config INFO FUSEKI_HOME=/jena-fuseki

[2021-11-03 10:42:11] Config INFO FUSEKI_BASE=/fuseki

[2021-11-03 10:42:11] Config INFO Shiro file: file:///fuseki/shiro.ini

[2021-11-03 10:42:11] Config INFO Load configuration: file:///fuseki/configuration/skosmos.ttl

[2021-11-03 10:42:12] Config INFO Register: /skosmos

[2021-11-03 10:42:13] Server INFO Started 2021/11/03 10:42:13 UTC on port 3030

curl http://localhost:9090 and curl http://localhost:9031 finish without error so containers skosmos-web and skosmos-fuseki-cache seem to be perfectly fine

But unfortunately the container skosmos-fuseki (port 9030->3030) times out. It generates no response until a timeout and then errors out:

$ curl -I -X POST -H Content-Type:text/turtle -T ../../BudgetInfrastructure.ttl -G http://localhost:9030/skosmos/data --data-urlencode graph=https://data.rijksfinancien.nl/begrotingsinfrastructuur/

curl: (56) Recv failure: Connection reset by peer

Strange thing: the POST command above is not registered in the logs for the skosmos-fuseki container. It just doesn't even get to the container.

Ports are active:

$ sudo netstat -plnt | grep docker

tcp 0 0 0.0.0.0:9090 0.0.0.0:* LISTEN 3140264/docker-prox

tcp 0 0 0.0.0.0:9030 0.0.0.0:* LISTEN 3135913/docker-prox

tcp 0 0 0.0.0.0:9031 0.0.0.0:* LISTEN 3135890/docker-prox

tcp6 0 0 :::9090 :::* LISTEN 3140270/docker-prox

tcp6 0 0 :::9030 :::* LISTEN 3135921/docker-prox

tcp6 0 0 :::9031 :::* LISTEN 3135896/docker-prox

Processes are active:

$ ps aex | grep docker

2620704 ? Ssl 10:58 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

3135890 ? Sl 0:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9031 -container-ip 172.19.0.2 -container-port 80

3135896 ? Sl 0:00 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9031 -container-ip 172.19.0.2 -container-port 80

3135913 ? Sl 0:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9030 -container-ip 172.19.0.3 -container-port 3030

3135921 ? Sl 0:00 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9030 -container-ip 172.19.0.3 -container-port 3030

3135988 ? Ss 0:00 /bin/bash /docker-entrypoint.sh /jena-fuseki/fuseki-server

3140264 ? Sl 0:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9090 -container-ip 172.19.0.4 -container-port 80

3140270 ? Sl 0:00 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9090 -container-ip 172.19.0.4 -container-port 80

What could I be missing? How best should i go about troubleshooting this?

Thanks in advance for any help,

Chris

Bruno P. Kinoshita

unread,

Nov 3, 2021, 5:34:34 PM11/3/21

to Skosmos Users, Christian C. Schouten

Hi Chris,

There was an old issue with the Jena container where restarting it would leave the Jena/Fuseki container in an unresponsive state [1]. But I think that issue has been fixed.

When you start everything, are you able to open Fuseki in your browser? It should be available in http://localhost:9030, use admin, pass the same.

You can also start a bash in that container and take a look if some of the local log files contain anything useful (if so, we could try to include the output in the container stdout, in stain/jena-docker).

Bruno

[1] https://github.com/stain/jena-docker/issues/34

--
You received this message because you are subscribed to the Google Groups "Skosmos Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skosmos-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/skosmos-users/96946340-15f4-4bb0-8063-cb0dbb0e8e94n%40googlegroups.com.

Christian C. Schouten

unread,

Nov 4, 2021, 3:06:03 PM11/4/21

to Skosmos Users

Thanks for your answer Bruno. I've tried adding ps to the docker container because I've received that error as well in a previous attempt. Still no luck.

I have instead opted for a solution easier than digging deeper and deeper: I've managed to install fuseki and Skosmos without a docker container :)

Thanks again,

Chris

Op woensdag 3 november 2021 om 22:34:34 UTC+1 schreef brunod...@yahoo.com.br:

Reply all

Reply to author

Forward