wk-mls commented on issue #2756:
URL:
https://github.com/apache/apisix-ingress-controller/issues/2756#issuecomment-4607369233
I was previously experiencing the `socket hang up` error as well and saved
debug logs:
```
2026-05-27T03:05:14.598Z DEBUG provider.executor
client/executor.go:303 received HTTP response from ADC Server {"server":
"http://10.10.10.10:9180,http://10.10.10.20:9180";, "status": 202, "response":
"{\"status\":\"partial_failure\",\"total_resources\":2,\"success_count\":1,\"failed_count\":1,\"success\":[{\"server\":\"http://10.10.10.20:9180\",\"event\":{},\"synced_at\":\"2026-05-27T03:05:14.000Z\"}],\"failed\":[{\"server\":\"http://10.10.10.10:9180\",\"event\":{},\"failed_at\":\"2026-05-27T03:05:14.598Z\",\"reason\":\"socket
hang up\"}]}"}
2026-05-27T03:05:14.598Z ERROR provider.executor
client/executor.go:328 ADC Server sync failed {"result":
{"status":"partial_failure","total_resources":2,"success_count":1,"failed_count":1,"success":[{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"0001-01-01T00:00:00Z","synced_at":"2026-05-27T03:05:14Z","response":{"status":0,"headers":null}}],"failed":[{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-05-27T03:05:14.598Z","synced_at":"0001-01-01T00:00:00Z","reason":"socket
hang up","response":{"status":0,"headers":null}}]}, "error": "ADC Server sync
failed: socket hang up"}
2026-05-27T03:05:14.598Z ERROR provider.executor
client/executor.go:142 failed to run http sync for server {"server":
"http://10.10.10.10:9180,http://10.10.10.20:9180";, "error": "ServerAddr:
http://10.10.10.10:9180,http://10.10.10.20:9180, Err: socket hang up"}
2026-05-27T03:05:14.598Z ERROR provider.client client/client.go:269
failed to execute adc command {"config":
{"name":"GatewayProxy/apisix/apisix-config","serverAddrs":["http://10.10.10.10:9180","http://10.10.10.20:9180"],"tlsVerify":false},
"error": "ADC execution error for GatewayProxy/apisix/apisix-config:
[ServerAddr: http://10.10.10.10:9180,http://10.10.10.20:9180, Err: socket hang
up]"}
2026-05-27T03:05:14.598Z ERROR provider.client client/client.go:210
failed to sync resources {"name": "GatewayProxy/apisix/apisix-config",
"error": "ADC execution errors: [ADC execution error for
GatewayProxy/apisix/apisix-config: [ServerAddr:
http://10.10.10.10:9180,http://10.10.10.20:9180, Err: socket hang up]]"}
2026-05-27T03:05:14.598Z DEBUG provider apisix/provider.go:306
handled ADC execution errors {"status_record":
{"GatewayProxy/apisix/apisix-config":{"Errors":[{"Name":"GatewayProxy/apisix/apisix-config","FailedErrors":[{"Err":"socket
hang
up","ServerAddr":"http://10.10.10.10:9180,http://10.10.10.20:9180","FailedStatuses":[{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-05-27T03:05:14.598Z","synced_at":"0001-01-01T00:00:00Z","reason":"socket
hang up","response":{"status":0,"headers":null}}]}]}]}}, "status_update":
{"ApisixGlobalRule/apisix/prometheus":["ServerAddr:
http://10.10.10.10:9180,http://10.10.10.20:9180, Err: socket hang
up"],"ApisixTls/apisix/tls":["ServerAddr:
http://10.10.10.10:9180,http://10.10.10.20:9180, Err: socket hang
up"],"Ingress/namespace1/deployment1":["ServerAddr:
http://10.10.10.10:9180,http://10.10.10.20:9180, Err: socket hang
up","ServerAddr: http://10.10.10.10:9180,http://10.10.10.20:9180, Err: socket
hang up"]}}
```
I saw the suggested fix of increasing `apisix.nginx.keepaliveTimeout` here
and in a separate issue
(https://github.com/apache/apisix-ingress-controller/issues/2704#issuecomment-3770819717)
so I tried increasing the `keepaliveTimeout` to the nginx default of `75s`,
which resolved the issue entirely. A partial fix was put into ADC with the idea
of proposing a default `keepaliveTimeout` of `75s`
(https://github.com/api7/adc/pull/407) but may not have been completed yet.
nginx documentation:
https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_timeout
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
