https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211660#M7910 <P>When I do this it automatically encrypts the password I set for it. I set the password on the license master and all the licenses slaves and restart the slaves. The password on the license slaves encrypts itself. This answer did not work for me.</P> Mon, 14 Mar 2016 21:08:34 GMT thomas_forbes 2016-03-14T21:08:34Z https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211658#M7908 <P>When upgrading from Splunk Enterprise 6.2.2 to 6.2.5, one no longer sees the license slave on the license master.</P> <P>Tried copying the encrypted "pass4SymmKey" value in etc/system/local/server.conf from license master to license slave (indexer), and restarting both Splunk instances, however this did not resolve the issue and the error remains.</P> <P>How to fix this and allow license slave to be seen on license master?</P> Wed, 02 Sep 2015 01:46:25 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211658#M7908 ostendrh 2015-09-02T01:46:25Z https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211659#M7909 <P>On Splunk Enterprise 6.2.x, Instead of copying the encrypted value of "pass4SymmKey" from the License master to your slave (indexer server), try entering the unencrypted password that you used when initially creating the "pass4SymmKey" on your license master and then restart the Splunk license slave instance. If you don't remember your password, you can change the value on both the Splunk license master and slave and restart both instances. After restart, the password should be encrypted again.</P> Wed, 02 Sep 2015 01:52:51 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211659#M7909 rostendorf_splu 2015-09-02T01:52:51Z https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211660#M7910 <P>When I do this it automatically encrypts the password I set for it. I set the password on the license master and all the licenses slaves and restart the slaves. The password on the license slaves encrypts itself. This answer did not work for me.</P> Mon, 14 Mar 2016 21:08:34 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211660#M7910 thomas_forbes 2016-03-14T21:08:34Z https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211661#M7911 <P>Got this fix to work when I got rid of my pass4SymmKey under my [general] stanza in my original server.conf file. Originally I had only (1) pass4SymmKey in the [general] stanza. I then added a pass4SymmKey to the [clustering] stanza creating (2) pass4Symmkeys. It appears as if the (2) keys were conflicting with each other. </P> <P>Thanks,<BR /> Tom Forbes</P> Mon, 14 Mar 2016 23:06:40 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-error-error-quot-Failed-to-contact-license-master/m-p/211661#M7911 thomas_forbes 2016-03-14T23:06:40Z