I'm also affected by this issue I think. I don't know for now whether it
has something to do with systemd or startup, but if the munin-node
service gets started with start munin-node, it can't be stopped with
/etc/init.d/munin-node stop although it went [OK]. Also /etc/init.d
/munin-node restart
I'm also affected by this issue I think. I don't know for now whether it
has something to do with systemd or startup, but if the munin-node
service gets started with start munin-node, it can't be stopped with
/etc/init.d/munin-node stop although it went [OK]. Also /etc/init.d
/munin-node restart
** Description changed:
[IMPACT]
* puppet setup with storeconfig activated
* On client run, master fail with stack level too deep error, and client do
no apply any of its manifests
* not all clients are affected, but if one client is failing it will fail
forever
* This issue is
** Description changed:
[IMPACT]
* puppet setup with storeconfig activated
* On client run, master fail with stack level too deep error, and client do
no apply any of its manifests
* not all clients are affected, but if one client is failing it will fail
forever
* This issue is
