Forum > GPU crunching
CPU <-> GPU rebranding
jasonkeil:
does anybody know how to rescheduler 1.9 to work with s@h beta test? i'm having problems with vlars and would like to move them to the cpu.
here is the thread that states my problem and Joe suggestion. any suggestions would be helpful and appreciated.
http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=1581
msattler:
Well........
I just had a scare with the rebranding tool.......
Got some new cuda work overnight, and ran the tool to move some VLAR over to the CPU. Tool ran, moved the work, and got the password error when restarting Boinc.
Manually shut Boinc down and restarted it, and when it came back up, the 'attach to project' window came up!!! No projects, no tasks!
Shut it down again and restarted it again, and, praise to the Gods of Seti....my tasks were back. The only ill effect was the loss of a bunch of crunch time on 4 AP wu's it had been crunching on....they exited with computation errors.
I think from now on I will shut down Boinc manually before running the rebranding tool and restart it manuall once it is done, unless the tool can be modified to start and stop Boinc in a safer manner.
Not to diss the tool, mind you.....I am glad it is available for those like me who practice 'no WU left behind'....LOL.
I am just going to be more cautious when using it until a fix is found or a successful non-vlarkill app comes along and I can update my drivers to run it.
Raistmer:
Non-service BOINC installation bugged by default.
Cause there is no correct method to end BOINC and be sure it's client_state.xml is written already.
You could implement some watchdogs or pinging or simple put pause in bat-file, but "boincmgr --quit" is not enough.
Actually I prefer just to kill boinc.exe process by wkill tool.
This method doesn't give guaranty that all science app are finished, htey can remain actie ~30 seconds after boinc.exe process kill, but at least I can be sure no more client_state.xml writes will be follow.
Regarding rebranding tool AFAIK it will not reschedule already started tasks so it doesn't need science apps exit, it only needs boinc.exe exit to keep client_state.xml safe.
@msattler
In your case it seems client_state_prev.xml was used to restore your BOINC. You are lucky indeed :)
Marius:
--- Quote from: msattler ---I just had a scare with the rebranding tool.......
--- End quote ---
Don't worry about it to much, for what i know boincmgr just misfired on restart and got credential errors (like you had before i guess). Boincmgr screen will be shown completely blanc without any tasks and projects, i've seen this before and i'm not really worried about it. Restarting boincmgr will solve it all. However those computation errors are weird, they should not have happened as i don't touch any of the the running workunits. Mayby Raistmer is right about reused .._prev.xml, but i'm not sure about that (and difficult to detect, mayby there was a collision with boinc.exe?)
Still this is a sign things can go wrong on 64 bit system (=systems not run with standard boinc service). If you happen to know a safe method on stopping/restarting boinc please do (better safe then sorry). I would appreciate any hint or report with workarounds, i'll happily adopt it in the tool if i can, but for now i dont have any workarounds (other then killing boinc the hard way with "pskill boinc.exe" (don't try this for fun!)).
Josef W. Segur:
Marius, would you describe more fully what the 1.9 release note relating to SETI Beta means? Is it just avoiding messing with Beta work, or actually meant to allow rebranding of work at Beta? If the latter, it appears not to be working from Jason Keil's experience.
Joe
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version