bastien-rcl

Results 14 comments of bastien-rcl

Note that if I previously create the images with `docker compose build` then the setup works. But I'm not sure it was intended to work that way, and I don't...

Thanks for your help. What looks like a possible cause in the Fleet logs is this : ``` {"log.level":"error","@timestamp":"2025-06-11T10:06:04.284Z","message":"failed to fetch elasticsearch version","component":{"binary":"fleet-server","dataset":"elastic_agent.fleet_server","id":"fleet-server-default","type":"fleet-server"},"log":{"source":"fleet-server-default"},"service.type":"fleet-server","error.message":"dial tcp [::1]:9200: connect: connection refused","ecs.version":"1.6.0","service.name":"fleet-server","ecs.version":"1.6.0"} ``` I'm...

Now that I come to think of it, `[::1]`, from `fleet-server`'s perspective is itself, not elastic. And that's perfectly normal that it finds nothing on port 9200 on its own...

From the fleet container : ``` root@fleet-server:/usr/share/elastic-agent# cat elastic-agent.yml ###################################### # Fleet configuration ###################################### outputs: default: type: elasticsearch hosts: '${ELASTICSEARCH_HOSTS:http://elasticsearch:9200}' ``` `$ELASTICSEARCH_HOSTS` is empty so I guess it defaults to...

Thanks @antoineco, maybe my comments above are too verbose, I'll try to summarize them here. The only error log in fleet is ``` {"log.level":"error","@timestamp":"2025-06-11T10:06:04.284Z","message":"failed to fetch elasticsearch version","component":{"binary":"fleet-server","dataset":"elastic_agent.fleet_server","id":"fleet-server-default","type":"fleet-server"},"log":{"source":"fleet-server-default"},"service.type":"fleet-server","error.message":"dial tcp [::1]:9200:...

Yes thanks. I need to wait until outside business hours to fiddle with the server. I will report then.

I did the upgrade to the latest commit, running 9.0.2. I did add the `ELASTICSEARCH_HOST: http://elasticsearch:9200` variable and checked within the running container that it's actually there. The behavior is...

I tried providing a `FLEET_SERVER_SERVICE_TOKEN` previously created from the kibana interface. Before that, the `fleet-server` container exited with code 1 about every 15 seconds. After setting the token, it still...

Yes I have been thinking about wiping it clean. But I really can't afford to lose the data on it. Do you recommend any way to re-initialize without losing any...

Thanks for taking the time to test that. I'm sorry if my issue gave the impression that the main branch was at fault. Just to clarify, the first thing I...