# Fleet server & integrations does not provide log/data **URL:** \ **Category:** Elasticsearch\ **Tags:** docker, fleet\ **Created:** [October 12, 2022, 9:06pm UTC](https://discuss.elastic.co/t/fleet-server-integrations-does-not-provide-log-data/316473 "2022-10-12T21:06:27Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 12, 2022, 9:06pm UTC](https://discuss.elastic.co/t/fleet-server-integrations-does-not-provide-log-data/316473/1 "2022-10-12T21:06:27Z")
Need help on fleet I have recently installed a cluster (8.4.0 docker) and facing issues with fleet/APM integration. Fleet container is running in the same elk server and getting registered with healthy status. However, unable to view APM data/fleet -\>data streams/fleet -\>agent-\> logs. I believe fleet is unable to push the data to ES. ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/6/56dd324b3f1b753d850fabe4a179296bd59e2e76.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/2/f2af0b0a23f64142b27c03f1977cdbf83d6c7ba1.png) I tried to troubleshoot but unable to find much info. Docker-compose file: version: '3.5' services: fleet: image: "[docker.elastic.co/beats/elastic-agent-complete:8.4.0](http://docker.elastic.co/beats/elastic-agent-complete:8.4.0)" container\_name: "elk-fleet" hostname: "elk-fleet" user: root environment: - FLEET\_SERVER\_ENABLE=true - FLEET\_SERVER\_ELASTICSEARCH\_HOST=[https://elkserverfqdn:9200](https://elkserverfqdn:9200) - FLEET\_SERVER\_POLICY\_ID=fleet-server-policy(created with wizad) - FLEET\_SERVER\_SERVICE\_TOKEN=zzzzzzzzzzzzzzzzzzzzzzzzzz - FLEET\_URL=[https://elkserverfqdn:8220](https://elkserverfqdn:8220) - FLEET-SERVER-CERT-CA= cacert.pem - FLEET\_SERVER\_CERT= cert.pem - FLEET\_SERVER\_CERT\_KEY= cert.pem - FLEET\_SERVER\_ELASTICSEARCH\_CA\_TRUSTED\_FINGERPRINT=base64ofcasha256fingerprint - FLEET\_SERVER\_ELASTICSEARCH\_CA= cacert.pem - FLEET\_CA=cacert.pem ports: - 8200:8200 - 8220:8220 (tried insecure options too - FLEET\_SERVER\_ELASTICSEARCH\_INSECURE=true and FLEET\_SERVER\_INSECURE\_HTTP=true) There is only one policy and with fleet server, system & Elastic APM integrations with collection of logs, metrics enabled. However, logs are not observed. Also changed logging level to “debug”. ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/f/8f28bfaf320e3201c3b392f38af7e1f6d6d296ac.png) Fleet Settings: Fleet server hosts: [https://elkserverfqdn:8220](https://elkserverfqdn:8220) (fleet is on elk server) outputs [https://elkserverfqdn:9200](https://elkserverfqdn:9200) ca fingerprint: base64of\_ca\_sha256fingerprint Fleet config: Host: 0.0.0.0 port 8200 APM: Host: 0.0.0.0:8200 url: [http://elkserverfqdn:8200](http://elkserverfqdn:8200) RUM : enabled Agent auth Anonymous enabled; allowed agents “\*” (added) ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c759e6b72a7699c146942d7374ede79f932bd3a5.png) Errors found from fleet container {"log":"{"log.level":"error","@timestamp":"2022-10-12T18:22:01.487Z","log.origin":{"file.name":"process/stdlogger.go","file.line":54},"message":"fleet-server stderr: \"{\\\"level\\\":\\\"info\\\",\\\"time\\\":\\\"2022-10-12T18:22:01Z\\\",\\\"message\\\":\\\"No applicable limit for 0 agents, using default.\\\"}\\n{\\\"level\\\":\\\"info\\\",\\\"time\\\":\\\"2022-10-12T18:22:01Z\\\",\\\"message\\\":\\\"No applicable limit for 0 agents, using default.\\\"}\\n\"","agent.console.name":"fleet-server","agent.console.type":"stderr","ecs.version":"1.6.0"}\n","stream":"stderr","time":"2022-10-12T18:22:01.487682391Z"} {"log":"{"log.level":"error","@timestamp":"2022-10-12T18:22:05.889Z","log.origin":{"file.name":"process/app.go","file.line":290},"message":"failed to stop fleet-server: os: process already finished","ecs.version":"1.6.0"}\n","stream":"stderr","time":"2022-10-12T18:22:05.889309437Z"} {"log":"{"log.level":"error","@timestamp":"2022-10-12T18:22:08.044Z","log.origin":{"file.name":"process/stdlogger.go","file.line":54},"message":"fleet-server stderr: \"{\\\"level\\\":\\\"info\\\",\\\"time\\\":\\\"2022-10-12T18:22:08Z\\\",\\\"message\\\":\\\"No applicable limit for 0 agents, using default.\\\"}\\n{\\\"level\\\":\\\"info\\\",\\\"time\\\":\\\"2022-10-12T18:22:08Z\\\",\\\"message\\\":\\\"No applicable limit for 0 agents, using default.\\\"}\\n\"","agent.console.name":"fleet-server","agent.console.type":"stderr","ecs.version":"1.6.0"}\n","stream":"stderr","time":"2022-10-12T18:22:08.045445124Z"} {"log":"{"log.level":"error","@timestamp":"2022-10-12T18:22:14.556Z","log.origin":{"file.name":"process/stdlogger.go","file.line":54},"message":"filebeat\_monitoring stderr: \"panic: close of closed channel\\n\\ngoroutine 159 [running]:\\ngithub.com/elastic/beats/v7/filebeat/beater.(\*Filebeat).Stop(0xc00072f620\"","agent.console.name":"filebeat\_monitoring","agent.console.type":"stderr","ecs.version":"1.6.0"}\n","stream":"stderr","time":"2022-10-12T18:22:14.55663006Z"} {"log":"{"log.level":"error","@timestamp":"2022-10-12T18:22:14.556Z","log.origin":{"file.name":"process/stdlogger.go","file.line":54},"message":"filebeat\_monitoring stderr: \")\\n\\t/go/src/github.com/elastic/beats/filebeat/beater/filebeat.go:428 +0x46\\ngithub.com/elastic/beats/v7/libbeat/cmd/instance.(\*Beat).launch.func5()\\n\\t/go/src/github.com/elastic/beats/libbeat/cmd/instance/beat.go:461 +0x68\\nsync.(\*Once).doSlow(0xc000647980, 0xc00095b340)\\n\\t/usr/local/go/src/sync/once.go:68 +0x178\\nsync.(\*Once).Do(0xc000647980, 0xc00095b340)\\n\\t/usr/local/go/src/sync/once.go:59 +0x45\\ngithub.com/elastic/elastic-agent-libs/service.HandleSignals.func1()\\n\\t/go/pkg/mod/github.com/elastic/elastic-agent-libs@v0.2.9/service/service.go:60 +0x20c\\ncreated by [github.com/elastic/elastic-agent-libs/service.HandleSignals](http://github.com/elastic/elastic-agent-libs/service.HandleSignals)\\n\\t/go/pkg/mod/github.com/elastic/elastic-agent-libs@v0.2.9/service/service.go:49 +0x268\\n\"","agent.console.name":"filebeat\_monitoring","agent.console.type":"stderr","ecs.version":"1.6.0"}\n","stream":"stderr","time":"2022-10-12T18:22:14.556670107Z"} {"log":"{"log.level":"error","@timestamp":"2022-10-12T18:22:15.504Z","log.origin":{"file.name":"process/stdlogger.go","file.line":54},"message":"metricbeat\_monitoring stderr: \"panic: close of closed channel\\n\\ngoroutine 121 [running]:\\ngithub.com/elastic/beats/v7/metricbeat/beater.(\*Metricbeat).Stop(0xc0009fa1c0)\\n\\t/go/src/github.com/elastic/beats/metricbeat/beater/metricbeat.go:276 +0x28\\ngithub.com/elastic/beats/v7/libbeat/cmd/instance.(\*Beat).launch.func5()\\n\\t/go/src/github.com/elastic/beats/libbeat/cmd/instance/beat.go:461 +0x68\\nsync.(\*Once).doSlow(0xc0005e5110, 0xc0013de680)\\n\\t/usr/local/go/src/sync/once.go:68 +0x178\\nsync.(\*Once).Do(0xc0005e5110, 0xc0013de680)\\n\\t/usr/local/go/src/sync/once.go:59 +0x45\\ngithub.com/elastic/elastic-agent-libs/service.HandleSignals.func1()\\n\\t/go/pkg/mod/github.com/elastic/elastic-agent-libs@v0.2.9/service/service.go:60 +0x20c\\ncreated by [github.com/elastic/elastic-agent-libs/service.HandleSignals](http://github.com/elastic/elastic-agent-libs/service.HandleSignals)\\n\\t/go/pkg/mod/github.com/elastic/elastic-agent-libs@v0.2.9/service/service.go:49 +0x268\\n\"","agent.console.name":"metricbeat\_monitoring","agent.console.type":"stderr","ecs.version":"1.6.0"}\n","stream":"stderr","time":"2022-10-12T18:22:15.504644325Z"} Am I missing something or configuring incorrectly? pls suggest. ---
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 13, 2022, 11:16am UTC](https://discuss.elastic.co/t/fleet-server-integrations-does-not-provide-log-data/316473/2 "2022-10-13T11:16:07Z")
I have found some thing with APM port { "build\_date": "2022-08-18T21:34:52Z", "build\_sha": "4b7eaacb757182da07d8b42166d5650be5511e89", "publish\_ready": false, "version": "8.4.0" } The publish\_ready used to be true for a working APM server. ---
**Author:** ![swchandu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swchandu/32/95295_2.png) [@swchandu](https://discuss.elastic.co/u/swchandu)\ **Post date:** [October 17, 2022, 4:20pm UTC](https://discuss.elastic.co/t/fleet-server-integrations-does-not-provide-log-data/316473/3 "2022-10-17T16:20:00Z")
I have tried many options **and found a workaround.** If the fleetserver/agent is connecting via the http(not https) endpoint of elasticsearch, this is working fine. I am using the command to retrieve fingerprint of CA and used where required.. openssl x509 -fingerprint -sha256 -in ca.pem |grep -i finger |awk -F'=' '{print $2}' |base64|tr '\n' ' ' Is this correct? Does any one has suggestions on this? ---
**Author:** ![Julia\_Bardi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julia_bardi/32/79463_2.png) [@Julia\_Bardi](https://discuss.elastic.co/u/Julia_Bardi)\ **Post date:** [November 21, 2022, 1:23pm UTC](https://discuss.elastic.co/t/fleet-server-integrations-does-not-provide-log-data/316473/5 "2022-11-21T13:23:03Z")
This config doesn't look good, as Fleet should be on 8220 port: Fleet config: Host: 0.0.0.0 port 8200 Does your Elasticsearch and Fleet Server start up without the insecure flags? It is recommended to use the https versions. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 19, 2022, 1:23pm UTC](https://discuss.elastic.co/t/fleet-server-integrations-does-not-provide-log-data/316473/6 "2022-12-19T13:23:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.