Hello,
I'm experiencing some issues with my Cluster Master. The instance for the CM had to be replaced and Splunk was reinstalled on new instance. Configuration was deployed exactly how it was before (CM was working fine) moving to this new instance with the Cluster Master.
The issue is the following:
Failed to contact license master: reason='Unable to connect to license master=https://xxxxxxxx-mc1:8089 Error resolving: Name or service not known'
Thanks to anyone that could lend a helping hand
Hi
this means that your host cannot resolve Your LM hostname. It could be that your node has different domain name or dns it not working. The correct way is to fix your node's DNS to work. Workaround can be to add your LM's IP - Name combination to your local hosts file on this node.
r. Ismo
Thank you all for stepping in for helping me. I'm actively working on applying your recommendations. I'll post back the result once I'm done and hopefully have a working environment, hoping that it will help someone else as well in the future.
Please update the pass4Symm key in server.conf or from clustering UI on CM. Because if you have copied the configuration over, new Splunk might not be able to decrypt the credentials.
Also, make sure you validate all IP addresses information and specifically check the server.conf configuration.
Thanks!
Change it to IPaddress of your LM and it will work.
Hi
never ever use IP address on splunk configurations! That works only if you have static environment where you never need to change anything (like update node to new, switch roles, add new nodes etc), in all other cases it will generate new issues later on.
It’s much better to fix the real issue now than later.
r. Ismo
Yep. Also there can be issues with issuing certificates for IP-s instead of hostnames. It can be done, but some CA's have problems with it and some CA operators have even bigger issues with that practice 😉
Ok @isoutamo , thanks
Hi
this means that your host cannot resolve Your LM hostname. It could be that your node has different domain name or dns it not working. The correct way is to fix your node's DNS to work. Workaround can be to add your LM's IP - Name combination to your local hosts file on this node.
r. Ismo
Thanks everyone!
Your input helped with solving my issue. I added the missing hosts in /etc/hosts and hashed the pass4SymmKey in [general] stanza to generate a new one at restart.