Open goetzk opened 7 years ago
Looks like this is specific to calling -arbiter, rather than restarting shinken itself. The bug is therefor going to be in the init script/s
sudo /etc/init.d/shinken restart
Restarting scheduler
Restarting poller [ OK ]
Restarting reactionner [ OK ]
Restarting broker [ OK ]
Restarting receiver [ OK ]
Restarting arbiter [ OK ]
Doing config check
sudo /etc/init.d/shinken-arbiter restart
/etc/rc.d/init.d/shinken: line 67: cd: /etc/rc.d/init.d/../../var: No such file or directory
/etc/rc.d/init.d/shinken: line 68: cd: /etc/rc.d/init.d/../../etc: No such file or directory
Restarting arbiter
Doing config check
[ OK ]
also happens for broker.
sudo /etc/init.d/shinken-broker restart
/etc/rc.d/init.d/shinken: line 67: cd: /etc/rc.d/init.d/../../var: No such file or directory
/etc/rc.d/init.d/shinken: line 68: cd: /etc/rc.d/init.d/../../etc: No such file or directory
Restarting broker
[ OK ]
I've just opened https://github.com/naparuba/shinken/issues/1901 upstream about this.
The service restarts are unreliable on amazon (and possibly others)
This is using ansible so may be an upstream bug.