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

init: mongodb main process terminated with status 100 when space is running low

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.4
    • Component/s: Stability
    • Labels:
      None
    • Environment:
      Ubuntu 11.10, 10 gen ubuntu packages using upstart, Virtual Machine using Virtual Box on Mac
    • Linux

      I was running an update command on a capped collection and the server suddenly started showing the following message:

      Thu May 10 12:47:07 DBClientCursor::init call() failed
      Thu May 10 12:47:07 query failed : ***** to: localhost
      Error: error doing query: failed
      Thu May 10 12:47:07 trying reconnect to localhost
      Thu May 10 12:47:07 reconnect localhost ok
      Thu May 10 12:47:07 DBClientCursor::init call() failed

      I couldn't find anything in the logs but I happened to check dmesg and it had the entry

      [ 49.842846] init: mongodb main process (1074) terminated with status 100

      And when I tried to start mongo again I got another entry in dmesg

      [ 225.928777] init: mongodb main process (1092) terminated with status 100

      The only thing that I can think of being the problem is that the VM I'm using is almost out of space

      => / is using 96.3% of 1.70GB

      I would imagine that if this is an issue with space then there should be something in the logs or something to point me in the right direction.

            Assignee:
            adamc Adam Comerford
            Reporter:
            real_ate Chris Manson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: