Issue with update-config

I set up a VM using HyperVisor and installed CommCare as a monolith then transferred the drive image to another system with a different LAN configuration. After editing the config files to reflect the new IP and running an update-config I was unable to get services up. After a bit of digging, I noticed the following files still reference the old IP:

/etc/kakfa/config/server.properties
/home/cchq/www/monolith/services/monolith_supervisor_celery_workers.conf
/etc/hosts
/etc/haproxy

the /etc/hosts file had two lines and referenced both old and new IP addresses against the server domain name.

Just to add to the list - other files that required manual editing include:
/etc/elasticsearch-1.7.6/elasticsearch.yml
/etc/haproxy/haproxy.cfg
/etc/monit/conf.d/redis
/etc/monit/conf.d/pgbouncer
/etc/monit/conf.d/postgresql
/etc/monit/conf.d/couchdb2

update-config only updates the CommCareHQ application configuration

This includes django localsettings.py and formplayer application.properties .

You might need to re-run deploy_stack.yml to propagate that sort of change everywhere. There are also more targeted playbooks or tags that can be run, depending on the scope of the change. deploy_stack should run in check mode first, which should let you inspect the diff to see if you’ve missed any files.

1 Like