[arvados] keepproxy's own loop blocks data upload

[Nico Cesar]

Hi Jason,

please take a look into this:


http://doc.arvados.org/install/install-api-server.html

this is where you define the networks that will use keepproxy or keepstore

------------------------------------------------------------------

# When Keep clients request a list of Keep services from the API server, the
# server will automatically return the list of available proxies if
# the request headers include X-External-Client: 1.  Following the example
# here, at the end of this section, add a line for each netmask that has
# direct access to Keep storage daemons to set this header value to 0.
geo $external_client {
  default        1;
  10.20.30.0/24  0;
}

------------------------------------------------------------------

where you see 10.20.30.0/24 you should replace it with you internal network.

Thanks,

Nico



On Tue, Sep 5, 2017 at 9:09 PM, Yongjian Guo <guoyj2003 at gmail.com> wrote:

> Hi, Everyone,
>
> When I install the system on our machine, I noticed the following problem:
>
> My keep service has three items: one proxy and two disk. When I upload
> data using arv, I noticed in the proxy debug message:
>
> 2017/09/06 08:32:01 DEBUG: [365a8581] Begin upload
> 0f1d6bcf55c34bed7f92a805d2d89bbf to https://keepproxy-arvados.code.cn:443
> 2017/09/06 08:32:01 DEBUG: [365a8581] Replicas remaining to write: 2
> active uploads: 1
> 2017/09/06 08:32:01 proxy loop detected (request has Via: "HTTP/1.0
> keepproxy"): perhaps keepproxy is misidentified by gateway config as an
> external client, or its keep_services record does not have
> service_type=proxy?
> 2017/09/06 08:32:01 DEBUG: [365a8581] Upload https://keepproxy-arvados.
> code.cn:443/0f1d6bcf55c34bed7f92a805d2d89bbf error: 500 response: loop
> detected
> 2017/09/06 08:32:01 DEBUG: [365a8581] Replicas remaining to write: 2
> active uploads: 0
> 2017/09/06 08:32:01 DEBUG: [365a8581] Begin upload
> 0f1d6bcf55c34bed7f92a805d2d89bbf to https://keepproxy-arvados.code.cn:443
> 2017/09/06 08:32:01 DEBUG: [365a8581] Replicas remaining to write: 2
> active uploads: 1
> 2017/09/06 08:32:01 proxy loop detected (request has Via: "HTTP/1.0
> keepproxy"): perhaps keepproxy is misidentified by gateway config as an
> external client, or its keep_services record does not have
> service_type=proxy?
> 2017/09/06 08:32:01 DEBUG: [365a8581] Upload https://keepproxy-arvados.
> code.cn:443/0f1d6bcf55c34bed7f92a805d2d89bbf error: 500 response: loop
> detected
> 2017/09/06 08:32:01 DEBUG: [365a8581] Replicas remaining to write: 2
> active uploads: 0
> 2017/09/06 08:32:01 DEBUG: [365a8581] Begin upload
> 0f1d6bcf55c34bed7f92a805d2d89bbf to https://keepproxy-arvados.code.cn:443
> 2017/09/06 08:32:01 DEBUG: [365a8581] Replicas remaining to write: 2
> active uploads: 1
> 2017/09/06 08:32:01 proxy loop detected (request has Via: "HTTP/1.0
> keepproxy"): perhaps keepproxy is misidentified by gateway config as an
> external client, or its keep_services record does not have
> service_type=proxy?
> 2017/09/06 08:32:01 DEBUG: [365a8581] Upload https://keepproxy-arvados.
> code.cn:443/0f1d6bcf55c34bed7f92a805d2d89bbf error: 500 response: loop
> detected
> 2017/09/06 08:32:01 127.0.0.1:42488 PUT /0f1d6bcf55c34bed7f92a805d2d89bbf
> 413 12 2 0  Could not write sufficient replicas: [500] loop detected
>
>
> It looks that the keepproxy keeps writing to itself. I checked the source
> code and feel it is in the array  of WritableLocalRoots.
>
> Do you know if there is a way to go around this problem?
>
> Thanks,
>
> Jason
>
>
>
>
>
> _______________________________________________
> arvados mailing list
> arvados at arvados.org
> http://lists.arvados.org/mailman/listinfo/arvados
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.arvados.org/pipermail/arvados/attachments/20170906/b15b90b6/attachment.html>