juju-core

unit agent fails to start after restart - run.socket: connection refused

Bug #1286213 reported by Michael Nelson
20
This bug affects 6 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Dimiter Naydenov
juju-core 1.17.5

Bug Description

Steps to repro:
1) juju bootstrap
2) juju deploy --repository=../.. local:whatever
3) Confirm that `juju run --service whatever "echo 'Hello world'"` works
4) sudo lxc-stop --reboot --name=my-local-machine-1
5) Retry `juju run --service whatever "echo 'Hello world'"`

Result:
error: dial unix /var/lib/juju/agents/unit-whatever-0/run.socket: connection refused

Everything else seems to work fine (debug-hooks, ssh etc.), eg:
$ juju ssh whatever/0 "echo 'Hello world'"
Hello world

Note, you don't have to reboot the machine to trigger this. Just doing "restart jujud-unit-whatever-0" will fail to actually get the unit back up and running because it sees a stale socket left on disk.

See original description

Related branches

lp:~dimitern/juju-core/320-lp-1286213-juju-run-socket-remove
Juju Engineering: Pending requested
Diff: 124 lines (+23/-19)
5 files modified
cmd/jujud/run.go (+1/-1)
cmd/jujud/run_test.go (+1/-1)
worker/uniter/runlistener.go (+12/-7)
worker/uniter/runlistener_test.go (+6/-6)
worker/uniter/uniter.go (+3/-4)
Revision history for this message
Curtis Hovey (sinzui) wrote :

Is the lxc series different from the host series? This issue may be a dupe of bug 1285901, which has a fix landing at this moment.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.17.5
tags: added: local-provider lxc run
Revision history for this message
Michael Nelson (michael.nelson) wrote : Re: [Bug 1286213] Re: juju run not available after reboot - run.socket: connection refused

On Fri, Feb 28, 2014 at 5:32 PM, Curtis Hovey <email address hidden> wrote:
> Is the lxc series different from the host series? This issue may be a
> dupe of bug 1285901, which has a fix landing at this moment.

Yes - host (and bootstrap) is trusty, deploying to precise lxc. I'll
try again when the fix for the above lands and see.

Thanks.

Revision history for this message
John A Meinel (jameinel) wrote : Re: juju run not available after reboot - run.socket: connection refused

This is actually critical because of the part reported by Andreas. After reboot you can't "juju run" because the Unit agent *fails to start* because the socket is left on disk.

Changed in juju-core:
importance: High → Critical
tags: added: regression
summary: - juju run not available after reboot - run.socket: connection refused
+ unit agent fails to start after restart - run.socket: connection refused
description: updated
Andreas Hasenack (ahasenack)
tags: added: landscape
Dimiter Naydenov (dimitern)
Changed in juju-core:
assignee: nobody → Dimiter Naydenov (dimitern)
status: Triaged → In Progress
Dimiter Naydenov (dimitern)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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