| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: What is the boinc friendly way to do a scheduled reboot? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 11
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This pertains to an automated, scheduled reboot. My script does a boinc suspend on the project, and then sleeps for 1 minute, and then reboots. However, this procedure clobbered an upload in progress early this morning. Apparently suspending a project does not suspend boinc uploads. My next guess would be to do a "boinccmd --get_file_transfers", until no transfers are happening, and then reboot, but I'm not sure that this would be sufficient. Should I also do a "--set_network_mode never" before (or after?) checking if there is a transfer in progress? Or, would that kill an in progress transfer? Or is this over-kill, and maybe the script should just sleep for 10 minutes after doing the suspend and before doing the reboot? (A reboot job does a "resume", after waiting a minute for the boinc-client to start.)
|
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges: 
|
I may be misunderstanding something, but if I am going to reboot the hardware, I would exit BOINC first, then do the reboot. I am assuming you have BOINC set to auto start after the reboot is finished. I would give BOINC about a 5 second window in order to have it do an orderly exit.
----------------------------------------Cheers
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 1 times, last edit by Sgt.Joe at Jan 27, 2018 1:15:18 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Stopping the boinc-client, and then waiting a while might be what I'm looking for - if it gracefully suspends any running tasks and does not clobber any in progress upload / download.
My process runs at 4 AM, does a software update, and then reboots the machine, while I am still snoozing. |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges: 
|
I like Sgt Joe's idea. It's the least complicated and most sane way of automating this.
----------------------------------------A more complicated way would be to modify the BOINC client settings so that network access is not allowed around 4 AM; i.e. "Transfer files only between 4:15 AM and 3:45 AM" in Preferences, but... this is silly. Having the process shut down BOINC prior to doing its update and reboot seems to follow KISS principles. But you're right: does it gracefully shut down the client if it's in the middle of a file transfer? I'd have to manually test this by waiting around until an upload happens then executing your script to see what happens.
[Edit 1 times, last edit by hchc at Jan 27, 2018 11:37:12 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Belt and suspenders: 1) suspend tasks; 2) wait until no transfers; 3) stop boinc-client; 4) wait 10 minutes and reboot. That's what the script does now, and that should be more than sufficient - probably over-kill.
|
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges:
|
Won't the tasks still be suspended after the reboot?
----------------------------------------
|
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges:
|
Won't the tasks still be suspended after the reboot? Yes ! Since the tasks are tagged as suspended in the task list (client_state.xml). After the reboot, you have to resume the tasks. However, because boinc and its mechanisms are very robust, I do not particularly take care of boinc if I need to reboot a machine. The WU will restart at the last stored checkpoint, transfers will be re-initiated and completed. Cheers, Yves |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Won't the tasks still be suspended after the reboot? Yes. In the reboot script, after waiting 1 minute for boinc-client to start, a resume is issued for the project. It all seems to be working OK. I haven't experienced anything getting clobbered again (so far). |
||
|
|
mmonnin
Advanced Cruncher Joined: Jul 20, 2016 Post Count: 148 Status: Offline Project Badges:
|
I also recommend suspending tasks/project before shutting down the client. In particular, WUProp tasks sometimes have computational errors if they are not suspected before client shutdown. Some projects are better than others with interruptions.
---------------------------------------- |
||
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges: 
|
For me it worked just OK, every time I reboot...though Linux (Ubuntu) have some issues with Intel motherboards, so have to shut down the system & then start again...same board on Windows reboots OK.
----------------------------------------Anyway, never had to run WU from beginning...so it's all OK, any time you reboot! Why? 1. If BOINC is doing some network stuff, it will either finish & system will wait on it, or it will do it after reboot (not completed action in Transfers). 2. If BOINC is closing, it will also save all data on disk upon exiting. Including the last saves for WUs. 3. BOINC has previously written all past saves for progress of WUs in regular intervals according to app program. So no worry about "lost time". So why do you worry about that? |
||
|
|
|