topic Re: Changing Management port from 8089 in Security

Changing Management port from 8089

chimbudp — Mon, 22 Apr 2013 10:33:46 GMT

Today , i got an Error -

The splunkd daemon cannot be reached by splunkweb. Check that there are no blocked network ports or that splunkd is still running

So , i Changed the management port from 8089 to 8090 ... Now its working fine.
Is there any other places i need to update this new Change ?
What is the effect if i suddenly Change my mgmt port to a new port ?

please help..

Re: Changing Management port from 8089

kristian_kolb — Mon, 22 Apr 2013 10:46:14 GMT

The management port is used for several different things;

-distributed search (indexers will receive search jobs on this port)
-deployment traffic (the deployment server listens on the mgmt port)
-searching (local splunkweb -> local splunkd communication)

Incorrectly changing the management port in some part of your splunk landscape, can cause some or all of the above functions to fail.

Re: Changing Management port from 8089

chimbudp — Mon, 22 Apr 2013 11:17:02 GMT

I have Changed the mgmt port via Command prompt. While trying to restart Splunkd. It shown , the management is blocked. Do u want to configure some other port ?: Y/N
So , i change to 8089 from 8089 . Was this okay ?

Re: Changing Management port from 8089

kristian_kolb — Mon, 22 Apr 2013 11:34:29 GMT

Assume you meant to write "to 8090 from 8089". Yes this will most likely not cause trouble in a single splunk scenario. Since Splunk prompts you to change the port, it'll hopefully make any other required changes, such as CLI->splunkd or splunkweb->splunkd.

However, if this splunk instance also acts as a deployment server, you'll need to update all deployment-clients to reflect the new config.

The same applies for any search head (if this is an indexer).

The questions is why the port is blocked. Is it used by any other process, or could it be some remnants of a previous splunk crash?