Satellite 6 Capsule's MongoDB Will Not Start After Installation

Solution Unverified - Updated

Environment

  • Red Hat Satellite 6.8 capsule software.
    • (Likely to affect other 6.y capsule versions as well as satellite.)
  • Red Hat Enterprise Linux 7 (RHEL 7)

Issue

  • After installation of the capsule software, a number of services will not start.
  • Upon investigation, it is found that MongoDB is the first service to not start.  Other services appear not to start due to their reliance on MongoDB.

Resolution

  • For the internal working of Red Hat Satellite services, it is required to have an IPv6 address on at least the loopback interface.  Re-enable IPv6 functionality.
  • If one desires that the server's IPv6 capability be limited, then follow the instructions in [How do I disable the IPv6 protocol on Red Hat Satellite and/or Red Hat Capsule server?].

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

The RHEL 7 server upon which the capsule software was being installed had its IPv6 stack disabled via an ipv6.disable=1 GRUB2's kernel option.

Diagnostic Steps

The /var/log/messages file shows:

Jan 13 15:39:11 capsule systemd: Starting High-performance, schema-free document-oriented database...

Jan 13 15:39:11 capsule mongodb-scl-helper: about to fork child process, waiting until server is ready for connections.

Jan 13 15:39:11 capsule mongodb-scl-helper: forked process: 16317

Jan 13 15:39:11 capsule mongodb-scl-helper: ERROR: child process failed, exited with error number 100

Jan 13 15:39:11 capsule systemd: rh-mongodb34-mongod.service: control process exited, code=exited status=100

Jan 13 15:39:11 capsule systemd: Failed to start High-performance, schema-free document-oriented database.

Jan 13 15:39:11 capsule systemd: Unit rh-mongodb34-mongod.service entered failed state.

Jan 13 15:39:11 capsule systemd: rh-mongodb34-mongod.service failed.

The /var/opt/rh/rh-mongodb34/log/mongodb/mongod.log file shows:

2021-01-13T15:39:11.915-0600 I CONTROL  [initandlisten] options: { command: [ "run" ], config: "/etc/opt/rh/rh-mongodb34/mongod.conf", net: { bindIp: "127.0.0.1,::1", ipv6: true, port: 27017, unixDomainSocket: { enabled: true, pathPrefix: "/var/opt/rh/rh-mongodb34/run/mongodb" } }, processManagement: { fork: true, pidFilePath: "/var/opt/rh/rh-mongodb34/run/mongodb/mongod.pid" }, storage: { dbPath: "/var/opt/rh/rh-mongodb34/lib/mongodb", engine: "wiredTiger" }, systemLog: { destination: "file", logAppend: true, logRotate: "reopen", path: "/var/opt/rh/rh-mongodb34/log/mongodb/mongod.log", verbosity: 0 } }

2021-01-13T15:39:11.932-0600 I -        [initandlisten] Assertion: 15863:listen(): invalid socket? Address family not supported by protocol src/mongo/util/net/listen.cpp 185
2021-01-13T15:39:11.932-0600 I CONTROL  [initandlisten] 
 0x55e08cf7647a 0x55e08cefbe69 0x55e08c1d86a9 0x55e08c1d8797 0x55e08cf13c32 0x55e08ceda796 0x55e08c1be032 0x55e08c1e2734 0x7facefd2a555 0x55e08c23ff05

The "Address family not supported by protocol" entry in the above indicates the problem.

SBR
Product(s)
Category
Tags

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.