I am now able to reproduce this issue.
The simplest way to work around this issue until we release an update is to boot with '--no-log' to stop Upstart logging any job output.
I am now able to reproduce this issue.
The simplest way to work around this issue until we release an update is to boot with '--no-log' to stop Upstart logging any job output.