mongodb fails to start with local provider

Bug #1302747 reported by Alex Lomov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Invalid
High
Unassigned

Bug Description

It appears that mongodb crashes on the start up
Here is output from /var/log/upstart/juju-db-vagrant-local.log:

warning: bind_ip of 0.0.0.0 is unnecessary; listens on all ips by default
note: noprealloc may hurt performance in many applications
using syslog ident: mongod.37017
0x95c496 0x9206fc 0x92079c 0x6d3e97 0x7459c4 0x57f1fe 0x580a9f 0x560845 0x7f13ea267ec5 0x5778fc
 /usr/lib/juju/bin/mongod(_ZN5mongo15printStackTraceERSo+0x26) [0x95c496]
 /usr/lib/juju/bin/mongod(_ZN5mongo11msgassertedEiPKc+0x9c) [0x9206fc]
 /usr/lib/juju/bin/mongod() [0x92079c]
 /usr/lib/juju/bin/mongod(_ZN5mongo16flushMyDirectoryERKN5boost10filesystem4pathE+0x217) [0x6d3e97]
 /usr/lib/juju/bin/mongod(_ZN5mongo15acquirePathLockEb+0x1e4) [0x7459c4]
 /usr/lib/juju/bin/mongod(_ZN5mongo14_initAndListenEi+0x81e) [0x57f1fe]
 /usr/lib/juju/bin/mongod(_ZN5mongo13initAndListenEi+0xf) [0x580a9f]
 /usr/lib/juju/bin/mongod(main+0x2d5) [0x560845]
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f13ea267ec5]
 /usr/lib/juju/bin/mongod() [0x5778fc]

Juju version is 1.17.7-trusty-amd64,
Ubuntu version is trusty 14.04.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Does the system have the juju-local package installed. More specific, does the system have juju-mongodb installed at
    /usr/lib/juju/bin/mongod

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.19.0
status: Triaged → Incomplete
Revision history for this message
Tim Penhey (thumper) wrote :

Curtis, you can see from the log file that it is using /usr/lib/juju/bin/mongod.

The more interesting part is that this looks like a vagrant trusty image.

Curtis Hovey (sinzui)
tags: added: vagrant
Changed in juju-core:
milestone: 1.19.0 → 1.19.1
Curtis Hovey (sinzui)
Changed in juju-core:
status: Incomplete → Invalid
milestone: 1.19.1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.