Deployment Architecture

Splunkweb login is not working

mataharry
Communicator

I'm getting the error message above while trying to login the interface.
In IE, the tab also reads Login - Splunk UNKNOWN_VERSION(000) even though I have a valid license installed.

This is my indexer/deployment-server/search-head/coffe-maker.

1 Solution

yannK
Splunk Employee
Splunk Employee

So your server an indexer, a search-head and a deployment server ?
do you have an idea of how many deployments-clients connects to it ?

Usually when the web interface is not displaying the version, this is because the splunkd (management port 8089) process is not responding to the splunkweb process.

  • because after a restart splunkd is busy (rebuilding the buckets by example)
  • or because too many deployments-clients are connected to splunkd on the port 8089 used also for the deployment.

The short term solution is to disable the deployment-server and change the management port from 8089 to another port (like 8090)
in $SPLUNK_HOME/etc/system/local/web.conf
([settings] mgmtHostPort )
That way the deployment-clients will not be served.

The long term solution is to setup a dedicated deployment server.
see http://splunk-base.splunk.com/answers/26620/how-many-clients-can-one-deployment-server-manage

View solution in original post

yannK
Splunk Employee
Splunk Employee

So your server an indexer, a search-head and a deployment server ?
do you have an idea of how many deployments-clients connects to it ?

Usually when the web interface is not displaying the version, this is because the splunkd (management port 8089) process is not responding to the splunkweb process.

  • because after a restart splunkd is busy (rebuilding the buckets by example)
  • or because too many deployments-clients are connected to splunkd on the port 8089 used also for the deployment.

The short term solution is to disable the deployment-server and change the management port from 8089 to another port (like 8090)
in $SPLUNK_HOME/etc/system/local/web.conf
([settings] mgmtHostPort )
That way the deployment-clients will not be served.

The long term solution is to setup a dedicated deployment server.
see http://splunk-base.splunk.com/answers/26620/how-many-clients-can-one-deployment-server-manage

Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...