juju-db segfault while syncing with replicas
Bug #1500981 reported by
JuanJo Ciarlante
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
High
|
Unassigned | ||
juju-mongodb (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Context:
* juju-core: 1.22.6.1 (agent)
* juju-mongodb: 2.4.9-0ubuntu3 (dpkg)
* linux: 3.16.0-50-generic (LTS HWE trusty)
This is one of the 3 mongod replicas as deployed with 'ensure-
'start juju-db' crashes with mongod segfault, running it manually shows:
http://
tags: | added: mongodb |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.26-alpha1 |
Changed in juju-core: | |
milestone: | 1.26-alpha1 → 1.26-alpha2 |
Changed in juju-core: | |
milestone: | 1.26-alpha2 → 1.26-beta1 |
Changed in juju-core: | |
milestone: | 1.26-beta1 → 2.0-alpha2 |
Changed in juju-core: | |
milestone: | 2.0-alpha2 → 2.0-alpha3 |
Changed in juju-core: | |
milestone: | 2.0-alpha3 → 2.0-beta4 |
Changed in juju-core: | |
status: | Triaged → Invalid |
To post a comment you must log in.
FYI this happens in machine#1, machine#0,#2 showing mongod's ok.