blocks|key|3509|text|您可能没有做任何真正错误的事情，只是/sbin/reboot关闭服务器的速度太快了，以至于服务器在Ansible自己可以关闭它之前就断开了Ansible使用的SSH连接。因此，Ansible报告了一个错误，因为它发现SSH连接由于意外原因而失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3510|为了解决这个问题，您可能需要从使用/sbin/reboot切换到使用/sbin/shutdown。shutdown命令让您通过一段时间，当与-r交换机结合使用时，它将执行重新启动，而不是实际关闭。因此，您可能希望尝试这样的任务：|offset|length|style|CODE|3511|-+name:+Restart+server
++command:+/sbin/shutdown+-r+%2B1
++async:+0
++poll:+0
++ignore_errors:+true|code-block|syntax|javascript|3512|这将使服务器重新启动延迟1分钟，但这样做应该会让Ansible有足够的时间关闭SSH连接本身，从而避免您当前收到的错误。|3513|entityMap^0|0|H|C|Y|E|1Y|2|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

You're likely not doing anything truly wrong, it's just that /sbin/reboot is shutting down the server so quickly that the server is tearing down the SSH connection used by Ansible before Ansible itself can close it. As a result Ansible is reporting an error because it sees the SSH connection failing for an unexpected reason.

What you might want to do to get around this is to switch from using <code>/sbin/reboot</code> to using <code>/sbin/shutdown</code> instead. The shutdown command lets you pass a time, and when combined with the <code>-r</code> switch it will perform a reboot rather than actually shutting down. So you might want to try a task like this:

<pre><code>- name: Restart server
 command: /sbin/shutdown -r +1
 async: 0
 poll: 0
 ignore_errors: true
</code></pre>

This will delay the server reboot for 1 minute, but in doing so it should give Ansible enough time to to close the SSH connection itself, thereby avoiding the error that you're currently getting.

blocks|key|3551|text|在重启任务之后，您应该有一个等待远程主机完成重启的local_action任务，否则，ssh连接将终止，剧本也将终止。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3552|-+name:+Reboot+server
++command:+/sbin/reboot

-+name:+Wait+for+the+server+to+finish+rebooting
++sudo:+no
++local_action:+wait_for+host="{{+inventory_hostname+}}"+search_regex=OpenSSH+port=22+timeout=300|code-block|syntax|javascript|3553|我还写了一篇关于实现类似解决方案的博客文章：https://oguya.github.io/linux/2015/02/22/ansible-reboot-servers/|3554|entityMap|0|LINK|mutability|MUTABLE|url|https://oguya.github.io/linux/2015/02/22/ansible-reboot-servers/^0|P|C|0|0|M|1S|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

After the reboot task, you should have a <code>local_action</code> task that waits for the remote host to finish rebooting, otherwise, the ssh connection will be terminated and so is the playbook.

<pre><code>
- name: Reboot server
 command: /sbin/reboot

- name: Wait for the server to finish rebooting
 sudo: no
 local_action: wait_for host="{{ inventory_hostname }}" search_regex=OpenSSH port=22 timeout=300
</code></pre>

I also wrote a blog post about achieving a similar solution: <a href="https://oguya.github.io/linux/2015/02/22/ansible-reboot-servers/" rel="noreferrer">https://oguya.github.io/linux/2015/02/22/ansible-reboot-servers/</a>

blocks|key|4511115|text|在重新启动时，所有ssh连接都将关闭。这就是Ansible任务失败的原因。从Ansible+1.9.x开始，ignore_errors:+true或failed_when:+false添加不再有效，因为对ssh连接的处理已经改变，并且关闭的连接现在是一个致命错误，在播放过程中无法捕获。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4511116|我想出的唯一方法是运行一个本地shell任务，然后启动一个单独的ssh连接，然后这个连接可能会失败。|4511117|-+name:+Rebooting
++delegate_to:+localhost
++shell:+ssh+-S+"none"+{{+inventory_hostname+}}+sudo+/usr/sbin/reboot"
++failed_when:+false
++changed_when:+true|code-block|syntax|javascript|4511118|entityMap^0|1I|J|22|I|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

At reboot time all ssh connections are closed. That's why the Ansible task fails. The <code>ignore_errors: true</code> or <code>failed_when: false</code> additions are no longer working as of Ansible 1.9.x because handling of ssh connections has changed and a closed connection now is a fatal error which can not be caught during play.

The only way I figured out how to do it is to run a local shell task which then starts a separate ssh connection, which then may fail.

<pre><code>- name: Rebooting
 delegate_to: localhost
 shell: ssh -S "none" {{ inventory_hostname }} sudo /usr/sbin/reboot"
 failed_when: false
 changed_when: true
</code></pre>

blocks|key|4511135|text|另一种解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4511136|-+name:+reboot+host
++command:+/usr/bin/systemd-run+--on-active=10+/usr/bin/systemctl+reboot
++async:+0
++poll:+0

-+name:+wait+for+host+sshd
++local_action:+wait_for+host="{{+inventory_hostname+}}"+search_regex=OpenSSH+port=22+timeout=300+delay=30|code-block|syntax|javascript|4511137|systemd-run创建“即时”的新服务，它将在10秒的延迟(--on-active=10)后启动systemctl+reboot。在wait_for中添加delay=30以添加额外的20秒，以确保主机确实开始重新启动。|offset|length|style|CODE|4511138|entityMap^0|0|0|0|B|W|E|1E|G|1W|8|27|8|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$]]

Another solution:

<pre><code>- name: reboot host
 command: /usr/bin/systemd-run --on-active=10 /usr/bin/systemctl reboot
 async: 0
 poll: 0

- name: wait for host sshd
 local_action: wait_for host="{{ inventory_hostname }}" search_regex=OpenSSH port=22 timeout=300 delay=30
</code></pre>

<code>systemd-run</code> creates "on the fly" new service which will start <code>systemctl reboot</code> after 10 sec of delay (<code>--on-active=10</code>).
<code>delay=30</code> in <code>wait_for</code> to add extra 20 sec to be sure that host actually started rebooting.

blocks|key|3667|text|上面的解决方案对我来说都不可靠。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3668|发布/sbin/reboot会导致play崩溃(在ansible完成任务之前，SSH连接就会关闭，即使使用ignore_errors:+true也会崩溃)，并且/usr/bin/systemd-run+--on-active=2+/usr/bin/systemctl+reboot不会在2秒后重启，而是在20秒到1分钟之间的随机时间段后重启，所以延迟有时是不够的，这是不可预测的。|offset|length|style|CODE|3669|此外，我不想等待几分钟，而云服务器可以在几秒钟内重启。|3670|所以这是我的解决方案：|3671|-+name:+Reboot+the+server+for+kernel+update
++shell:+(+sleep+3+&&+/sbin/reboot+&+)
++async:+0
++poll:+0+

-+name:+Wait+for+the+server+to+reboot
++local_action:+wait_for+host="{{ansible_host}}"+delay=15+state=started+port="{{ansible_port}}"+connect_timeout=10+timeout=180|code-block|syntax|javascript|3672|这就是完成任务的shell:+(+sleep+3+&&+/sbin/reboot+&+)代码行。|3673|在shell脚本中使用(+command+&+)在后台运行一个程序并分离它:命令立即成功，但在shell被销毁后仍然存在。|3674|Ansible立即得到响应，服务器在3秒后重新启动。|3675|entityMap^0|0|2|C|1H|J|28|1O|0|0|0|0|8|10|0|B|D|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|18|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|X|$]]

None of the above solutions worked reliably for me.

Issuing a <code>/sbin/reboot</code> crashes the play (the SSH connection is closed before ansible finished the task, it crashes even with <code>ignore_errors: true</code>) and <code>/usr/bin/systemd-run --on-active=2 /usr/bin/systemctl reboot</code> will not reboot after 2 seconds, but after a random amount of time between 20 seconds and one minute, so the delay is sometime not sufficient and this is not predictable.

Also I don't want to wait for minutes while a cloud server can reboot in few seconds.

So here is my solution:

<pre><code>- name: Reboot the server for kernel update
 shell: ( sleep 3 &amp;&amp; /sbin/reboot &amp; )
 async: 0
 poll: 0 

- name: Wait for the server to reboot
 local_action: wait_for host="{{ansible_host}}" delay=15 state=started port="{{ansible_port}}" connect_timeout=10 timeout=180
</code></pre>

That's the <code>shell: ( sleep 3 &amp;&amp; /sbin/reboot &amp; )</code> line that does the trick.

Using <code>( command &amp; )</code> in shell script runs a program in the background and detaches it: the command succeed immediately but persists after the shell is destroyed.

Ansible get its response immediately and the server reboots 3 seconds later.

blocks|key|4511194|text|-+name:+restart+server
++shell:+sleep+2+&&+shutdown+-r+now+"Ansible+updates+triggered"
++async:+1
++poll:+0
++become:+true
++ignore_errors:+true


-+name:+waiting+for+the+server+to+come+back
++local_action:+wait_for+host=testcentos+state=started+delay=30+timeout=300
++sudo:+false|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|4511195|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>- name: restart server
 shell: sleep 2 &amp;&amp; shutdown -r now "Ansible updates triggered"
 async: 1
 poll: 0
 become: true
 ignore_errors: true


- name: waiting for the server to come back
 local_action: wait_for host=testcentos state=started delay=30 timeout=300
 sudo: false
</code></pre>

blocks|key|3703|text|还有另一个版本(从其他答案中组合而来)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3704|---
-+name:+restart+server
++command:+/usr/bin/systemd-run+--on-active=5+--timer-property=AccuracySec=100ms+/usr/bin/systemctl+reboot
++async:+0
++poll:+0
++ignore_errors:+true
++become:+yes

-+name:+wait+for+server+{{+ansible_ssh_host+%7C+default(inventory_hostname)+}}+to+come+back+online
++wait_for:
++++port:+22
++++state:+started
++++host:+'{{+ansible_ssh_host+%7C+default(inventory_hostname)+}}'
++++delay:+30
++delegate_to:+localhost|code-block|syntax|javascript|3705|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Yet another (combined from other answers) version:

<pre><code>---
- name: restart server
 command: /usr/bin/systemd-run --on-active=5 --timer-property=AccuracySec=100ms /usr/bin/systemctl reboot
 async: 0
 poll: 0
 ignore_errors: true
 become: yes

- name: wait for server {{ ansible_ssh_host | default(inventory_hostname) }} to come back online
 wait_for:
 port: 22
 state: started
 host: '{{ ansible_ssh_host | default(inventory_hostname) }}'
 delay: 30
 delegate_to: localhost
</code></pre>

blocks|key|3731|text|我使用的是Ansible+2.5.3。下面的代码可以很容易地工作，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3732|-+name:+Rebooting+host
++shell:+'shutdown+-r+%2B1+"Reboot+triggered+by+Ansible"'

-+wait_for_connection:
++++delay:+90
++++timeout:+300|code-block|syntax|javascript|3733|您可以立即重新启动，如果您的计算机需要一段时间才能关闭，则插入延迟：|3734|++++-+name:+Rebooting+host
++++++shell:+'shutdown+-r+now+"Reboot+triggered+by+Ansible"'
++++++async:+1
++++++poll:+1
++++++ignore_errors:+true

#+Wait+120+seconds+to+make+sure+the+machine+won't+connect+immediately+in+the+next+section.
++++-+name:+Delay+for+the+host+to+go+down
++++++local_action:+shell+/bin/sleep+120|3735|然后进行轮询，使剧本尽快返回：|3736|++++-+name:+Wait+for+the+server+to+finish+rebooting
++++++wait_for_connection:
++++++++delay:+15
++++++++sleep:+15
++++++++timeout:+300|3737|这将使剧本在重启后尽快返回。|3738|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I am using Ansible 2.5.3.
Below code works with ease,

<pre><code>- name: Rebooting host
 shell: 'shutdown -r +1 "Reboot triggered by Ansible"'

- wait_for_connection:
 delay: 90
 timeout: 300
</code></pre>

You can reboot immediately, then insert a delay if your machine takes a while to go down:

<pre><code> - name: Rebooting host
 shell: 'shutdown -r now "Reboot triggered by Ansible"'
 async: 1
 poll: 1
 ignore_errors: true

# Wait 120 seconds to make sure the machine won't connect immediately in the next section.
 - name: Delay for the host to go down
 local_action: shell /bin/sleep 120
</code></pre>

Then poll to make the playbook return as soon as possible:

<pre><code> - name: Wait for the server to finish rebooting
 wait_for_connection:
 delay: 15
 sleep: 15
 timeout: 300
</code></pre>

This will make the playbook return as soon as possible after the reboot.

blocks|key|4511238|text|下面的解决方案非常适合我：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4511239|-+name:+Restart+machine
++shell:+"sleep+5+&&+sudo+shutdown+-r+now"
++async:+1
++poll:+0

-+name:+wait+for+ssh+again+available.
++wait_for_connection:
++++connect_timeout:+20
++++sleep:+5
++++delay:+5
++++timeout:+300|code-block|syntax|javascript|4511240|休眠是必需的，因为ansible只需要很短的时间就可以完成连接。关于这个问题的精彩帖子写在这里：https://www.jeffgeerling.com/blog/2018/reboot-and-wait-reboot-complete-ansible-playbook|offset|length|4511241|entityMap|0|LINK|mutability|MUTABLE|url|https://www.jeffgeerling.com/blog/2018/reboot-and-wait-reboot-complete-ansible-playbook^0|0|0|1C|2F|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Following solution works for me perfect:

<pre><code>- name: Restart machine
 shell: "sleep 5 &amp;&amp; sudo shutdown -r now"
 async: 1
 poll: 0

- name: wait for ssh again available.
 wait_for_connection:
 connect_timeout: 20
 sleep: 5
 delay: 5
 timeout: 300
</code></pre>

Sleep is required because ansible requires few second's to wrap up connection.
Excelent post about this problem was written here:
<a href="https://www.jeffgeerling.com/blog/2018/reboot-and-wait-reboot-complete-ansible-playbook" rel="nofollow noreferrer">https://www.jeffgeerling.com/blog/2018/reboot-and-wait-reboot-complete-ansible-playbook</a>

I'm trying to reboot server running <code>CentOS 7</code> on VirtualBox. I use this task:

<pre><code>- name: Restart server
 command: /sbin/reboot
 async: 0
 poll: 0
 ignore_errors: true
</code></pre>

Server is rebooted, but I get this error:

<pre><code>TASK: [common | Restart server] ***********************************************
fatal: [rolcabox] =&gt; SSH Error: Shared connection to 127.0.0.1 closed.
It is sometimes useful to re-run the command using -vvvv, which prints SSH debug output to help diagnose the issue.

FATAL: all hosts have already failed -- aborting
</code></pre>

What am I doing wrong? How can I fix this?

How to reboot CentOS 7 with Ansible?

云服务器

服务器

CentOS

我正在尝试重新启动在VirtualBox上运行CentOS 7的服务器。我使用这个任务：- name: Restart server  command: /sbin/reboot  async: 0  poll: 0  ignore_errors: true服务器重新启动，但我收到以下错误：TASK: [common ...

问如何使用Ansible重启CentOS 7？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Ansible重启CentOS 7？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Ansible重启CentOS 7？
EN