forum.opsi.org

Verfasst: **02 Feb 2017, 01:11**

I've noticed that since 4.0.7 the bootimage has included some sort of waiting period before rebooting?

[7] [Feb 01 18:20:11] Command 'umount' found at: '/bin/umount' (Posix.py|710)
[6] [Feb 01 18:20:11] Executing: /bin/umount /dev/sda2 (Posix.py|769)
[6] [Feb 01 18:20:11] Using encoding 'ANSI_X3.4-1968' (Posix.py|802)
[7] [Feb 01 18:20:13] Exit code: 0 (Posix.py|853)
[5] [Feb 01 18:20:13] diskcounter is still 0 (setup.py|971)
[7] [Feb 01 18:20:13] Command 'sleep' found at: '/bin/sleep' (Posix.py|710)
[7] [Feb 01 18:20:13] Command 'shutdown' found at: '/sbin/shutdown' (Posix.py|710)
[6] [Feb 01 18:20:13] Executing: /bin/sleep 60; /sbin/shutdown -r now (Posix.py|769)
[7] [Feb 01 18:20:13] Command 'bash' found at: '/bin/bash' (Posix.py|710)
[6] [Feb 01 18:20:13] Executing: /bin/sleep 1 (Posix.py|769)
[7] [Feb 01 18:20:13] Command 'reboot' found at: '/sbin/reboot' (Posix.py|710)
[6] [Feb 01 18:20:13] Executing: /sbin/reboot -p (Posix.py|769)
[5] [Feb 01 18:20:13] Script execution successful (master.py|1466)
[7] [Feb 01 18:20:13] Executing jsonrpc method 'productOnClient_updateObjects' on host u'opsi.gcecad-service.nl' (JSONRPC.py|115)
[7] [Feb 01 18:20:13] Posting request... (JSONRPC.py|713)
[7] [Feb 01 18:20:13] Starting new HTTPS connection (0) to opsi.gcecad-service.nl:4447 (HTTP.py|645)
[7] [Feb 01 18:20:13] Connection established to: opsi.gcecad-service.nl (HTTP.py|647)
[7] [Feb 01 18:20:19] Closing connection: <httplib.HTTPSConnection instance at 0x7f4fdcb44d88> (HTTP.py|565)
[7] [Feb 01 18:20:19] Content-Type: gzip-application/json;charset=utf-8, Content-Encoding: deflate (JSONRPC.py|730)
[7] [Feb 01 18:20:19] Expecting deflated data from server (backwards compatible) (JSONRPC.py|738)
[6] [Feb 01 18:20:19] Received signal 1 (master.py|584)
[6] [Feb 01 18:20:19] Received signal 15 (master.py|584)
[5] [Feb 01 18:20:19] Need to terminate (master.py|586)
[6] [Feb 01 18:20:19] Executing: cat /var/tmp/opsi/sysconf.ini (Posix.py|769)

I'm looking at the /bin/sleep 60 command here. Has this been included for a reason, or something?

Verfasst: **02 Feb 2017, 07:20**

yes some things changes with 4.0.6 and then again with 4.0.7

In internal tests we saw that sometimes the disk was not properly synced, therefore the 60 seconds wait (yeah i know a sync instruction would be better

). Then we also had some issues with the reboot. The command was send but the machine didn't reboot, therefore the multiple different reboot calls.

Now with the current stable bootimage (20161221) those multiple reboot instruction are dismissed. Now we run one reboot command with a one minute delay. This had to be done becasue on systemd the reboot is faster, compared to sysV and sometimes the bootimage had a failed state when the machine rebooted. In the end the OS installation was successfull but the report stayed at false until the client-agent installed.

Cheers
Mathias

Verfasst: **03 Feb 2017, 00:59**

Ah, ok, I didn't know this was a planned change. Then all is good.

forum.opsi.org

bootimage waiting to reboot [solved]

bootimage waiting to reboot [solved]

Re: bootimage waiting to reboot

Re: bootimage waiting to reboot