Monitoring Splunk

mongod exited abnormally (exit code 1, status: exited with code 1) - look at mo ERROR: Failed to fix non-voting members Priority value during mongod version miReason: ERROR while running mongod-fix-voting-priority migration.

srampally
Path Finder

mongod exited abnormally (exit code 1, status: exited with code 1) - look at mo
ERROR: Failed to fix non-voting members Priority value during mongod version miReason:
ERROR while running mongod-fix-voting-priority migration.

when i upgrade to 7.1.5 i get this error when i start --accept-license

please help me

Tags (1)
0 Karma

dkeck
Influencer

Hi
Looks like this user had the same problem, have a look at this answer

https://answers.splunk.com/answers/712300/upgrade-to-72-fails-with-error-while-running-mongo.html

0 Karma

dkeck
Influencer

Please accept the answer if it helped you 🙂 thank you

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...