Knowledge Management

ERROR: The kvstore port [foo] is already bound. Splunk needs to use this port.

_gkollias
Builder

Hi,

Rather than seeing a mgmt port bound error, I am seeing kvstore port is already bound. I ran ps -aux | grep <port> and noticed a mongod process taking up the port. Does mongod correspond to Splunk's KV store? Just trying to see if there is any connection between the two before killing the process ID and restarting the indexer. Any insight is greatly appreciated.

Thanks in advance

0 Karma
1 Solution

Masa
Splunk Employee
Splunk Employee

Yes, KVStore's engine is tight related to mongodb process built in Splunk package. The port number must be set in [kvstore] stanza in server.conf. If you are not running any Splunk instances and the port is taken by a mongo process, most likely you are safe to kill the process.

View solution in original post

Masa
Splunk Employee
Splunk Employee

Yes, KVStore's engine is tight related to mongodb process built in Splunk package. The port number must be set in [kvstore] stanza in server.conf. If you are not running any Splunk instances and the port is taken by a mongo process, most likely you are safe to kill the process.

Get Updates on the Splunk Community!

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...