Month: February 2018

Determine which Runbook Server ran a runbook instance

When you’re troubleshooting an issue with a runbook and you have multiple runbook servers, it can be useful to know which runbook server the runbook was executed on. Recently I found myself in such a situation, and after a quick google search I couldn’t find any method of finding the runbook server. I decided to

Splunk: ERR_CONNECTION_ABORTED on port 8089

After updating the SSL certificate on our Splunk servers, I needed to verify that the new SSL certificate was in place and working. I did this by browsing to each server on port 8089. I was able to connect to all of the servers except one: To check that Splunk was listening on the correct