Open dgilm opened 10 years ago
I think you should define it in a command config file
yes, it's in the default configuraiton since the 2.0, but we do not add it to updated 1.4 one as an update never change the user configuration :)
On Fri, Sep 19, 2014 at 2:04 PM, Sébastien Coavoux <notifications@github.com
wrote:
I think you should define it in a command config file
— Reply to this email directly or view it on GitHub https://github.com/shinken-monitoring/mod-ws-arbiter/issues/8#issuecomment-56168557 .
You are right @Seb-Solon,
So, there's a misspelling in the commands/restart-shinken.cfg (or in external_command.py of the core repo)?
--- commands/restart-shinken.cfg.orig 2014-09-19 14:18:49.946241592 +0200
+++ commands/restart-shinken.cfg 2014-09-19 14:18:58.534241433 +0200
@@ -1,5 +1,5 @@
define command {
- command_name restart-shinken
- command_line sudo /etc/init.d/shinken restart
+ command_name restart_shinken
+ command_line /etc/init.d/shinken restart
}
/reload seems not to be managed by external_command.py.
We can ask @mohierf . He did the PR to add reload / restart feature :)
Did this ever get resolved, seeing the same issue :)
N/M, I see that the fix requires Shinken 2.2-RC1 :)
I am not able to execute external commands with the ws-arbiter module.
I want to restart the arbiter with the following request:
I get:
With a reload command:
I get pretty the same result:
Is there any config I am missing? Is this related to #1?
The versions that I am using: Shinken 2.0.3 and ws-arbiter module from master branch