Hi Raphael, This is due to a misconfiguration in mcollective's server.cfg
The way upstart behaves with scripts that fork themselves (as is the case with mcollective) makes it very difficult for upstart to track the process once it has been forked. This is why the default configuration in mcollective server.cfg on the package specifies daemonize=0 so upstart can track the process properly. This behaviour shown on the bug means that the user has set daemonize=1 on server.cfg, which is not supported by the upstart script. Marking as invalid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965188 Title: Mcollective is launched more than once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mcollective/+bug/965188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
