You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2019. It is now read-only.
The service restarts are unreliable on amazon (and possibly others)
[...]
RUNNING HANDLER [goetzk.shinken : restart shinken arbiter] *********************
fatal: [13.55.21.151]: FAILED! => {"changed": false, "failed": true, "msg": "/etc/rc.d/init.d/shinken: line 67: cd: /etc/rc.d/init.d/../../var: No such file or directory\n/etc/rc.d/init.d/shinken: line 68: cd: /etc/rc.d/init.d/../../etc: No such file or directory\n/etc/rc.d/init.d/shinken: line 67: cd: /etc/rc.d/init.d/../../var: No such file or directory\n/etc/rc.d/init.d/shinken: line 68: cd: /etc/rc.d/init.d/../../etc: No such file or directory\n"}
[...]
PLAY RECAP *********************************************************************
123.123.321.321 : ok=3 changed=1 unreachable=0 failed=1
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 ]
The service restarts are unreliable on amazon (and possibly others)
This is using ansible so may be an upstream bug.
The text was updated successfully, but these errors were encountered: