Hello All, Splunk Enterprise version 8.1 Post a recent server crash, our Splunk instance isn't coming up. The splunk service isn’t’ starting despite us having gracefully rebooted the server once. The error is it thinks TCP port 8089 is already occupied by splunk itself despite splunk service not running. Pls see below output. Even if I force kill the process ID related to 8089/TCP, the system automatically spawns a new process ID and shows 8089 as occupied yet again by splunkd. This is going in an endless loop. There is nothing in splunkd.log file to indicate this weird behavior. What is making splunk launch a new process automatically despite us force killing the PID ?