appl/splunkheavyforwarder/etc/system/default/nf connection_timeout = 30 appl/splunkheavyforwarder/etc/apps/wq_full_license_server/local/nf
Being that the error is the rest call (LMMasterRestHandler) someone is calling the Enterprise Instance as a slave, which is not supported on the trial. I am assuming somewhere along the line in your set up, you have either configured the master URI on the HF, or you have configured a setting not supported by the standalone. home/splunker/splunk/etc/system/default/nf strict_pool_quota = true home/splunker/splunk/etc/system/default/nf squash_threshold = 2000 home/splunker/splunk/etc/system/default/nf send_timeout = 30 home/splunker/splunk/etc/system/default/nf report_interval = 1m home/splunker/splunk/etc/system/default/nf receive_timeout = 30 home/splunker/splunk/etc/system/default/nf master_uri = self home/splunker/splunk/etc/system/default/nf connection_timeout = 30 home/splunker/splunk/etc/system/local/nf active_group = Enterprise
home/splunker/splunk/etc/system/local/nf
SPLUNK ENTERPRISE SUPPORT LICENSE
splunk btool server list license -debug on your heavy forwarder, or just log into the Heavy forwarder and check under Settings > Licensing to confirm that is is acting as a master and is not pointing to your Enterprise instance.įor example, here is my standalone License master: bin]$. in the splunk enterprise server I am getting the above error which is mentioned in this post. I am trying to monitor the application logs from 5 servers and forwarding the logs to 6th server, where splunk enterprise and splunk heavy forwarder is installed. from ip=xx.xx.xx.xxġ0-05-2017 17:10:59.926 +0530 ERROR LMMasterRestHandler - path=/masterlm/usage: This license does not support being a remote master. from ip=xx.xx.xx.xxġ0-05-2017 17:08:58.928 +0530 ERROR LMMasterRestHandler - path=/masterlm/usage: This license does not support being a remote master.
0 kommentar(er)
