[2.34.0 -> 2.36.2] request to graphql-engine failed, reason: socket hang up

[arcenik]

Version Information

• hasura / graphql-engine: 2.36.2
• input-output-hk / cardano-graphql: 8.0.0
• cardano-node: 8.7.3

Environment

On premise K8S cluster, using custom docker image based on ubuntu:22.04

What is the current behaviour?

The graphql-server makes request to graphql-engine and get a lot of ECONRESET

2024-01-23T08:27:37.767785380Z {
  "name":"cardano-graphql",
  "hostname":"cardano-ogmios-preview-test-873-graphql-server-df88db448-cws9l",
  "pid":1,
  "level":50,
  "err":{
    "message":"request to http://cardano-ogmios-preview-test-873-graphql-engine-headless:8888/v1/graphql failed, reason: socket hang up",
    "type":"system",
    "errno":"ECONNRESET",
    "code":"ECONNRESET"
  },
  "msg":"request to http://cardano-ogmios-preview-test-873-graphql-engine-headless:8888/v1/graphql failed, reason: socket hang up",
  "time":"2024-01-23T08:27:37.767Z",
  "v":0
}

The graphql-engine is started with basic parameters

graphql-engine serve \
   --server-port 8888 \
   --database-url "${HASURA_GRAPHQL_DATABASE_URL}"

Any possible solutions/workarounds you're aware of?

Rolling back to version 2.34.0 fixed the issue.

Keywords

• ECONNRESET

[codingkarthik]

@arcenik Can you tell me when do you get this error? Does this happen on running any GraphQL query?

[arcenik]

The backend makes request to graphql-server that makes request to graphql-engine. The log extract is from graphql-server, no error where found on the graphql-engine logs.

[codingkarthik]

The log extract is from graphql-server, no error where found on the graphql-engine logs.

So, maybe the request didn't reach the graphql-engine? But, as you mentioned, if you downgrade, the problem is resolved?

[laibe]

this issue is still present in v2.39.1

[SamirTalwar]

Hey folks, if you can put together a simple reproduction (e.g. a Docker Compose file and Dockerfiles for associated images), then we would be happy to investigate. Right now we cannot reproduce anything.

[laibe]

similar to https://github.com/hasura/graphql-engine/issues/9393 we had to downgrade nodejs on our cardano-graphql server to major version 18 to fix the issue (before we were running 20 and 22).