AWS Thinkbox Discussion Forums

remote slave commands not logged in slave history

It seems that remote slave commands (stop slave, restart slave etc) are not being logged in the slave history…

cheers,
laszlo

Thanks! Logged as a bug.

Cheers,
Ryan

Actually, it was already logged as a bug.

It’s currently not targeting 6.1 though. The current plan is to look into it for 6.2.

On a side note, it would be great to have a slave history that includes the initial creation of the slave. Lately I’ve been seeing a lot of secondary slaves that seem to spring into existence without being told to. I look at the slave history for these and I can’t find out who created the slave, which machine the command was sent from, etc. The slave history has 0 entries in it.

Hmm, I’m not sure if that’s even an option. A slave doesn’t appear in the system until it has already launched, and many things can cause the slave to launch (not just a remote command).

Just remembered that the Launcher log on that slave machine should show when that slave was launched, and if it was from a remote command, it might be showing where the remote command came from.

Privacy | Site terms | Cookie preferences