Comment 17 for bug 922754

This problem is caused when upstart attempts to exec directly a command that does not exist

I've created an updated package (upstart version '1.4-0ubuntu5~jh ') in my 'ppa:jamesodhunt/upstart-job-logging' PPA [1] that fixes this issue.

Please could those affected by this problem try it out and provide feedback.

[1] - https://launchpad.net/~jamesodhunt/+archive/upstart-job-logging