# New Load Balancer stay initializing
**URL:** https://forums.suse.com/t/new-load-balancer-stay-initializing/2287
**Category:** Rancher 1.x
**Created:** [April 2, 2016, 10:28pm UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287 "2016-04-02T22:28:36Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Fernando\_Felicissimo](https://forums.suse.com/u/Fernando_Felicissimo)
#### Post date: [April 2, 2016, 10:28pm UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287/1 "2016-04-02T22:28:36Z")
I installed the Kibana 4 through the catalog on the “Configuration Options” selected “ETCD-discovery” starting dai he created 3 Kibana 1 containers in each Host of my cluster and 1 Load Balance the container start normally but the Load Balance is in status "initializing"
How can I solve this problem? What you guys need information that can help to solve the problem?
thank you,
---
### Author:  [@stan25](https://forums.suse.com/u/stan25)
#### Post date: [April 10, 2016, 12:06pm UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287/2 "2016-04-10T12:06:14Z")
I actually have this same problem when creating a load balancer for my app. It ends up working but always stays in the initializing state and occasionally comes out of that state and changes to Active.
---
### Author:  [@Fernando\_Felicissimo](https://forums.suse.com/u/Fernando_Felicissimo)
#### Post date: [April 11, 2016, 12:12pm UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287/3 "2016-04-11T12:12:20Z")
I managed to figure out the problem … in my case the Node first became configured with the IP PRIVATE and should be with the IP PUBLICO it the agent networks did not communicate … to fix this it was necessary to do the following :
sudo docker run -d -e CATTLE\_AGENT\_IP=\ --privileged
-v /var/run/docker.sock:/var/run/docker.sock
rancher/agent:v0.8.2 http://SERVER\_IP:8080/v1/scripts/xxxx
[http://docs.rancher.com/rancher/faqs/#are-the-ips-of-the-hosts-correct-in-the-ui](http://docs.rancher.com/rancher/faqs/#are-the-ips-of-the-hosts-correct-in-the-ui)
---
### Author:  [@denise](https://forums.suse.com/u/denise)
#### Post date: [April 12, 2016, 4:05am UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287/4 "2016-04-12T04:05:58Z")
@stan25 Are you sure that the hosts have cross host communication?
Typically, load balancers will be stuck in initiliazing because they are unable to pass health checks, which require cross host communication working.
---
### Author:  [@Fernando\_Felicissimo](https://forums.suse.com/u/Fernando_Felicissimo)
#### Post date: [April 12, 2016, 12:13pm UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287/5 "2016-04-12T12:13:55Z")
Hi denise,
As reported above … the problem was fixed after performing the procedure above.
---
### Author:  [@denise](https://forums.suse.com/u/denise)
#### Post date: [April 12, 2016, 4:38pm UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287/6 "2016-04-12T16:38:12Z")
Thanks for the update @Fernando_Felicissimo. I was trying to make sure @stan25 was able to figure out his issue. 🙂
---
### Author:  [@stan25](https://forums.suse.com/u/stan25)
#### Post date: [April 15, 2016, 1:01pm UTC](https://forums.suse.com/t/new-load-balancer-stay-initializing/2287/7 "2016-04-15T13:01:03Z")
Ok I will have to take a look at this. Thanks.