About emayssat

emayssat · ‎09-12-2016

It turns out that this is a bash human error. '${SPLUNK_USER}:${SPLUNK_PASSWORD}' doesn't expend in bash. The expansion only happens if it is double quoted.

emayssat · ‎08-29-2016

To install the splunkforwarder to connect to Splunk Cloud, at boot time, I run splunk set servername -auth admin: , which fails as follow: But I get the following error: 2016-08-29 23:21:01,589 P1647 [INFO] + /opt/splunkforwarder/bin/splunk set servername zookeeper1.logs001msi.us-west-1a.i-250d4d60.54-183-105-58.374244366136 -auth '${SPLUNK_USER}:${SPLUNK_PASSWORD}' 2016-08-29 23:21:01,589 P1647 [INFO] Could not look up HOME variable. Auth tokens cannot be cached. *** 2016-08-29 23:21:01,589 P1647 [INFO] Login failed *** 2016-08-29 23:21:01,589 P1647 [INFO] + /opt/splunkforwarder/bin/splunk edit monitor /var/log -auth '${SPLUNK_USER}:${SPLUNK_PASSWORD}' 2016-08-29 23:21:01,589 P1647 [INFO] Could not look up HOME variable. Auth tokens cannot be cached. 2016-08-29 23:21:01,589 P1647 [INFO] Login failed Is there a way to get around this? Best,

emayssat · ‎07-05-2016

I am reconfiguring the universal splunk forwarder to connect to splunk cloud. With the CLI, I am able to setup forward-server and monitors, but my forward server are always 'inactive'. I obviously need to install the right credentials. Where can I find those credentails? http://docs.splunk.com/Documentation/SplunkCloud/6.4.0/User/ForwardDataToSplunkCloudFromLinux Step 4 doesn't help as I don't have a 'Universal Forwarder' button/link on the left !!!!

Posts	3
Solutions	1
Karma Given	0
Karma Received	1
Member Since	‎07-05-2016

Online Status	Offline
Date Last Visited	‎06-05-2020 02:04 AM

Getting error "Could not look up HOME variable. Au...

Where are my splunkcloud credentials?

Re: Getting error "Could not look up HOME variable...

Getting error "Could not look up HOME variable. Au...

Where are my splunkcloud credentials?