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

mongod server crashed in opensuse

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • ALL

      On OpenSuse, I encountered the following problem

      Here is the output of the user creation, which i created before. For confirmation i again create the same user, mongod confirmed that user exist with this message

      2016-02-13T15:55:24.404-0500 E QUERY Error: couldn't add user: User "admin@admin" already exists

      After restarting mongod with

      sudo mongod --dbpath /data/db1 --auth

      and Login with Access control

      mongo admin --port 27017 -u admin -p root --authenticationDatabase admin

      the console shows the following error

      2016-02-13T15:58:18.527-0500 I NETWORK DBClientCursor::init call() failed 2016-02-13T15:58:18.531-0500 E QUERY Error: 10276 DBClientBase::findN: transport error: 127.0.0.1:27017 ns: admin.$cmd query:

      { saslContinue: 1, payload: BinData(0, 633D626977732C723D353153664E516A722F6D6834303574374D464148582B6C695779444E2F6E4E676E6F4C515530557148612B5A59323548575130394E4C4B484C50773263...), conversationId: 1 }

      at DB._authOrThrow (src/mongo/shell/db.js:1271:32) at (auth):6:8 at (auth):7:2 at src/mongo/shell/db.js:1271 exception: login failed

      The mongod shows this error

      2016-02-13T15:58:18.471-0500 I NETWORK [initandlisten] connection accepted from 127.0.0.1:53183 #1 (1 connection now open)

      2016-02-13T15:58:18.490-0500 F - [conn1] Invalid access at address: 0

      2016-02-13T15:58:18.524-0500 F - [conn1] Got signal: 11 (Segmentation fault).

      which shows that mongod stopped.

      What did I do wrong?

            Assignee:
            Unassigned Unassigned
            Reporter:
            mongo_2 Muhammad Usman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: