iODBC Driver issue on RDF import

[aottr]

I've tested the RDF-file upload and RDF-source import, both options reported the same error message given below, canceling the data import.

Could not import given model: Error importing statements: SQL Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]FA112: Can't stat file '/tmp/owcID79A', error (2) : No such file or directory () in query: CALL DB.DBA.RDF_LOAD_RDFXML(FILE_TO_STRING_OUTPUT('/tmp/owcID79A'), 'http://localhost:8080/XXXX/', 'http://localhost:8080/XXXX/')

The terminal running docker-compose only displayed nginx/phpserver routing information.

[white-gecko]

I can't reproduce this issue. Is the database below 2 MB as configured per default at the moment? Could you please provide more details on your setup? Did you make any changes to the compose setup? Did you try removing the relevant images and let docker pull them again?

[aottr]

I've removed all containers and recreated them via docker-compose up, the error still shows up if I try to import any data.
The original database has a size of around 45MB so I created a test-database with some of the entries (~123.4kB, 886 N-Triples)

I didn't make any changes to the compose setup.
The test-setup:
i7-4600U@ 4x 3.3Ghz, 8GB RAM, 8GB Swap, Linux Arch Kernel 4.9.33-1-lts
docker-compose version 1.15.0
docker version 17.06.1-ce

[aottr]

I successfully imported some ttl dumps from dbpedia on a second test environment so the import extension may be incompatible with the sparqlify N-Triples output.
Is there a common method to convert N-Triples to N3/Turtle/(RDF/XML)?

[white-gecko]

Ah ok, cool so we are getting closer. I think I will try it with RDF/XML as well. Maybe this is the reason.

[lonniev]

I solved this issue by:

• docker-compose config | pbcopy
• pbpaste # show me how docker-compose treats the yml file
• pbpaste > docker-compose.yml # overwrite the legacy version
• vi docker-compose.yml # change the version to 2.4
• add under virtuoso volumes: # map a relative ./tmp directory to /tmp
  - ./tmp:/tmp
• mkdir ./tmp
• stopping all containers, purging everything, and rerunning docker-compose up

Apparently the virtuoso image needs a /tmp filesystem.