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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Automated Threat Analysis: Available in ES Premier

Automated Threat Analysis: Centralize and Accelerate Phishing Investigations in Splunk Enterprise ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...