ISWC-Reproducibility-Track / Paper_607

0 stars 0 forks source link

Server saying " ERROR - /usr/src/app/contexts/context_overwrite.json missing" #1

Open riccardoAlbertoni opened 4 years ago

riccardoAlbertoni commented 4 years ago

I have tried to reproduce the ISWC paper 607, I was able to generate the openAPI and the server for DBpedia Music, but I have some problems when executing the server.

Could the authors (@mosoriob or @dgarijo) take a look at the notebook ([1] or [2]) and doublecheck what has gone wrong? I have to admit I quite rusty on Docker.

Thanks, Riccardo

[1]https://colab.research.google.com/drive/1XKk_feh4Eb-fC3FGQ9kGwfiP7KieswT3?usp=sharing [2]https://github.com/riccardoAlbertoni/ISWC_reproducibility607/blob/master/Reproducing607.ipynb

dgarijo commented 4 years ago

Thanks @riccardoAlbertoni, it looks like one of the latest updates we have done to OBA messes the deployment up (we are adding more tests to detect these type of things) https://github.com/KnowledgeCaptureAndDiscovery/OBA/issues/132 We will fix it this week and let you know.

BTW, the report you are making is AMAZING. When everything is done I would like to link from it/copy it from our tutorials page.

dgarijo commented 4 years ago

@riccardoAlbertoni, we have fixed the issue, please have a look whenever you have the chance. Thanks!

riccardoAlbertoni commented 4 years ago

Thanks, @dgarijo. I am afraid I still not able to start successfully the server, please take a look at the last section "starting up a container" in the notebook. What I am doing wrong? Is it expected that I get the following error?

2020-10-13 18:11:54,033 - root - ERROR - /usr/src/app/contexts/context_overwrite.json missing

Am I accessing the correct URLs http://localhost:8080/3.5.1/ui and http://localhost:8080/3.5.1/openapi.json?

dgarijo commented 4 years ago

@riccardoAlbertoni This is exactly the issue we seemed to address yesterday: https://github.com/KnowledgeCaptureAndDiscovery/OBA/issues/134 We will look if you are missing something, but please keep in mind that you have to update the oba release and rerun the jar.

riccardoAlbertoni commented 4 years ago

Sure, thanks for reminding this, but I had rerun all the instructions listed in the notebook, so everything should have been updated during my last attempt.

dgarijo commented 4 years ago

ok, will try to reproduce and get back to you.

dgarijo commented 4 years ago

Hi @riccardoAlbertoni, I looked it up (sorry for the delay, it's been crazy lately). What is happening is that you didn't expose the ports in the docker container (we should have said so in the documentation, I will update it). I ran everything else as you did (I also got the error about the context, but it works just fine).

To expose the port, just do:

docker run -p 8080:8080 -v $PWD/openapi_server/openapi/:/usr/src/app/openapi_server/openapi/ openapi_server

And then access the localhost url you had in your configuration. If you used the one in examples, it isversion: v1.3.0, so you'll find it in: http://localhost:8080/v1.3.0/ui

you should see a swagger API with bands and genres (4 paths in total). When testing the API, if you select the default number of items per page (100), the query is going to be slow (10-11s). If you change it to 10, I usually get results within 5-6 secs (perfomance improves significantly building a cache but for the reproducibulity effort it may not be needed)

mosoriob commented 4 years ago

The context_overwrite file is a optional file to overwrite the context returned by the endpoint. The log level of the message is incorrect and produces misunderstood.

mosoriob commented 4 years ago

https://github.com/KnowledgeCaptureAndDiscovery/OBA/issues/137

riccardoAlbertoni commented 4 years ago

Ok, thanks @dgarijo and @mosoriob, I am now able to access http://localhost:8080/v1.3.0/ui and get the list of bands and details about bands. I appreciate that you have already updated the instructions adding the -p parameter.

dgarijo commented 4 years ago

Great, let us know if you have more questions. I am thinking on adding another example with a simpler ontology, which will resolve queries very quickly :)