Issues with new containers created by FMC

jrawlings1980 May 23, 2012 12:08 PM

I have created some remote containers using FMC. Sometimes they do not appear in the list of containers and even when they do they will not start. The logs repeatedly display this error...

org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /fabric/registry/containers/domains/test3

Has anyone seen this before?

FMC_container_error.png 138.1 KB
Stack_FMC_Container.log 10.5 KB

1. Re: Issues with new containers created by FMC

stlewis May 23, 2012 2:02 PM (in response to jrawlings1980)

This tends to happen if the remote container cannot connect back to the fabric server (in this case FMC) to fully register. Typical reasons are that the remote host cannot resolve your local machine's hostname, or the remote process is unable to connect to the fabric registry, often because it's on a machine behind a NAT or firewall and you need to set up some port forwards so that the machine can connect back to your local machine through the NAT device.
Actions
2. Re: Issues with new containers created by FMC

jrawlings1980 May 27, 2012 3:43 PM (in response to stlewis)

Thank you. Yes you were right. I needed to set the server names in the host files.
Actions

Go to original post