Open tianguohui opened 4 years ago
@tianguohui Does this happen for other versions of Hasura like v1.1.1
?
@tianguohui对于其他版本的Hasura会发生这种情况
v1.1.1
吗?
yes,V1.0.0, V1.2.1, v1.1.1 all have this situation. Is it the problem of CentOS server? I use CentOS 7.6, a new server
It seems like the client is closing the connections: https://stackoverflow.com/questions/1434451/what-does-connection-reset-by-peer-mean
Can you try to share a repro with a minimal client?
I use docker compose to start hasura connection with postgresql11.6, and the page reports an error: DB schema loading failed
I checked the logs and found: Spock Error while handling ["v1","query"]: receiveloop: resource vanished (Connection reset by peer) Spock Error while handling ["v1","query"]: receiveloop: resource vanished (Connection reset by peer) Spock Error while handling ["v1","query"]: receiveloop: resource vanished (Connection reset by peer) {"type":"http-log","timestamp":"2020-05-21T05:07:50.233+0000","level":"info","detail":{"operation":{"query_execution_time":1.1540291e-2,"user_vars":{"x-hasura-role":"admin"},"request_id":"d5c6fcde-a5a2-4689-9ed4-40c68f42da23","response_size":1135,"request_read_time":2.935287e-3},"http_info":{"status":200,"http_version":"HTTP/1.1","url":"/v1/query","ip":"xx.xx.xx.xx","method":"POST","content_encoding":"gzip"}}}
My docker- compose.yml The contents of the document are:
version: '3' services: graphql: image: docker.io/hasura/graphql-engine:v1.2.1 restart: always container_name: xxxx ports: