Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-2920

Restart of replicaset member, errors in ops manager

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Declined
    • Affects Version/s: None
    • Fix Version/s: No versions
    • Component/s: None
    • Labels:
      None

      Description

      I'm running a replicaset mongo 4.0.21-ent on Red Hat Enterprise Linux Server release 7.9 (Maipo). I'm using ops manager and the mms automation to run mongo services, not the systemd mongo unit file.

      After system patches, I restart a specific replicaset member. I see the member come online in ops manager, but mongo fails to start due to a missing `/var/run/mongodb` to check for an old mongod.pid file.

      Manually, I create the directory and chmod to mongod. Then the mongo service being managed through mms automation comes back online.

      How can I update the mss automation for this one node? The other two nodes don't have a /var/run/mongodb directory and neither has problems when patched. There is no mongodb.pid file at that location on ANY of the nodes.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jason.lubken@pennmedicine.upenn.edu Jason Lubken
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: