Knowledge Management

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

_gkollias
SplunkTrust
SplunkTrust

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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...