# Debugging containers in "Initialzing" state w/health checks

**URL:** <https://forums.suse.com/t/debugging-containers-in-initialzing-state-w-health-checks/3331>\
**Category:** Rancher 1.x\
**Created:** [July 6, 2016, 2:13pm UTC](https://forums.suse.com/t/debugging-containers-in-initialzing-state-w-health-checks/3331 "2016-07-06T14:13:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexR](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@alexR](https://forums.suse.com/u/alexR)\
**Post date:** [July 6, 2016, 2:13pm UTC](https://forums.suse.com/t/debugging-containers-in-initialzing-state-w-health-checks/3331/1 "2016-07-06T14:13:20Z")

</div>

Hello Everyone,

I have an environment where services are NOT receiving health checks, I run a simple nginx:latest containter add a health check on port 80 and even though the services work, it is forever stuck in “Initializing”. I’ve read the documentation and understand that agents on other hosts in the environment will do the Health checks. Problem is in the log I don’t see any health checks being done.

I am aware that this might be a networking problem and I’ve flushed my firewall and restarted the docker-engine to be on the safe side, but still I get the failing tests.

How can I troubleshoot this? could some test be doing from the shell inside a container? or something else to check?

I’ve read [https://github.com/rancher/rancher/issues/2516](https://github.com/rancher/rancher/issues/2516) but gotten nowhere.

Any help is appreciated.

Alejandro

Rancher v1.1.0  
Cattle v0.165.4  
User Interface v1.1.12  
Rancher Compose v0.8.5  
Debian Jessie on Bare Metal.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [July 7, 2016, 5:53am UTC](https://forums.suse.com/t/debugging-containers-in-initialzing-state-w-health-checks/3331/2 "2016-07-07T05:53:25Z")

</div>

Do you have multiple hosts? If so, the first thing is to check cross host networking. You can check this by exec-ing into a network agent on one container and pinging the IP (10.42.x.x) of another network agent on another host.

[http://docs.rancher.com/rancher/latest/en/faqs/troubleshooting/#cross-host-communication](http://docs.rancher.com/rancher/latest/en/faqs/troubleshooting/#cross-host-communication)

---

<div class="post-metadata">

**Author:** ![alexR](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@alexR](https://forums.suse.com/u/alexR)\
**Post date:** [July 7, 2016, 7:57am UTC](https://forums.suse.com/t/debugging-containers-in-initialzing-state-w-health-checks/3331/3 "2016-07-07T07:57:50Z")

</div>

Thank you very much @denise, I had not read that part of the docs, very useful.

In my case our hardware servers are configured to use a “bonding” network interface, and I had not explicitly set the CATTLE\_AGENT\_IP when adding the host to the environment.

Great stuff! Thanks again.

Alejandro