juju-core

Undead service

Bug #1191908 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
New
Undecided
Unassigned

Bug Description

I managed to get a service that will not die. I think this was a result of something like 'juju deploy local:postgresql; juju destroy-service local:postgresql' but can't be sure (I killed my test suite at the wrong moment).

machines:
  "0":
    agent-state: started
    agent-version: 1.11.0
    dns-name: 10.55.63.175
    instance-id: e60754bd-a989-4141-b626-f4522e450471
    series: precise
services:
  postgresql:
    charm: local:precise/postgresql-78
    exposed: false
    life: dying
    units:
      postgresql/0:
        agent-state: pending

Revision history for this message
Stuart Bishop (stub) wrote :
Download full text (31.6 KiB)

machine-0.log:

2013/06/17 18:42:12 INFO worker/provisioner: found machine "18" pending provisioning
2013/06/17 18:42:12 DEBUG worker/firewaller: started watching unit postgresql/0
2013/06/17 18:42:12 DEBUG worker/firewaller: started watching machine 18
2013/06/17 18:42:12 INFO environs: reading tools with major version 1
2013/06/17 18:42:12 DEBUG environs/tools: reading v1.* tools
2013/06/17 18:42:12 INFO environs: falling back to public bucket
2013/06/17 18:42:12 DEBUG environs/tools: reading v1.* tools
2013/06/17 18:42:12 DEBUG environs/tools: found 1.10.0-precise-amd64
[...]
2013/06/17 18:42:12 DEBUG environs/tools: found 1.9.14-raring-amd64
2013/06/17 18:42:12 INFO environs: filtering tools by version: 1.11.0
2013/06/17 18:42:12 INFO environs: filtering tools by series: precise
2013/06/17 18:42:16 DEBUG environs/openstack: openstack user data; 2780 bytes
2013/06/17 18:42:21 INFO environs/openstack: started instance "5f3fce1f-31db-4439-8a87-e471eec96fbb"
2013/06/17 18:42:21 NOTICE worker/provisioner: started machine 18 as instance 5f3fce1f-31db-4439-8a87-e471eec96fbb
2013/06/17 18:43:52 DEBUG worker/firewaller: stopped watching unit postgresql/0
2013/06/17 18:44:27 INFO worker/provisioner: removing dead machine "18"
2013/06/17 18:44:27 DEBUG worker/firewaller: stopped watching machine 18
2013/06/17 18:44:27 DEBUG environs/openstack: terminating instances [5f3fce1f-31db-4439-8a87-e471eec96fbb 5f3fce1f-31db-4439-8a87-e471eec96fbb]

all-machines.log:

juju-lcy2-machine-0:2013/06/17 18:42:12 INFO worker/provisioner: found machine "18" pending provisioning
juju-lcy2-machine-0:2013/06/17 18:42:12 DEBUG worker/firewaller: started watching unit postgresql/0
juju-lcy2-machine-0:2013/06/17 18:42:12 DEBUG worker/firewaller: started watching machine 18
juju-lcy2-machine-0:2013/06/17 18:42:12 INFO environs: reading tools with major version 1
juju-lcy2-machine-0:2013/06/17 18:42:12 DEBUG environs/tools: reading v1.* tools
juju-lcy2-machine-0:2013/06/17 18:42:12 INFO environs: falling back to public bucket
juju-lcy2-machine-0:2013/06/17 18:42:12 DEBUG environs/tools: reading v1.* tools
juju-lcy2-machine-0:2013/06/17 18:42:12 DEBUG environs/tools: found 1.10.0-precise-amd64
[...]
juju-lcy2-machine-0:2013/06/17 18:42:12 DEBUG environs/tools: found 1.9.14-raring-amd64
juju-lcy2-machine-0:2013/06/17 18:42:12 INFO environs: filtering tools by version: 1.11.0
juju-lcy2-machine-0:2013/06/17 18:42:12 INFO environs: filtering tools by series: precise
juju-lcy2-machine-0:2013/06/17 18:42:16 DEBUG environs/openstack: openstack user data; 2780 bytes
juju-lcy2-machine-0:2013/06/17 18:42:21 INFO environs/openstack: started instance "5f3fce1f-31db-4439-8a87-e471eec96fbb"
juju-lcy2-machine-0:2013/06/17 18:42:21 NOTICE worker/provisioner: started machine 18 as instance 5f3fce1f-31db-4439-8a87-e471eec96fbb
juju-lcy2-machine-18:2013/06/17 18:43:24 NOTICE agent starting
juju-lcy2-machine-18:2013/06/17 18:43:24 INFO state: opening state; mongo addresses: ["10.55.63.175:37017"]; entity "machine-18"
juju-lcy2-machine-18:2013/06/17 18:43:24 NOTICE agent starting
juju-lcy2-machine-18:2013/06/17 18:43:24 INFO state: connection established
juju-lcy2-machine-18:2013/06/17 18:43:2...

Revision history for this message
Stuart Bishop (stub) wrote :

Running 'juju remove-unit postgresql/0' cleared the perverse state.

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.