In slave 2, I notice other values have been set for all ports listed here, including the SlaveRemoteLogPort. These seem to be applied at random every time I try to start the slave.
Hmm. We added a feature for UBL that the Slave binds to a port to detect genuine usage. It’s this setting in the UBL section of “Configure Repository Options”:
If my guess is right, I’m not sure how we can work around it, but I know who wrote it and will discuss with them what our path forward can be.
Do you have Tools > Configure Repository Options > Global Remote Command Port Override set? This sets the same static port for all slaves so the second slave is trying to startup on the same port as the which is already in use.
Alternatively you can disable that feature and then set override for each slave independently to get “Connect to Slave log” working.
Thanks, you’ve hit the nail on the head there! As soon as I turned this off, I was able to startup multiple slaves on all machines.
Glad that this was a trivial issue but I noticed there is no documentation to say that multiple slaves will not launch when this is enabled, can I make a feature request for this?
The problem at the moment is that we need to move that feature to a central application (say the Launcher) before we can do a proper hand-off to multiple Slaves. I’ll add you to an internal ticket here though.
