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

mongod locks up on OSX after less than two days of uptime

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.0.3
    • Component/s: None
    • Labels:
      None
    • Environment:
      sys info: Darwin erh2.10gen.cc 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 BOOST_LIB_VERSION=1_40
      OSX 10.6.8
      2 x 2.66 GHz Dual-Core Intel Xeon
      11 GB RAM
    • OS X

      I installed mongodb 2.0.3 for OSX on Monday on my workstation for development use. It's been working fine until just a few minutes ago, when it refused new DB connections. I was running mongod in a separate terminal in non-daemon mode; the process wouldn't respond to Ctrl-C. Ultimately I had to kill -9 the process.

      Console output before killing the process:

      Wed Mar  7 12:17:23 [conn72] CMD: drop pac.tmp.mr.plugins_1790_inc
      Wed Mar  7 12:17:23 [conn72] command pac.$cmd command: { mapreduce: "plugins", map: "
          function () {
            var pluginId = this._id;
            this.reviews.forEach(function(review) {
              emit(review._id, {pluginId: pluginId, review: ...", reduce: "
          function (key, values) {
            if (values.length > 0) return values[0];
          }", verbose: false, out: "reviews" } ntoreturn:1 reslen:131 275ms
      got pipe signal:13
      Wed Mar  7 12:19:37 [initandlisten] select() signal caught, continuing
      got pipe signal:13
      Wed Mar  7 12:19:37 [initandlisten] select() signal caught, continuing
      got pipe signal:13
      got pipe signal:13
      got pipe signal:13
      Wed Mar  7 12:19:37 [initandlisten] select() signal caught, continuing
      

            Assignee:
            benjamin.becker Ben Becker
            Reporter:
            arun Arun Bhalla
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: