Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-3956

MongoDB creates pid file before running service

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • None
    • mongodb
    • None
    • CentOS 7 (without SELinux)
      MongoDB 3.2.10
      mongodb git commit 5a3ea902e3f69eeb0b5b6b5f441d3d19812b6f22

    Description

      ==> default: Notice: /Stage[main]/Mongodb::Server::Config/File[/etc/mongod.conf]/content: content changed '{md5}511d7600a3ea4e2b3227fc9157af5a7f' to '{md5}fa1a5424c80c2618372431ef1571f209'
      ==> default: Notice: /Stage[main]/Mongodb::Server::Config/File[/var/lib/mongodb]/ensure: created
      ==> default: Notice: /Stage[main]/Mongodb::Server::Config/File[/var/run/mongodb/mongod.pid]/ensure: created
      ==> default: Info: Class[Mongodb::Server::Config]: Scheduling refresh of Class[Mongodb::Server::Service]
      ==> default: Info: Class[Mongodb::Server::Service]: Scheduling refresh of Service[mongodb]
      ==> default: Error: Systemd start for mongod failed!
      ==> default: journalctl log for mongod:
      ==> default: -- Logs begin at Sat 2016-10-08 03:52:24 UTC, end at Sat 2016-10-08 03:58:07 UTC. --
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: Starting SYSV: Mongo is a scalable, document-oriented database....
      ==> default: Oct 08 03:58:07 localhost.localdomain mongod[1138]: Error starting mongod. /var/run/mongodb/mongod.pid exists.
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: mongod.service: control process exited, code=exited status=1
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: Failed to start SYSV: Mongo is a scalable, document-oriented database..
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: Unit mongod.service entered failed state.
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: mongod.service failed.
      ==> default: 
      ==> default: Error: /Stage[main]/Mongodb::Server::Service/Service[mongodb]/ensure: change from stopped to running failed: Systemd start for mongod failed!
      ==> default: journalctl log for mongod:
      ==> default: -- Logs begin at Sat 2016-10-08 03:52:24 UTC, end at Sat 2016-10-08 03:58:07 UTC. --
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: Starting SYSV: Mongo is a scalable, document-oriented database....
      ==> default: Oct 08 03:58:07 localhost.localdomain mongod[1138]: Error starting mongod. /var/run/mongodb/mongod.pid exists.
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: mongod.service: control process exited, code=exited status=1
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: Failed to start SYSV: Mongo is a scalable, document-oriented database..
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: Unit mongod.service entered failed state.
      ==> default: Oct 08 03:58:07 localhost.localdomain systemd[1]: mongod.service failed.
      ==> default: 
      ==> default: Notice: /Stage[main]/Mongodb::Server::Service/Service[mongodb]: Triggered 'refresh' from 1 events
      ==> default: Notice: /Stage[main]/Mongodb::Server::Service/Mongodb_conn_validator[mongodb]: Dependency Service[mongodb] has failures: true
      

      Current workaround is:

      sudo rm /var/run/mongodb/mongod.pid
      sudo systemctl start mongod
      sudo puppet agent -t
      

      But I don't think that is an acceptable solution to the problem.

      Attachments

        Activity

          People

            Unassigned Unassigned
            awippler Andrew Wippler
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support