LInker Error : Remote Info: Upstream Address: Not Available

application: brief :
we have linkerd setup with forwarding all request to local haproxy listening on port 4040,

problem summary :
we are getting below error though i can see service[haproxy] is running fine on “localhost:4040” and accepting requests , when i restart the linkerd service error is gone but comes again after some time .

Error:
May 30 07:05:36 PD_VM_DAGW_DownloadAPIGW_1522244462080 linkerd-1.3.0-exec[877]: E 0530 07:05:36.472 UTC THREAD31 TraceId:51461fe27d99633a: service failure: com.twitter.finagle.CancelledRequestException: request cancelled. Remote Info: Upstream Address: Not Available, Upstream id: Not Available, Downstream Address: /127.0.0.1:4040, Downstream label: #/io.l5d.fs/jclocal, Trace Id: 51461fe27d99633a.8bee666b62774ba7<:51461fe27d99633a

Additional details :
There are also 502 errors due to this , kindly help to fix this issue :
*linkerd version : linkerd-1.3.5
*cat /opt/linkerd/disco/jclocal
127.0.0.1 4040

*haproxy is able to listen on 4040
telnet 127.0.0.1 4040
Trying 127.0.0.1…
Connected to 127.0.0.1.
Escape character is ‘^]’.

*Linkerd config :/opt/linkerd/config/linkerd.yaml

admin:
  port: 9991
  ip: 0.0.0.0

namers:
- kind: io.l5d.fs
  rootDir: /opt/linkerd/disco/

routers:
- protocol: http
  label: linkerd-in
  maxChunkKB: 112640
  maxRequestKB: 112640
  dstPrefix: /http

  identifier:
    - kind: io.l5d.path
      segments: 2
    - kind: io.l5d.path
      segments: 1

  dtab: |
    /http/* => /#/io.l5d.fs/jclocal;
  httpAccessLog: /opt/linkerd/logs/access.log
  servers:
  - port: 5051
    ip: 0.0.0.0
    maxConcurrentRequests: 2000


  client:
    loadBalancer:
      kind: ewma
    failureAccrual:
      kind: io.l5d.successRate
      successRate: 0.9
      requests: 1000
      backoff:
        kind: jittered
        minMs: 5000
        maxMs: 300000

- protocol: http
  label: linkerd-out
  maxChunkKB: 112640
  maxRequestKB: 112640

  interpreter:
    kind: io.l5d.namerd
    dst: /$/inet/pd-namerd.service.jiocloud.prod.internal/5100
    namespace: pd

  identifier:
    - kind: io.l5d.path
      segments: 2
    - kind: io.l5d.path
      segments: 1


  dstPrefix: /http

  servers:
  - port: 5052
    ip: 0.0.0.0
    maxConcurrentRequests: 2000

  bindingCache:
    paths: 100
    trees: 100
    bounds: 1000
    clients: 1000
    idleTtlSecs: 3600


  client:
    hostConnectionPool:
      minSize: 20
      maxSize: 1000
      idleTimeMs: 10000
      maxWaiters: 5000

    loadBalancer:
      kind: ewma
    failureAccrual:
      kind: io.l5d.successRate
      successRate: 0.9
      requests: 1000
      backoff:
        kind: jittered
        minMs: 5000
        maxMs: 300000

telemetry:
- kind: io.l5d.prometheus

Hi @rathoreshakti7, thanks for submitting this ticket. Do you mind formatting your logs and yaml so that it is easier to read? You can use Github’s markdown style in discourse as well.

Thanks!

com.twitter.finagle.CancelledRequestException: request cancelled means that the request was cancelled by the caller. it doesn’t indicate any problem with Linkerd. So I think it’s unrelated to any 502 errors you are seeing.

Can you provide more information about the 502 (is there a response body? how was the 502 triggered? etc)

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.