# Elastic agent(synthetics) error connecting to fleet
**URL:** https://discuss.elastic.co/t/elastic-agent-synthetics-error-connecting-to-fleet/346669
**Category:** Elastic Agent
**Tags:** metricbeat
**Created:** [November 7, 2023, 11:47pm UTC](https://discuss.elastic.co/t/elastic-agent-synthetics-error-connecting-to-fleet/346669 "2023-11-07T23:47:03Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@senyam08](https://discuss.elastic.co/u/senyam08)
#### Post date: [November 7, 2023, 11:47pm UTC](https://discuss.elastic.co/t/elastic-agent-synthetics-error-connecting-to-fleet/346669/1 "2023-11-07T23:47:03Z")
Deployed elastic stack using ECK operator
Trying to deploy elastic agent as deployment to run synthetics. Deployed fleet server as its required for synthetics elastic agent
Followed the config from below
[https://raw.githubusercontent.com/elastic/cloud-on-k8s/2.9/config/recipes/elastic-agent/fleet-kubernetes-integration.yaml](https://raw.githubusercontent.com/elastic/cloud-on-k8s/2.9/config/recipes/elastic-agent/fleet-kubernetes-integration.yaml)
First issue was agent was not starting up without creating policy manually in kibana UI
Created agent policy and used that synthetics agent config
Elastic agent started up without issue. But i see following error
17:19:01.711
elastic\_agent
[elastic\_agent][warn] Possible transient error during checkin with fleet-server, retrying
17:21:41.873
elastic\_agent
[elastic\_agent][error] ack retrier: commit failed with error: acknowledge 1 actions '[action\_id: policy:3b0f0980-7dc3-11ee-b527-1b8d592e7276:1:1, type: POLICY\_CHANGE]' for elastic-agent '9e6738ff-e837-48b5-a683-822e51abe685' failed: read tcp 10.15.225.60:56824-\>172.20.116.33:8220: read: connection reset by peer
17:22:17.783
elastic\_agent
[elastic\_agent][error] Cannot checkin in with fleet-server, retrying
17:22:42.961
elastic\_agent
[elastic\_agent][info] Updating running component model
17:26:02.920
elastic\_agent
[elastic\_agent][error] ack retrier: commit failed with error: acknowledge 1 actions '[action\_id: policy:3b0f0980-7dc3-11ee-b527-1b8d592e7276:1:1, type: POLICY\_CHANGE]' for elastic-agent '9e6738ff-e837-48b5-a683-822e51abe685' failed: read tcp 10.15.225.60:46850-\>172.20.116.33:8220: read: connection reset by peer
17:27:07.811
elastic\_agent
[elastic\_agent][info] Updating running component model
17:27:07.916
elastic\_agent
[elastic\_agent][info] Updating running component model
17:27:46.123
elastic\_agent
[elastic\_agent][error] Cannot checkin in with fleet-server, retrying
17:27:48.332
elastic\_agent
[elastic\_agent][info] Updating running component model
17:30:09.351
elastic\_agent
[elastic\_agent][error] ack retrier: commit failed with error: acknowledge 1 actions '[action\_id: policy:3b0f0980-7dc3-11ee-b527-1b8d592e7276:1:1, type: POLICY\_CHANGE]' for elastic-agent '9e6738ff-e837-48b5-a683-822e51abe685' failed: read tcp 10.15.225.60:50596-\>172.20.116.33:8220: read: connection reset by peer
17:32:53.451
elastic\_agent
[elastic\_agent][info] Updating running component model
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 5, 2023, 11:47pm UTC](https://discuss.elastic.co/t/elastic-agent-synthetics-error-connecting-to-fleet/346669/2 "2023-12-05T23:47:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.