juju debug-log prints some log messages, but quickly stops streaming

[Matt Rae]

using juju 2.0-beta7, and running 'juju debug-log' I will see the most recent log messages printed, but no additional streaming updates. pressing ctrl-c then running juju debug-log again prints new messages, but again no additional log messages are printed after debug-log hangs.

ubuntu@maas-region-controller:~/charms$ juju debug-log
unit-ceph-osd-3: 2016-05-24 13:34:04 DEBUG worker.uniter.jujuc server.go:174 hook context id "ceph-osd/3-update-status-4878277179938632726"; dir "/var/lib/juju/agents/unit-ceph-osd-3/charm"
unit-ceph-osd-3: 2016-05-24 13:34:04 INFO worker.uniter.jujuc server.go:173 running hook tool "relation-get" ["--format=json" "-r" "mon:40" "-" "ceph/0"]
unit-ceph-osd-3: 2016-05-24 13:34:04 DEBUG worker.uniter.jujuc server.go:174 hook context id "ceph-osd/3-update-status-4878277179938632726"; dir "/var/lib/juju/agents/unit-ceph-osd-3/charm"
...
unit-ceph-osd-1: 2016-05-24 13:36:01 DEBUG juju.worker.dependency engine.go:479 "uniter" manifold worker stopped: failed to initialize uniter for "unit-ceph-osd-1": remove /var/lib/juju/locks/uniter-hook-execution/alive.17492: read-only file system
unit-ceph-osd-1: 2016-05-24 13:36:01 ERROR juju.worker.dependency engine.go:526 "uniter" manifold worker returned unexpected error: failed to initialize uniter for "unit-ceph-osd-1": remove /var/lib/juju/locks/uniter-hook-execution/alive.17492: read-only file system

[not updated over the course of a few minutes, although many hooks are running]

^C
ubuntu@maas-region-controller:~/charms$

[Cheryl Jennings (cherylj)]

Can you attach machine-0.log from the controller and output of juju debug-log --debug (there may be something interesting in the --debug output that gets logged)?

I wasn't able to recreate in a simple case.

[Launchpad Janitor (janitor)]

[Expired for juju-core because there has been no activity for 60 days.]

[Menno Finlay-Smits (menno.smits)]

This is likely to have been due to the same root cause as bug 1590605