# Unable to initialize Fleet in v8.0.0

**URL:** https://discuss.elastic.co/t/unable-to-initialize-fleet-in-v8-0-0/296968
**Category:** Kibana
**Tags:** fleet
**Created:** [February 11, 2022, 11:34am UTC](https://discuss.elastic.co/t/unable-to-initialize-fleet-in-v8-0-0/296968 "2022-02-11T11:34:03Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)
#### Post date: [February 11, 2022, 11:01pm UTC](https://discuss.elastic.co/t/unable-to-initialize-fleet-in-v8-0-0/296968/4 "2022-02-11T23:01:09Z")

</div>

@Amine27 , @vvlad

Resolved it by finding out the Packages ID's for Elasticsearch, Logstash and Kibana... the ones at fault and then deleting them, checking if they existed in other policies by checking the stat to be 100% sure those integrations were deleted.

[http://192.168.0.156:5601/api/fleet/package\_policies](http://192.168.0.156:5601/api/fleet/package_policies) -\> get the policy id's

 ![Screen Shot 2022-02-12 at 12.01.59 AM](https://us1.discourse-cdn.com/elastic/original/3X/3/4/34ced9fcd174ed0be3d561956eb4f8211e595f0c.jpeg)

 ![Screen Shot 2022-02-11 at 11.56.38 PM](https://us1.discourse-cdn.com/elastic/original/3X/c/e/ce34afbfe47950a78ba03dc7459dcfb069cb3c77.png)  
 ![Screen Shot 2022-02-11 at 11.56.57 PM](https://us1.discourse-cdn.com/elastic/original/3X/1/b/1ba05ee61fb3ced7f57e6a65f8fe811efaaf4ff7.png)  
 ![Screen Shot 2022-02-11 at 11.57.16 PM](https://us1.discourse-cdn.com/elastic/original/3X/4/3/43bab52f8ffdc72eeb71af0e4f921c33c7b3a220.png)

---

_[View the full topic](https://discuss.elastic.co/t/unable-to-initialize-fleet-in-v8-0-0/296968)._