Inspecting the fleet's internal indices, I see that the status is online and is regullary checked
I do not know why is not displaying properly the status in the UI
Thank you @blaker
Just one more data (I don't know if is relevant), just in case:
The installation that is presenting the problem was done via RPM.
I made another installation using the zipped binaries and I observed some difference in the behaviour when enroll/install de fleet server
When enrolling the elastic-agent with the Default Fleet Server Policy (rpm installation), it does all the tasks, it enrolls and the it stops. (In Kibana the status appears as updating but the EA is down)
Then I have to start the agent using systemctl start elastic-agent
When installing the elastic-agent the Default Fleet Server Policy (zipped binary installation) it does all the tasks, it enrolls and the agent remains running. In the Fleet UI appears first as Updating and then as Healthy
Hi @blaker does exists any way to reset all my fleet configuration (deleting indices or something) and try to install the fleet server again?
(I tried unenrolling and enrolling again but same result)
Thank you
Finally I managed to reset all my fleet configurations.
I've installed the fleet server again (using the ziped binary method) and the result is the same.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.