Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-32598

sudo systemctl start mongod is a noop when server shutdown using a separate method

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 3.2.18
    • Fix Version/s: None
    • Component/s: Packaging
    • Labels:
      None
    • Environment:
      Centos 7.4
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      1. sudo systemctl start mongod
      2. mongo --eval 'db.getSiblingDB("admin").shutdownServer()'
      3. sudo systemctl start mongod
      4. mongo
    • Sprint:
      Build Expedite
    • Case:

      Description

      Service is not flagged as down when the server is shutdown via kill or db.shutdownServer().

      One workaround is to restart the service instead of starting it: sudo systemctl restart mongod

      [root@centos74 ~]# systemctl status -l mongod
      ‚óŹ mongod.service - SYSV: Mongo is a scalable, document-oriented database.
         Loaded: loaded (/etc/rc.d/init.d/mongod; bad; vendor preset: disabled)
         Active: active (exited) since Tue 2018-01-09 16:01:15 UTC; 3min 46s ago
           Docs: man:systemd-sysv-generator(8)
        Process: 7448 ExecStop=/etc/rc.d/init.d/mongod stop (code=exited, status=0/SUCCESS)
        Process: 7464 ExecStart=/etc/rc.d/init.d/mongod start (code=exited, status=0/SUCCESS)
       Main PID: 4133 (code=killed, signal=KILL)
       
      Jan 09 16:01:15 centos74.vagrant.dev systemd[1]: Starting SYSV: Mongo is a scalable, document-oriented database....
      Jan 09 16:01:15 centos74.vagrant.dev runuser[7476]: pam_unix(runuser:session): session opened for user mongod by (uid=0)
      Jan 09 16:01:15 centos74.vagrant.dev mongod[7464]: Starting mongod: [  OK  ]
      Jan 09 16:01:15 centos74.vagrant.dev systemd[1]: Started SYSV: Mongo is a scalable, document-oriented database..
       
      [root@centos74 ~]# pgrep -lfa mongod
       
      [root@centos74 ~]# mongo
      MongoDB shell version: 3.2.18
      connecting to: test
      2018-01-09T16:05:18.965+0000 W NETWORK  [thread1] Failed to connect to 127.0.0.1:27017, in(checking socket for error after poll), reason: errno:111 Connection refused
      2018-01-09T16:05:18.965+0000 E QUERY    [thread1] Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed :
      connect@src/mongo/shell/mongo.js:229:14
      @(connect):1:6
       
      exception: connect failed
      

      Host details:

      cat /etc/redhat-release
      CentOS Linux release 7.4.1708 (Core)
       
      uname -a
      Linux centos74.vagrant.dev 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
       
      systemctl  --version
      systemd 219
      +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
       
      rpm -qva | grep mongo
      mongodb-enterprise-shell-3.2.18-1.el7.x86_64
      mongodb-enterprise-mongos-3.2.18-1.el7.x86_64
      mongodb-enterprise-tools-3.2.18-1.el7.x86_64
      mongodb-enterprise-3.2.18-1.el7.x86_64
      mongodb-enterprise-server-3.2.18-1.el7.x86_64
      

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: