From 8af039fec444a647f87daf3350bd5e385446fe09 Mon Sep 17 00:00:00 2001 From: Alexei Sheplyakov Date: Wed, 20 May 2015 12:05:10 +0300 Subject: [PATCH] IBP: configure mcollectived so it daemonizes itself The server.cfg shipped with mcollective package tells mcollectived to daemonize itself, and the config generated by cloud init tells it to run in the background (assuming that the init script is responsible for daemonization). This mismatch breaks PID file: start-stop-daemon forks, detaches, records its pid, and runs mcollectived which daemonizes again. As a result the PID recored in the PID file is wrong so subsequent start/restart/stop action can't find the previously launched process and starts an extra instance of mcollective. In order to solve the problem 1) fix the init script (assuming that mcollectived daemonizes itself) 2) generate a proper server.cfg (with daemonize=1 statement) Related-Bug: #1454741 Merge-After: https://review.fuel-infra.org/6760 Change-Id: I1b9ddc2d8ec790b5a6cb1095e32559cf506c48e7 --- cloud-init-templates/cloud_config_ubuntu.jinja2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloud-init-templates/cloud_config_ubuntu.jinja2 b/cloud-init-templates/cloud_config_ubuntu.jinja2 index a791134..55ad8e2 100644 --- a/cloud-init-templates/cloud_config_ubuntu.jinja2 +++ b/cloud-init-templates/cloud_config_ubuntu.jinja2 @@ -47,7 +47,7 @@ mcollective: libdir: /usr/share/mcollective/plugins logfile: /var/log/mcollective.log loglevel: debug - daemonize: 0 + daemonize: 1 direct_addressing: 1 ttl: 4294957 securityprovider: psk