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

Mongodb SEGFAULTS with a null pointer

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker - P1
    • Resolution: Duplicate
    • Affects Version/s: 2.2.3
    • Fix Version/s: None
    • Component/s: Concurrency, Stability
    • Labels:
    • Environment:
      Centos 6.2, pymongo-2.1.1-1, pulp-2.1.3-1
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      Linux
    • Steps To Reproduce:
      Hide
      1. service mongod status
        mongod dead but pid file exists
      2. service mongod restart
        Stopping mongod: [FAILED]
        Starting mongod: [ OK ]
      3. service mongod status
        mongod (pid 30930) is running...
      4. pulp-manage-db
        Beginning database migrations.
        Migration package pulp.server.db.migrations is up to date at version 4
        Migration package pulp_rpm.migrations is up to date at version 7
        Database migrations complete.
        Loading content types.
        Content types loaded.
      5. service httpd restart
        Stopping httpd: [ OK ]
        Starting httpd: [ OK ]
      6. service mongod status
        mongod dead but pid file exists

      -------------------------------------
      Method 2)

      1. mongo pulp_database < echo "db.queued_calls.drop();"
        MongoDB shell version: 2.2.3
        connecting to: pulp_database
        false
        Wed Jul 24 10:25:24 mongo got signal 11 (Segmentation fault), stack trace:

      Wed Jul 24 10:25:24 0x59e416 0x47adbd 0x3a41032900
      mongo(_ZN5mongo15printStackTraceERSo+0x26) [0x59e416]
      mongo(_Z12quitAbruptlyi+0x31d) [0x47adbd]
      /lib64/libc.so.6() [0x3a41032900]

      Show
      service mongod status mongod dead but pid file exists service mongod restart Stopping mongod: [FAILED] Starting mongod: [ OK ] service mongod status mongod (pid 30930) is running... pulp-manage-db Beginning database migrations. Migration package pulp.server.db.migrations is up to date at version 4 Migration package pulp_rpm.migrations is up to date at version 7 Database migrations complete. Loading content types. Content types loaded. service httpd restart Stopping httpd: [ OK ] Starting httpd: [ OK ] service mongod status mongod dead but pid file exists ------------------------------------- Method 2) mongo pulp_database < echo "db.queued_calls.drop();" MongoDB shell version: 2.2.3 connecting to: pulp_database false Wed Jul 24 10:25:24 mongo got signal 11 (Segmentation fault), stack trace: Wed Jul 24 10:25:24 0x59e416 0x47adbd 0x3a41032900 mongo(_ZN5mongo15printStackTraceERSo+0x26) [0x59e416] mongo(_Z12quitAbruptlyi+0x31d) [0x47adbd] /lib64/libc.so.6() [0x3a41032900]

      Description

      I am trying to use pulp, which a program that manages package repositories, and uses mongodb as a backend. However, it has been causing mongodb to segfault. https://bugzilla.redhat.com/show_bug.cgi?id=986070 http://pastebin.com/VgfHZj0q (the file being piped in just contains "db.queued_calls.drop();" ). The second link in particular seems to point the finger at mongo.

      Pulp has a db purging call queued, and on its startup it segfaults mongodb, which itself complains about a null pointer, and what appears to a threading problem (as soon as anything thread but the first does anything it gets said null pointer)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michael.grundy Michael Grundy
              Reporter:
              jgreenleaf Jim
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: