Different beacon/tangodb see the same tango devices
I'll post this for future reference but it is difficult to reproduce (@matias.guijarro you may add info). If I encounter this again I will add more info.
- I start beacon-server on two different machines (called machine1 and machine2)
machine1:wout/dev/bliss % beacon-server --db_path=.../wout/dev/bliss/test_configuration --port=59341 --tango_port=37632 --redis_port=49220 --webapp_port=60049 --redis_socket=/tmp/bliss_testenv_ph7i025c/redis_8skkoe.sock
machine2:wout/dev/bliss % beacon-server --db_path=.../wout/dev/bliss/test_configuration --port=34641 --tango_port=50665 --redis_port=34791 --webapp_port=53648 --redis_socket=/tmp/bliss_testenv_ug60pbob/redis_fad5ma.sock
They have nothing in common, except for the db_path (which means the yaml files and beacon.rdb).
- I start a tango server on machine 1 with the tango database on machine 1
machine1:wout/dev/bliss % BEACON_HOST=machine1:59341 TANGO_HOST=machine1:37632 NexusWriterService test --log=info
- Starting a tango server on machine 2 with the tango database on machine 2 says that the server is already running
machine2:wout/dev/bliss % BEACON_HOST=machine2:34641 TANGO_HOST=machine2:50665 NexusWriterService test --log=info
and if you do
TANGO_HOST=machine2:50665 jive
the device info shows the tango server running on machine1, eventhough this is the tango database running an machine 2.
Edited by Wout De Nolf