MongoDB Replication Set Configuration Issue on CentOS 7












0















My mongodb instance will not run as standalone and I haven't been able to discover why. Its probably something simple. Please point me in the right direction.



Linux myserver 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

mongo -version
MongoDB shell version v4.0.6


running the command:





mongo --host 10.0.0.7/admin --port 27017 -u user -p mypassword





returns:



MongoDB shell version v3.4.13
connecting to: mongodb://admin:27017/?replicaSet=10.0.0.7
2019-03-06T00:54:32.412-0500 I NETWORK [thread1] Starting new replica set monitor for 10.0.0.7/admin:27017
2019-03-06T00:54:32.414-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known
2019-03-06T00:54:32.414-0500 W NETWORK [thread1] No primary detected for set 10.0.0.7
2019-03-06T00:54:32.414-0500 I NETWORK [thread1] All nodes for set 10.0.0.7 are down. This has happened for 1 checks in a row.
2019-03-06T00:54:32.914-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known


So I logged into mongo shell on the host and ran:



use admin
show users



{
"_id" : "admin.myname",
"user" : "myname",
"db" : "admin",
"roles" : [
{
"role" : "readWriteAnyDatabase",
"db" : "admin"
},
{
"role" : "root",
"db" : "admin"
},
{
"role" : "userAdminAnyDatabase",
"db" : "admin"
}
],
"mechanisms" : [
"SCRAM-SHA-1",
"SCRAM-SHA-256"
] }


and




rs.status()




{
"ok" : 0,
"errmsg" : "not running with --replSet",
"code" : 76,
"codeName" : "NoReplicationEnabled"
}


Mongd.conf



# mongod.conf

# for documentation of all options, see:
# http://docs.mongodb.org/manual/reference/configuration-options/

# where to write logging data.
systemLog:
destination: file
logAppend: true
path: /var/log/mongodb/mongod.log

# Where and how to store data.
storage:
# dbPath: /var/lib/mongo
dbPath: /data/mongo
journal:
enabled: true
# engine:
# mmapv1:
# wiredTiger:

# how the process runs
processManagement:
fork: true # fork and run in background
pidFilePath: /var/run/mongodb/mongod.pid # location of pidfile
timeZoneInfo: /usr/share/zoneinfo

# network interfaces
net:
port: 27017
# bindIp: 127.0.0.1 # Enter 0.0.0.0,:: to bind to all IPv4 and IPv6 addresses or, alternatively, use the net.bindIpAll setting.
bindIpAll: true

security:
authorization: "enabled"

#operationProfiling:

#replication:

#sharding:

## Enterprise-Only Options

#auditLog:

#snmp:








share







New contributor




Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    My mongodb instance will not run as standalone and I haven't been able to discover why. Its probably something simple. Please point me in the right direction.



    Linux myserver 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

    mongo -version
    MongoDB shell version v4.0.6


    running the command:





    mongo --host 10.0.0.7/admin --port 27017 -u user -p mypassword





    returns:



    MongoDB shell version v3.4.13
    connecting to: mongodb://admin:27017/?replicaSet=10.0.0.7
    2019-03-06T00:54:32.412-0500 I NETWORK [thread1] Starting new replica set monitor for 10.0.0.7/admin:27017
    2019-03-06T00:54:32.414-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known
    2019-03-06T00:54:32.414-0500 W NETWORK [thread1] No primary detected for set 10.0.0.7
    2019-03-06T00:54:32.414-0500 I NETWORK [thread1] All nodes for set 10.0.0.7 are down. This has happened for 1 checks in a row.
    2019-03-06T00:54:32.914-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known


    So I logged into mongo shell on the host and ran:



    use admin
    show users



    {
    "_id" : "admin.myname",
    "user" : "myname",
    "db" : "admin",
    "roles" : [
    {
    "role" : "readWriteAnyDatabase",
    "db" : "admin"
    },
    {
    "role" : "root",
    "db" : "admin"
    },
    {
    "role" : "userAdminAnyDatabase",
    "db" : "admin"
    }
    ],
    "mechanisms" : [
    "SCRAM-SHA-1",
    "SCRAM-SHA-256"
    ] }


    and




    rs.status()




    {
    "ok" : 0,
    "errmsg" : "not running with --replSet",
    "code" : 76,
    "codeName" : "NoReplicationEnabled"
    }


    Mongd.conf



    # mongod.conf

    # for documentation of all options, see:
    # http://docs.mongodb.org/manual/reference/configuration-options/

    # where to write logging data.
    systemLog:
    destination: file
    logAppend: true
    path: /var/log/mongodb/mongod.log

    # Where and how to store data.
    storage:
    # dbPath: /var/lib/mongo
    dbPath: /data/mongo
    journal:
    enabled: true
    # engine:
    # mmapv1:
    # wiredTiger:

    # how the process runs
    processManagement:
    fork: true # fork and run in background
    pidFilePath: /var/run/mongodb/mongod.pid # location of pidfile
    timeZoneInfo: /usr/share/zoneinfo

    # network interfaces
    net:
    port: 27017
    # bindIp: 127.0.0.1 # Enter 0.0.0.0,:: to bind to all IPv4 and IPv6 addresses or, alternatively, use the net.bindIpAll setting.
    bindIpAll: true

    security:
    authorization: "enabled"

    #operationProfiling:

    #replication:

    #sharding:

    ## Enterprise-Only Options

    #auditLog:

    #snmp:








    share







    New contributor




    Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      My mongodb instance will not run as standalone and I haven't been able to discover why. Its probably something simple. Please point me in the right direction.



      Linux myserver 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

      mongo -version
      MongoDB shell version v4.0.6


      running the command:





      mongo --host 10.0.0.7/admin --port 27017 -u user -p mypassword





      returns:



      MongoDB shell version v3.4.13
      connecting to: mongodb://admin:27017/?replicaSet=10.0.0.7
      2019-03-06T00:54:32.412-0500 I NETWORK [thread1] Starting new replica set monitor for 10.0.0.7/admin:27017
      2019-03-06T00:54:32.414-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known
      2019-03-06T00:54:32.414-0500 W NETWORK [thread1] No primary detected for set 10.0.0.7
      2019-03-06T00:54:32.414-0500 I NETWORK [thread1] All nodes for set 10.0.0.7 are down. This has happened for 1 checks in a row.
      2019-03-06T00:54:32.914-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known


      So I logged into mongo shell on the host and ran:



      use admin
      show users



      {
      "_id" : "admin.myname",
      "user" : "myname",
      "db" : "admin",
      "roles" : [
      {
      "role" : "readWriteAnyDatabase",
      "db" : "admin"
      },
      {
      "role" : "root",
      "db" : "admin"
      },
      {
      "role" : "userAdminAnyDatabase",
      "db" : "admin"
      }
      ],
      "mechanisms" : [
      "SCRAM-SHA-1",
      "SCRAM-SHA-256"
      ] }


      and




      rs.status()




      {
      "ok" : 0,
      "errmsg" : "not running with --replSet",
      "code" : 76,
      "codeName" : "NoReplicationEnabled"
      }


      Mongd.conf



      # mongod.conf

      # for documentation of all options, see:
      # http://docs.mongodb.org/manual/reference/configuration-options/

      # where to write logging data.
      systemLog:
      destination: file
      logAppend: true
      path: /var/log/mongodb/mongod.log

      # Where and how to store data.
      storage:
      # dbPath: /var/lib/mongo
      dbPath: /data/mongo
      journal:
      enabled: true
      # engine:
      # mmapv1:
      # wiredTiger:

      # how the process runs
      processManagement:
      fork: true # fork and run in background
      pidFilePath: /var/run/mongodb/mongod.pid # location of pidfile
      timeZoneInfo: /usr/share/zoneinfo

      # network interfaces
      net:
      port: 27017
      # bindIp: 127.0.0.1 # Enter 0.0.0.0,:: to bind to all IPv4 and IPv6 addresses or, alternatively, use the net.bindIpAll setting.
      bindIpAll: true

      security:
      authorization: "enabled"

      #operationProfiling:

      #replication:

      #sharding:

      ## Enterprise-Only Options

      #auditLog:

      #snmp:








      share







      New contributor




      Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      My mongodb instance will not run as standalone and I haven't been able to discover why. Its probably something simple. Please point me in the right direction.



      Linux myserver 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

      mongo -version
      MongoDB shell version v4.0.6


      running the command:





      mongo --host 10.0.0.7/admin --port 27017 -u user -p mypassword





      returns:



      MongoDB shell version v3.4.13
      connecting to: mongodb://admin:27017/?replicaSet=10.0.0.7
      2019-03-06T00:54:32.412-0500 I NETWORK [thread1] Starting new replica set monitor for 10.0.0.7/admin:27017
      2019-03-06T00:54:32.414-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known
      2019-03-06T00:54:32.414-0500 W NETWORK [thread1] No primary detected for set 10.0.0.7
      2019-03-06T00:54:32.414-0500 I NETWORK [thread1] All nodes for set 10.0.0.7 are down. This has happened for 1 checks in a row.
      2019-03-06T00:54:32.914-0500 I NETWORK [thread1] getaddrinfo("admin") failed: Name or service not known


      So I logged into mongo shell on the host and ran:



      use admin
      show users



      {
      "_id" : "admin.myname",
      "user" : "myname",
      "db" : "admin",
      "roles" : [
      {
      "role" : "readWriteAnyDatabase",
      "db" : "admin"
      },
      {
      "role" : "root",
      "db" : "admin"
      },
      {
      "role" : "userAdminAnyDatabase",
      "db" : "admin"
      }
      ],
      "mechanisms" : [
      "SCRAM-SHA-1",
      "SCRAM-SHA-256"
      ] }


      and




      rs.status()




      {
      "ok" : 0,
      "errmsg" : "not running with --replSet",
      "code" : 76,
      "codeName" : "NoReplicationEnabled"
      }


      Mongd.conf



      # mongod.conf

      # for documentation of all options, see:
      # http://docs.mongodb.org/manual/reference/configuration-options/

      # where to write logging data.
      systemLog:
      destination: file
      logAppend: true
      path: /var/log/mongodb/mongod.log

      # Where and how to store data.
      storage:
      # dbPath: /var/lib/mongo
      dbPath: /data/mongo
      journal:
      enabled: true
      # engine:
      # mmapv1:
      # wiredTiger:

      # how the process runs
      processManagement:
      fork: true # fork and run in background
      pidFilePath: /var/run/mongodb/mongod.pid # location of pidfile
      timeZoneInfo: /usr/share/zoneinfo

      # network interfaces
      net:
      port: 27017
      # bindIp: 127.0.0.1 # Enter 0.0.0.0,:: to bind to all IPv4 and IPv6 addresses or, alternatively, use the net.bindIpAll setting.
      bindIpAll: true

      security:
      authorization: "enabled"

      #operationProfiling:

      #replication:

      #sharding:

      ## Enterprise-Only Options

      #auditLog:

      #snmp:






      replication mongodb centos-7





      share







      New contributor




      Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 5 mins ago









      Reenactor RobReenactor Rob

      1011




      1011




      New contributor




      Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Reenactor Rob is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Reenactor Rob is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231427%2fmongodb-replication-set-configuration-issue-on-centos-7%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Reenactor Rob is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Reenactor Rob is a new contributor. Be nice, and check out our Code of Conduct.













          Reenactor Rob is a new contributor. Be nice, and check out our Code of Conduct.












          Reenactor Rob is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231427%2fmongodb-replication-set-configuration-issue-on-centos-7%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          SQL Server 17 - Attemping to backup to remote NAS but Access is denied

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          Restoring from pg_dump with foreign key constraints