If the launcher’s repository is set to a different one from what the monitor is set to, the ‘connect to slave log’ right click option will fail with this message:
Connecting to lapro0168…
The slave name provided does not have a machine name or IP address associated with it. The slave may not exist in the repository.
The launcher that is set to a different repo, is it on the same machine as the monitor or the slave?
This is on my machine, i was testing a script on our staging repository, so for a while i’ve set the launcher to the staging repo, and had my monitor connected to that as well. Then i reset the monitor to the live repository, but did not reset the launcher. Our staging repo only has a few slaves in it, while the main repo has all our slaves. So now my launcher was set to the staging repo, and my monitor was set to the live repo. Then i right clicked on a slave and tried to connect to its live log (that particular machine did not exist in the staging repo), and got the failure.
If i then (without shutting down the monitor) reset the launcher’s repo to the live repo as well, the connect to slave log command would start working. The slave itself was active on the live repo
Hmm yes I see. Seems like the issue is that DeadlineCommand is being run for the default repository, instead of the repository that the Monitor that called it. We’ll look into this.