-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use reboot command to all nodes from wibed server #4
Comments
sorry, this is an issue of wibed server that I don't remember where it is. |
can you workaround this with echo c >/proc/sysrq-trigger |
Great! I cannot test now (no wibed system near me), but seems that would be better if: So, should be: echo sub > /proc/sysrq-trigger yes, should be https://twitter.com/qolund/status/600250659603148800 documentation source: https://www.kernel.org/doc/Documentation/sysrq.txt |
Hi, sorry for the delay but I am on vacation and have no laptop. The reboot command causes an exception to the node-controller communication system. Though I cannot test it now, I think reboot could work with a command that would execute in the background: a delay of 20 seconds and then reboot. I will reopen the issue. And when I am back from vacation i will try to solve it in a more generic way. |
[Perhaps is a known issue, but let's have it noted.]
Reboot command cannot be executed because needs confirmation that does not arrive.
The text was updated successfully, but these errors were encountered: