Message boards :
Number crunching :
ET Phone home?
Message board moderation
Author | Message |
---|---|
Brkovip Send message Joined: 18 May 99 Posts: 274 Credit: 144,414,367 RAC: 0 |
Hello everyone, I am having some issues on this system: ID: 6790314 with the BOINC version 7.0.28. It seems to refuse to call home and get new tasks or report tasks unless I manually send them. I have tried changing network settings around and nothing seems to help. I am hoping I am just missing something silly with this system. TIA |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Hello everyone, What are both your cache settings? Claggy |
Brkovip Send message Joined: 18 May 99 Posts: 274 Credit: 144,414,367 RAC: 0 |
Hello everyone, 1 and 1 |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Hello everyone, So at the moment, Boinc should cache up to 2 days worth of work, then wait for the cache to drop to 1 days worth of work before asking again, you could try 2 + 0.01 Claggy |
John Clark Send message Joined: 29 Sep 99 Posts: 16515 Credit: 4,418,829 RAC: 0 |
I had the same problem spread over several projects. This was resolved by using a BAT file to do the BOINC Manager update. The BAT file I use is specific for my system running SETI on the CPUs ... cls :START echo off time /t PING -n 3660 127.0.0.1>nul boinccmd --project http://setiathome.berkeley.edu/ update GOTO START The number, after the PING statement, is the time in seconds until the next update request. I now have few projects requiring manual updating between different project updates, unless I look in between the BAT file requests where the PING has a long set time. It's good to be back amongst friends and colleagues |
Slavac Send message Joined: 27 Apr 11 Posts: 1932 Credit: 17,952,639 RAC: 0 |
I had the same issue until Jason and Claggy sorted me out. 1. Go to your Boinc > Preferences > Network Usage > Click "Clear". 2. Now set your "Connect every __ Days" to 4. 3. Set "Additional Work Buffer" to 0.01 4. Click "OK" Why this works, I have no idea but it worked for me. Executive Director GPU Users Group Inc. - brad@gpuug.org |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I had the same problem spread over several projects. This was resolved by using a BAT file to do the BOINC Manager update. In newer versions of windows you can use the command timeout to have a delay in your .bat scripts. Server 2003 also has it, but XP didn't see to get it. You can copy timeout.exe form a 2003 machine or download timeout.exe from the 2000 resource kit tools. http://www.petri.co.il/download_free_reskit_tools.htm Then you could have: @ECHO OFF cls :start @ECHO %time% boinccmd --project http://setiathome.berkeley.edu/ update timeout 3660 /nobreak goto start Also this would get the job done. @ECHO OFF @ECHO %time% boinccmd --project http://setiathome.berkeley.edu/ update timeout 3660 /nobreak %~nx0 SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.