Consolidated Troubleshooting Article for Red Hat Satellite 6.x MongoDB-related Issues

Disclaimer:
The articles and solutions referred to here apply to Red Hat Satellite 6.9 and earlier.

Issues

• In Red Hat Satellite mongodb fail to start with pulp_celerybeat
• The mongo engine upgrade to wiredTiger fails with error "`execute': wrong number of arguments (given 1, expected 3) (ArgumentError)" in Satellite 6.9
• Mongod process with wiredTiger engine consumes up to half of RAM in Satellite6
• [Satellite 6] katello-service status returns "Some services failed to status: mongod"
• Getting warnings related to mongodb directory on Red Hat Satellite Capsule server
• The rh-mongodb34-mongod service fails to start with error 'Cannot write pid file to /var/opt/rh/rh-mongodb34/run/mongodb/mongod.pid: Permission denied' in Red Hat Satellite or Capsule 6.
• Satellite 6 Capsule's MongoDB Will Not Start After Installation
• On Red Hat Satellite 6.2 Content view publishing is failing with "There was an issue with the backend service pulp: 500 Internal Server Error (RuntimeError)" error message

How To

• Increasing promote/publish speed in Satellite 6 by compacting mongoDB
• How to repair MongoDB database?
• Repair Stale MongoDB lock file for Satellite 6 pulp_streamer Service
• How to migrate mongoDB storage engine from MMAPv1 to WiredTiger in Satellite 6.5 or later?
• How to restore just mongo database for Satellite 6?

Useful Information

• Memory consumption by different engines used in Mongodb database in Red Hat Satellite 6