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!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...