Unable to connect to the remote server No connection could be made because the target machine actively refused it xxx.xxx.xxx.xxx:8088
2. The HEC was enabled in the Global Settings but still it not seeing anything listening on port 8088.
3. Getting the below errors while running any commands in command line.
$SPLUNK_HOME/bin/splunk list monitorWarning: Attempting to revert the SPLUNK_HOME ownershipWarning: Executing "chown -R splunk:splunk /opt/splunkforwarder"Couldn't change ownership for /opt/splunkforwarder/var/log/splunk: Operation not permittedNot Found
1. Check that the HEC Token is correctly configured in both, the script and the inputs.conf file.
2. Confirm that HEC is enabled in the Global Settings.
3. On Network Setting ort 8088 needs to be open and correctly configured.
a. Executed the following command but nothing was amiss
netstat -an | grep 8088
4. Restart Splunk: Sometimes, a simple restart of your Splunk Instance can resolve issues related to the upgrade.
5. Search (SPL):
index = hec_index but could not see any data post the upgrade.
6. Execute command, but nothing was found
$SPLUNK_HOME/bin/splunk list monitor
7. Check the user:
ps -ef
1. Improvements to Universal Forwarder (UF) security, including the limiting of access to the UF management port to only the local machine.
2. Change the settings by following the path $SPLUNK_HOME/etc/system/local/server.conf
[httpServer]
mgmtMode = tcp
[httpServer]
* Set stand-alone HTTP settings for splunkd under this stanza name.
* Follow this stanza name with any number of the following setting/value
pairs.
* If you do not specify an entry for each setting, splunkd uses the default
value.mgmtMode = none|auto|tcp
* Sets the transport layer protocol mode for Splunk CLI management commands.
* A value of "none" means that only Splunk CLI commands that can be run
offline are available for use on the instance.
* A value of "auto" means that CLI commands execute over a Unix Domain Socket (UDS),
which represents as $SPLUNK_HOME/var/run/splunk/cli.socket on the file system.
* If the OS does not support UDS, and if 'disableDefaultPort' has a value of "false",
the CLI executes over the splunkd management port.
* If 'disableDefaultPort' has a value of "true", only CLI commands that can be
run offline are available for use on the instance.
* A value of "tcp" means the CLI commands execute over the splunkd
management port.
* This setting is only available on the universal forwarder.
* NOTE: There is a path length limit of 104-108 characters for the UDS socket file. This includes
whatever the $SPLUNK_HOME environment variable expands to. If you exceed this length for the
socket file, UDS does not work, and you must reinstall the universal forwarder, because you cannot
take corrective action to fix the UDS path. Verify the UDS path length when configuring this setting.
* Default: auto
3. By setting this stanza, both 8088 & 8089 are listening, and the commands start to give output.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |