Did you find a solution for this challenge? ... View more

There are a few tasks that are only available with the CM. Monitor fix up tasks, observe -remove excess buckets, and index specific related tasks. We added a dashboard in MC that monitors the MC progress for the above mentioned tasks too. HTHs ... View more

How did you validate that you can connect to the license master? ... View more

You can use these keys to validate the integrity of your private key, CSR, and pem. The STDIN values should all match. openssl rsa -noout -modulus -in splunk.key | openssl md5 (stdin)= ca1cc4ca1dbe1a6cfda25eb5c2703fb1 openssl req -noout -modulus -in Your-splunk.csr | openssl md5 (stdin)= ca1cc4ca1dbe1a6cfda25eb5c2703fb1 openssl x509 -noout -modulus -in splunk.pem | openssl md5 (stdin)= ca1cc4ca1dbe1a6cfda25eb5c2703fb1 The incorrect value should illustrate which ssl component has a problem. HTHs ... View more

I have not had much luck with the web_service.log for troubleshooting. Can you restart splunk, then run a tail -300 on the /opt/splunk/var/log/splunk/splunkd.log and post the results here? There should be an entry similar to this: -0600 ERROR SSLCommon - Can't read certificate file /opt/splunk/etc/auth/MYSPLUNKCERTS & Key/splunk-Hostname-Private.key errno=33558530 error:02001002:system library:fopen:No such file or directory -0600 ERROR HTTPServer - SSL context could not be created - error in cert or password is wrong -0600 ERROR HTTPServer - SSL will not be enabled That may provide better suggest to debug ... View more