Security

Trying to run the Distributed Management Console, getting "ERROR KVStoreIntrospection - failed to get introspection data"

howyagoin
Contributor

Hi,

When trying to Run DMC (ha ha), I've noticed that it's failing to get the introspection data from the kvstore.

05-22-2016 17:52:08.996 +1000 ERROR KVStorageProvider - An error occurred during the last operation ('serverStatus', domain: '2', code: '5'): Failed to connect to target host: 127.0.0.1:8191
05-22-2016 17:52:08.996 +1000 ERROR KVStoreIntrospection - failed to get introspection data
05-22-2016 17:52:09.072 +1000 ERROR KVStorageProvider - An error occurred during the last operation ('serverStatus', domain: '2', code: '5'): Failed to connect to target host: 127.0.0.1:8191
05-22-2016 17:52:09.072 +1000 ERROR KVStoreIntrospection - failed to get introspection data
05-22-2016 17:52:09.142 +1000 ERROR KVStorageProvider - An error occurred during the last operation ('serverStatus', domain: '2', code: '5'): Failed to connect to target host: 127.0.0.1:8191
05-22-2016 17:52:09.142 +1000 ERROR KVStoreIntrospection - failed to get introspection data

There must be something incredibly trivial that I'm missing here - I've set the Splunk Enterprise box to have a KV Store, but haven't created anything in a collections.conf (as it's not clear what needs to be set up for the distributed management console to work).

There's likely something obvious here...hints appreciated.

0 Karma
1 Solution

howyagoin
Contributor

I'm an idiot.

Problem was that mongod copied the server.pem which expired last week; as per another note in Answers I found:

$SPLUNK_HOME/bin/splunk createssl server-cert -d . -n server

And that created another server.pem; likely this is related to the tech-note which Splunk sent out talking about expiring certificates.

Restarted splunk after making a new server.pem, all good.

View solution in original post

howyagoin
Contributor

I'm an idiot.

Problem was that mongod copied the server.pem which expired last week; as per another note in Answers I found:

$SPLUNK_HOME/bin/splunk createssl server-cert -d . -n server

And that created another server.pem; likely this is related to the tech-note which Splunk sent out talking about expiring certificates.

Restarted splunk after making a new server.pem, all good.

Get Updates on the Splunk Community!

Splunk Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...

Introducing Value Insights (Beta): Understand the Business Impact your organization ...

Real progress on your strategic priorities starts with knowing the business outcomes your teams are delivering ...

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...