V8 crashes if mongod run as service on Azure

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.2
    • Component/s: MapReduce
    • None
    • Environment:
      CentOS 7, Azure VM
    • Linux
    • Hide

      Following query crushes server:

      db['2015-04-13'].group({
    key:{id:1},
    cond:{created_at:{$gte: new Date('2015-04-13')}},
    reduce:function (curr, resul) {},
    initial: {}
})
      Show
      Following query crushes server: db[ '2015-04-13' ].group({ key:{id:1}, cond:{created_at:{$gte: new Date( '2015-04-13' )}}, reduce:function (curr, resul) {}, initial: {} })
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Query provided in "Steps to reproduce" crushes server.
      There is output of server log with verbosity at level 5 is attached as file (starting only from a command execution).

      Problem occur only if Mongod starts as service (service mongod start), if mongod started in following way:
      sudo su -s /bin/bash mongod
      mongod -f /etc/mongod.conf
      Then query successfully runs; however service mongod status returns "inactive (dead)".

      ulimits set according to documentation, mongod is an owner of Data folder, and mongod never runs on same data path as different users.

      Another problem with running as service did come up during deployment, and may have something in common with described issue: if run as service, mongod is unable to create lock file and database in any other folder then default /var/lib/ even if mongod is assign owner recursively of new db path .

        1. Backtrace.txt
          6 kB

            Assignee:
            Ramon Fernandez
            Reporter:
            Victor Pozdniakov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: