- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to Bind IP - Splunk Issue - OOps the server encountered unexpected Condition
Hello All,
I found an wired problem/defect. Not sure whether you are getting the same.
Issue: I am unable to Bind IP and getting error 'OOps the server encountered unexpected Condition '
Followed the : https://docs.splunk.com/Documentation/Splunk/8.0.3/Admin/BindSplunktoanIP
It's related to editing the correct 'web.conf' file.
The document basically not telling which 'web.conf' file to edit. There are Eight 'web.conf' files in total.
if you try coping 'web.conf' from 'Defaullt' folder into 'local' folder and editing 'mgmtHostPort' (with correct IP port etc,) it still does not work.
Resolution : if you edit 'web.conf' file (for mgmtHostPort) in the below location, it works perfectly i.e. you are able to launch the Splunk with 'IP address:8000' port.
C:/Programme Files/Splunk/var/run/splunk/merged/web.conf
However: If you restart Splunk Enterprise via the web console i.e. 'Restart button' within the application. The settings goes and you need to do it again. If you restart via Microsoft services>splunkd.service -- there is no problem.
Environment Used : Splunk Enterprise - 9.3.1 (On-prem) OS : Windows Server 2022
Also tried on Splunk Enterprise - 9.2.1 (On-prem) - Has same problem.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

https://docs.splunk.com/Documentation/Splunk/latest/admin/Wheretofindtheconfigurationfiles
This is how Splunk merges settings from all the configuration files to create an effective configuration which will be applied.
