Menu
▾
▴
Re: [Bigdata-developers] Blazegraph Docker problem: "ERROR: Could not contact server"
|
From: Mikel E. A. <mik...@gm...> - 2015-10-29 10:21:59
|
Find attached a screenshot of the log
Let me know if this suffices,
Thanks
2015-10-29 2:04 GMT+01:00 Brad Bebee <be...@sy...>:
> Mikel,
>
> Do you get any javascript output when accessing the workbench when it
> works initially?
>
> Thanks, --Brad
>
> On Wed, Oct 28, 2015 at 11:39 AM, Mikel Egaña Aranguren <
> mik...@gm...> wrote:
>
>> Hi;
>>
>> I'm still getting the same error. I can access
>> http://127.0.0.1:9999/bigdata/#splash but then if I access the
>> container's IP (obtained with inspect, 172.17.0.4) the connection is
>> refused:
>>
>> mikel@durruti:~$wget
>> http://172.17.0.4:9999/bigdata/sparql?query=select%20*%20where%20{%20?s%20?p%20?o%20}%20limit%201
>> <http://172.17.0.4:9999/bigdata/sparql?query=select%20*%20where%20%7B%20?s%20?p%20?o%20%7D%20limit%201>
>> Konektatzen 172.17.0.4:9999... huts egin da: Connection refused
>>
>> Thanks
>>
>> 2015-10-28 16:25 GMT+01:00 Brad Bebee <be...@sy...>:
>>
>>> Mikel,
>>>
>>> You'll need to make sure to use the IP of the docker container to access
>>> the Blazegraph instance. Outside of the container, it will not be running
>>> on 127.0.0.1, but rather the IP assigned to the docker container.
>>>
>>> You'll need to run something like *docker inspect --format '{{
>>> .NetworkSettings.IPAddress }}' "CONTAINER ID".*
>>>
>>> Let us know if that works.
>>>
>>> Thanks, --Brad
>>>
>>>
>>>
>>>
>>> On Wed, Oct 28, 2015 at 11:11 AM, Mikel Egaña Aranguren <
>>> mik...@gm...> wrote:
>>>
>>>> Hi;
>>>>
>>>> I'm preparing a Docker image that includes Blazegraph, but Blazegraph
>>>> is not working. It must be a problem with the Docker setting but perhaps
>>>> someone can give a pointer. (I have also submitted the question to stack
>>>> overflow [1])
>>>>
>>>> The Dockerfile [2] isimply copies a working installation of blazegraph
>>>> and executes the nano sparql server:
>>>>
>>>> COPY blazegraph /LinkedDataServer/blazegraph
>>>> CMD java -server -jar blazegraph/bigdata-bundled.jar
>>>>
>>>> When I run the container (also including pubby and refine):
>>>>
>>>> docker run -d -p 9999:9999 -p 3333:3333 -p 8080:8080
>>>> mikeleganaaranguren/linked-data-server:0.0.1
>>>>
>>>> It runs fine, i.e. I can access Blazegraph at http://127.0.0.1:9999.
>>>> However, when I try to do a query or update data I get "ERROR: Could not
>>>> contact server". Also, I can't access the server programmatically
>>>> (Connection reset by peer):
>>>>
>>>> wget
>>>> http://127.0.0.1:9999/bigdata/sparql?query=select%20*%20where%20{%20?s%20?p%20?o%20}%20limit%201
>>>> <http://127.0.0.1:9999/bigdata/sparql?query=select%20*%20where%20%7B%20?s%20?p%20?o%20%7D%20limit%201>
>>>>
>>>> However when I enter the image and run blazegraph manually I can do the
>>>> wget above, both to localhost and the "internal" IP of the image. Obviously
>>>> there is something wrong with the Docker setting, but any clues will be
>>>> wellcome. Also, is there any blazegraph log I can access when runing
>>>> blazegraph like this?
>>>>
>>>> Thanks
>>>>
>>>>
>>>> [1]
>>>> http://stackoverflow.com/questions/33368741/docker-container-with-blazegraph-triple-store-not-working-possibly-due-to-networ
>>>> [2]
>>>>
>>>> FROM ubuntu:14.04
>>>> MAINTAINER Mikel Egaña Aranguren <my.email@x.com>
>>>>
>>>> RUN apt-get update && apt-get install -y openjdk-7-jre wget curl
>>>>
>>>> RUN mkdir /LinkedDataServer
>>>>
>>>> COPY google-refine-2.5 /LinkedDataServer/google-refine-2.5
>>>> COPY blazegraph /LinkedDataServer/blazegraph
>>>> COPY jetty /LinkedDataServer/jetty
>>>>
>>>> EXPOSE 9999
>>>> EXPOSE 3333
>>>> EXPOSE 8080
>>>>
>>>> WORKDIR /LinkedDataServer
>>>> CMD java -server -jar blazegraph/bigdata-bundled.jar
>>>> CMD google-refine-2.5/refine -i 0.0.0.0
>>>>
>>>> WORKDIR /LinkedDataServer/jetty
>>>> CMD java -jar start.jar jetty.port=8080
>>>>
>>>>
>>>> --
>>>> Mikel Egaña Aranguren, Ph.D.
>>>>
>>>> http://mikeleganaaranguren.com
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Bigdata-developers mailing list
>>>> Big...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>>>
>>>>
>>>
>>>
>>> --
>>> _______________
>>> Brad Bebee
>>> CEO, Managing Partner
>>> SYSTAP, LLC
>>> e: be...@sy...
>>> m: 202.642.7961
>>> f: 571.367.5000
>>> w: www.blazegraph.com
>>>
>>> Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance
>>> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
>>> APIs. Mapgraph™ <http://www.systap.com/mapgraph> is our disruptive new
>>> technology to use GPUs to accelerate data-parallel graph analytics.
>>>
>>> CONFIDENTIALITY NOTICE: This email and its contents and attachments
>>> are for the sole use of the intended recipient(s) and are confidential or
>>> proprietary to SYSTAP, LLC. Any unauthorized review, use, disclosure,
>>> dissemination or copying of this email or its contents or attachments is
>>> prohibited. If you have received this communication in error, please notify
>>> the sender by reply email and permanently delete all copies of the email
>>> and its contents and attachments.
>>>
>>
>>
>>
>> --
>> Mikel Egaña Aranguren, Ph.D.
>>
>> http://mikeleganaaranguren.com
>>
>>
>>
>
>
> --
> _______________
> Brad Bebee
> CEO, Managing Partner
> SYSTAP, LLC
> e: be...@sy...
> m: 202.642.7961
> f: 571.367.5000
> w: www.blazegraph.com
>
> Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance
> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
> APIs. Mapgraph™ <http://www.systap.com/mapgraph> is our disruptive new
> technology to use GPUs to accelerate data-parallel graph analytics.
>
> CONFIDENTIALITY NOTICE: This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP, LLC. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
>
--
Mikel Egaña Aranguren, Ph.D.
http://mikeleganaaranguren.com
|
