Deployment Architecture

On a new Splunk Forwarder installation the Command Line Interface doesn't work when login authentication is needed

thomasaross
New Member

This is on a new installation. Linux OS. The install and setup went smoothly enough and using some canned config files (i.e inputs.conf) everything seems to be working (forwarding and indexing). The problem is using the CLI on the forwarder. As the user "splunk" when I exercise the CLI, I get different results. Some commands (the cheap ones like "./splunk help commands") work. Those that require authentication like "./splunk show server name" responds with "Your session is invalid. Please login." The login always fails despite using the correct username/password. Any ideas as to cause or correction?

0 Karma

lguinn2
Legend

I don't mean to be a jerk, but my bet is that your user name or password is invalid.
Did you change the admin password on the forwarder?

If not, the default user name is admin and the default password is changeme.
You really don't need any other Splunk user on your forwarder except admin.

0 Karma

thomasaross
New Member

Thanks but I (we) did change the admin password and it does work from the web console. Right now, because it says "...session invalid" it seems to not recognize the "splunk" user, so I believe it isn't a password problem by itself.

0 Karma
Get Updates on the Splunk Community!

Dashboards: Hiding charts while search is being executed and other uses for tokens

There are a couple of features of SimpleXML / Classic dashboards that can be used to enhance the user ...

Splunk Observability Cloud's AI Assistant in Action Series: Explaining Metrics and ...

This is the fourth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how ...

Brains, Bytes, and Boston: Learn from the Best at .conf25

When you think of Boston, you might picture colonial charm, world-class universities, or even the crack of a ...