On Wednesday 03 October 2012 02:47:05 you wrote: > Update for the record. As we have since found out, it's much worse than > just needing an "expect fork." Somewhere along the line, before it gets > around to running the start-cluster-controller code proper, maas- > provision does a whole bunch of other forks. The question is whether we > can make upstart track the right child process.
The answer to fix this is to make a completely new wrapper script outside of maas-provision, I think. There's some weirdness going on in it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059453 Title: The celery cluster worker is not properly stopped To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1059453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs