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

Environment

• Red Hat Satellite 6.2

Issue

• Content view publishing fails on satellite server as mongod service is failing to start,error in /var/lib/mongod/mongodb.log:

2017-08-10T15:41:43.297+0530 ***** SERVER RESTARTED *****
2017-08-10T15:41:43.302+0530 ERROR: Cannot write pid file to /var/run/mongodb/mongod.pid: No such file or directory
2017-08-10T15:43:51.447+0530 ***** SERVER RESTARTED *****

• Content view publishing is failing with "There was an issue with the backend service pulp: 500 Internal Server Error (RuntimeError)" error message.

Resolution

• Confirm /var/run/mongodb/ directory exist on the satellite server,if not then follow below steps to create directory or already available fix its permission:

 # mkdir -p /var/run/mongodb/
 # chown -R mongodb:mongodb /var/run/mongodb/
 # service mongod start
 # katello-service restart

• Once all services are up,go ahead and publish the content view.

For more KB articles/solutions related to Red Hat Satellite 6.x MongoDB Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x MongoDB-related Issues

Root Cause

• Mongodb was failing to start as it was not able create /var/run/mongodb/mongod.pid file as the directory was not available on the satellite server.
• Creating the directory with proper permissions and restarting the services fixed this issue.

Diagnostic Steps

• Check for mongodb logs under /var/log/mongod/mongodb.log or /var/lib/mongod/mongodb.log for error messages.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.