The "eucalyptus" service remains in the DISABLED state when using --bind-addr

Follow

Eucalyptus Versions:  3.4+

The "eucalyptus" service remains in the DISABLED state when using --bind-addr on the Cloud Controller (CLC)

Problem

Adding the --bind-addr parameter to eucalyptus.conf on the CLC to shift component communication to a different interface results in the eucalyptus service staying in the "DISABLED" state, as seen in euca-describe-services:

SERVICE eucalyptus              eucalyptus      192.168.1.20             DISABLED        92      http://192.168.1.20:8773/services/Eucalyptus     arn:euca:eucalyptus:::192.168.1.20/

Environment

Eucalyptus CLC using version 3.4 or upwards, with --bind-addr parameter specified in /etc/eucalyptus/eucalyptus.conf.

Resolution

To resolve this issue the --bind-addr parameter must be present in the eucalyptus.conf BEFORE running euca_conf --initialize to create the database. Failure to do this results in the default interface for the eucalyptus service being statically defined in the database, thus modification after initialization will not result in the desired change.  To correct this action you must start from a clean cloud and delete /var/lib/eucalyptus/db and /var/lib/eucalyptus/keys and re-initialize and re-register all components. 

Have more questions? Submit a request

Comments

Powered by Zendesk