Getting Data In

How to disable the universal forwarder default management port 8089 with a deployment server?

serwin
Explorer

I'm trying to disable the default management point on the universal forwarders (8089) with the deployment server and I'm having a hard time getting the deployment server to deploy correctly. I have created the app that should disable it and it successfully pushes, but when I do a netstat, it's still listening. Anyone have any advice or see anything I'm doing incorrectly? If I edit the local\server.conf on the test server, it successfully disables the management port.

Thanks!

On the deployment server

deployment-apps\disable_mgmt_app\etc\system\local\server.conf

[httpServer]
disableDefaultPort = true
1 Solution

serwin
Explorer

Actually solved this one myself, when adding the app you don't need to specify directories you just need to place it in deployment-apps/disable_mgmt/local/server.conf and it will work.

View solution in original post

mustapha_arakji
Splunk Employee
Splunk Employee

Snippet from Splunk docs about changing server.conf file:

https://docs.splunk.com/Documentation/Splunk/9.0.0/admin/Serverconf

disableDefaultPort = <boolean>
* If set to "true", turns off listening on the splunkd management port,
  which is 8089 by default.
* On Universal Forwarders, when  this value is "true" the value set 
  for mgmtHostPort in web.conf will be ignored. Similarly, when set to "false", 
  the value set for mgmtHostPort in web.conf will be used for binding management port.
* NOTE: On Universal Forwarders, to reduce the risk of exploitation Splunk recommends 
  the management port is disabled and local CLI is not used. If the management port is enabled, 
  a valid TLS certification should be installed and the port should be bound to localhost.
* NOTE: Changing this setting is not recommended on other Splunk instances.
  * This is the general communication path to splunkd.  If it is disabled,
    there is no way to communicate with a running splunk instance.
  * This means many command line splunk invocations cannot function,
    Splunk Web cannot function, the REST interface cannot function, etc.
  * If you choose to disable the port anyway, understand that you are
    selecting reduced Splunk functionality.
* Default: false

 

0 Karma

serwin
Explorer

Actually solved this one myself, when adding the app you don't need to specify directories you just need to place it in deployment-apps/disable_mgmt/local/server.conf and it will work.

Get Updates on the Splunk Community!

2024 Splunk Career Impact Survey | Earn a $20 gift card for participating!

Hear ye, hear ye! The time has come again for Splunk's annual Career Impact Survey!  We need your help by ...

Optimize Cloud Monitoring

  TECH TALKS Optimize Cloud Monitoring Tuesday, August 13, 2024  |  11:00AM–12:00PM PST   Register to ...

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...