juju-core

juju-db segfault while syncing with replicas

Bug #1500981 reported by JuanJo Ciarlante
10
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-availability',
'start juju-db' crashes with mongod segfault, running it manually shows:
http://paste.ubuntu.com/12614724/

Revision history for this message
JuanJo Ciarlante (jjo) wrote :

FYI this happens in machine#1, machine#0,#2 showing mongod's ok.

Revision history for this message
JuanJo Ciarlante (jjo) wrote :

FYI this started happening since its (mongod) inception:
grep mongo /var/log/syslog |tail -40 -> http://paste.ubuntu.com/12614948/

Revision history for this message
Martin Packman (gz) wrote :

This package hasn't changed in trusty in more than a year.

<http://changelogs.ubuntu.com/changelogs/pool/universe/j/juju-mongodb/juju-mongodb_2.4.9-0ubuntu3/changelog

Do you have any ideas on what's different with the environment you're hitting these segfaults from everywhere else?

Changed in juju-core:
status: New → Incomplete
Revision history for this message
JuanJo Ciarlante (jjo) wrote :

@gz: I got this at our staging environment, where we re-deploy
HA'd juju + openstacks several times a week (or day), 1st time
I positively observe this behavior, so I'd guess it's unfortunately
a subtle race condition or alike.

I did save /var/lib/juju/db/, /var/log/syslog and /var/log/juju/machine-?.log
from the 3 state servers, can provide them.

Changed in juju-core:
status: Incomplete → New
Curtis Hovey (sinzui)
tags: added: mongodb
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.26-alpha1
Revision history for this message
Robie Basak (racb) wrote :

Thank you for the report JuanJo.

I think action needs to be taken here in Juju first to isolate a failure case for the juju-mongodb package in Ubuntu. Until then, we can't work on it from a juju-mongodb perspective, so marking Incomplete.

Changed in juju-mongodb (Ubuntu):
status: New → Incomplete
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.26-alpha1 → 1.26-alpha2
Cheryl Jennings (cherylj)
Changed in juju-core:
milestone: 1.26-alpha2 → 1.26-beta1
Cheryl Jennings (cherylj)
Changed in juju-core:
milestone: 1.26-beta1 → 2.0-alpha2
Cheryl Jennings (cherylj)
Changed in juju-core:
milestone: 2.0-alpha2 → 2.0-alpha3
Cheryl Jennings (cherylj)
Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta4
Revision history for this message
Cheryl Jennings (cherylj) wrote :

@jjo - are you still seeing this issue?

Changed in juju-core:
milestone: 2.0-beta4 → none
Anastasia (anastasia-macmood)
Changed in juju-core:
status: Triaged → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju-mongodb (Ubuntu) because there has been no activity for 60 days.]

Changed in juju-mongodb (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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