This repository has been archived by the owner on Apr 19, 2019. It is now read-only.
Rabbit FQDN Issues returning #39
Assignees
Labels
Comments
|
Fixed in my local branch: andymcc@78ef2ca |
andymcc
added a commit
to andymcc/ansible-lxc-rpc
that referenced
this issue
Sep 1, 2014
Rabbit occassionally fails to start because it can't resolve its "short name" The /etc/hosts file is dropped after the install phase, which starts up rabbit automatically - Moving the /etc/hosts file correction to happen before the install phase will resolve this. Fixes rcbops#39
mancdaz
pushed a commit
to mancdaz/ansible-lxc-rpc
that referenced
this issue
Oct 13, 2014
Rabbit occassionally fails to start because it can't resolve its "short name" The /etc/hosts file is dropped after the install phase, which starts up rabbit automatically - Moving the /etc/hosts file correction to happen before the install phase will resolve this. Fixes rcbops#39
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Friday Aug 29, 2014 at 14:29 GMT
Originally opened as https://github.com/rcbops/ansible-lxc-rpc-orig/issues/486
Rabbit sometimes fails to start because it can't connect to itself (when using anFQDN):
TASK: [rabbit_common | Install rabbit packages] *******************************
failed: [node12.domain.com_rabbit_mq_container-48e7bee8] => (item=rabbitmq-server)
Since the package install starts the package this fails, logs show the following:
rabbit@node12:
hosts shows the following:
root@node12:~# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 node12.domain.com_rabbit_mq_container-48e7bee8
Moving the "Fix /etc/hosts" entry in the rabbit_common to be above the install will fix this.
The text was updated successfully, but these errors were encountered: