vortegatorres commented on issue #2708:
URL:
https://github.com/apache/apisix-ingress-controller/issues/2708#issuecomment-3844077083
> When the issue occurs, are there any error logs in the Ingress Controller?
Sorry, I missed this earlier. This isn't happening just during the incident,
`ingress-controller` is consistently logging this error:
```
2026-02-03 23:26:15.434 error 2026-02-03T22:26:15.434Z ERROR
provider apisix/provider.go:282 failed to sync {"error": "failed to
sync 1 configs: GatewayProxy/k6-api-prod/apisix-config"}
2026-02-03 23:26:15.432 error 2026-02-03T22:26:15.431Z ERROR
provider.client client/client.go:210 failed to sync resources
{"name": "GatewayProxy/k6-api-prod/apisix-config", "error": "ADC execution
errors: [ADC execution error for GatewayProxy/k6-api-prod/apisix-config:
[ServerAddr:
http://<REDACTED_IP_1>:9180,http://<REDACTED_IP_2>:9180,http://<REDACTED_IP_3>:9180,http://<REDACTED_IP_4>:9180,http://<REDACTED_IP_5>:9180,http://<REDACTED_IP_6>:9180,
Err: socket hang up]]"}
2026-02-03 23:26:15.431 error 2026-02-03T22:26:15.431Z ERROR
provider.client client/client.go:269 failed to execute adc command
{"config":
{"name":"GatewayProxy/k6-api-prod/apisix-config","serverAddrs":["http://<REDACTED_IP_1>:9180","http://<REDACTED_IP_2>:9180","http://<REDACTED_IP_3>:9180","http://<REDACTED_IP_4>:9180","http://<REDACTED_IP_5>:9180","http://<REDACTED_IP_6>:9180"],"tlsVerify":false},
"error": "ADC execution error for GatewayProxy/k6-api-prod/apisix-config:
[ServerAddr:
http://<REDACTED_IP_1>:9180,http://<REDACTED_IP_2>:9180,http://<REDACTED_IP_3>:9180,http://<REDACTED_IP_4>:9180,http://<REDACTED_IP_5>:9180,http://<REDACTED_IP_6>:9180,
Err: socket hang up]"}
2026-02-03 23:26:15.431 error 2026-02-03T22:26:15.431Z ERROR
provider.executor client/executor.go:142 failed to run http sync for
server {"server":
"http://<REDACTED_IP_1>:9180,http://<REDACTED_IP_2>:9180,http://<REDACTED_IP_3>:9180,http://<REDACTED_IP_4>:9180,http://<REDACTED_IP_5>:9180,http://<REDACTED_IP_6>:9180",
"error": "ServerAddr:
http://<REDACTED_IP_1>:9180,http://<REDACTED_IP_2>:9180,http://<REDACTED_IP_3>:9180,http://<REDACTED_IP_4>:9180,http://<REDACTED_IP_5>:9180,http://<REDACTED_IP_6>:9180,
Err: socket hang up"}
2026-02-03 23:26:15.431 error 2026-02-03T22:26:15.431Z ERROR
provider.executor client/executor.go:328 ADC Server sync failed
{"result":
{"status":"all_failed","total_resources":6,"success_count":0,"failed_count":6,"success":[],"failed":[{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-02-03T22:26:15.431Z","synced_at":"0001-01-01T00:00:00Z","reason":"socket
hang
up","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-02-03T22:26:15.431Z","synced_at":"0001-01-01T00:00:00Z","reason":"socket
hang
up","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-02-03T22:26:15.431Z","synced_at":"0001-01-01T00:00:00Z","reason":"socket
hang
up","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-02-03T22:26:15.431Z","synced
_at":"0001-01-01T00:00:00Z","reason":"socket hang
up","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-02-03T22:26:15.431Z","synced_at":"0001-01-01T00:00:00Z","reason":"socket
hang
up","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-02-03T22:26:15.431Z","synced_at":"0001-01-01T00:00:00Z","reason":"socket
hang up","response":{"status":0,"headers":null}}]}, "error": "ADC Server sync
failed: socket hang up"}
```
> If endpoint updates are delayed, this situation may occur temporarily.
Could you clarify whether the problem **recovers automatically after some
time**, or if it **persists for an extended period**?
It recovers after restarting the apisix deployment.
> If it persists for a long time, does **reducing the interval of scheduled
full synchronization** help mitigate the issue, or does the problem remain even
after multiple full sync cycles?
How can I reduce the interval?
--
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]
