2005-03-28 11:08:37 [SETI@home] Deferring communication with project for 1 weeks, 3 days, 6 hours, 41 minutes, and 21 seconds

Questions and Answers : Macintosh : 2005-03-28 11:08:37 [SETI@home] Deferring communication with project for 1 weeks, 3 days, 6 hours, 41 minutes, and 21 seconds
Message board moderation

To post messages, you must log in.

AuthorMessage
Aleksander Szablewski

Send message
Joined: 3 Apr 99
Posts: 34
Credit: 5,133,740
RAC: 0
Poland
Message 91821 - Posted: 28 Mar 2005, 9:18:53 UTC

Nice, isn't it?

The SETI project is EMPTY on my CPU, yet my account RESULTS show some work unit should be computed.

I can see many people have similar problems.
But no answers on that :-(

I think I'll better quit the project.

Bye.
ID: 91821 · Report as offensive
C

Send message
Joined: 3 Apr 99
Posts: 240
Credit: 7,716,977
RAC: 0
United States
Message 91947 - Posted: 28 Mar 2005, 16:09:09 UTC

Easy solution: Change your computer clock. I had a similar problem, so I added the defferal time to the current time, set my clock to about 5 minutes before that, waited five minutes, and SETI decided it was through with the deferral and contacted the server to download more work. When it was through downloading, I reset my clock to the correct time and proceeded merrily on my way!

C

Join Team MacNN
ID: 91947 · Report as offensive
Profile n1mie

Send message
Joined: 20 Jan 02
Posts: 11
Credit: 127,908
RAC: 0
United States
Message 92100 - Posted: 29 Mar 2005, 1:43:14 UTC - in response to Message 91947.  

> Easy solution: Change your computer clock. I had a similar problem, so I
> added the defferal time to the current time, set my clock to about 5 minutes
> before that, waited five minutes, and SETI decided it was through with the
> deferral and contacted the server to download more work. When it was through
> downloading, I reset my clock to the correct time and proceeded merrily on my
> way!
>
> C


That's one way to solve the problem. But when the client still won't work (dreaded empty file error) then it's moot. This crud just doesn't work on 10.2.8.
<img SRC="http://www.boincstats.com/stats/banner.php?cpid=5b627a4a8d262e4f4a81844654cfc68d">
ID: 92100 · Report as offensive
raghu

Send message
Joined: 5 Mar 01
Posts: 13
Credit: 172,588
RAC: 0
United States
Message 93715 - Posted: 1 Apr 2005, 15:19:36 UTC

A second option is to manually edit the rpcmin line in the client_state.xml file (when boinx has stopped running), and set it to 0. Restart boinc. Boinc should contact the server immediately. Your account results will be updated only when seti contacts the server, not when seti sends the results back to the server.
ID: 93715 · Report as offensive
Aleksander Szablewski

Send message
Joined: 3 Apr 99
Posts: 34
Credit: 5,133,740
RAC: 0
Poland
Message 93734 - Posted: 1 Apr 2005, 16:47:01 UTC - in response to Message 93715.  

> A second option is to manually edit the rpcmin line in the client_state.xml
> file (when boinx has stopped running), and set it to 0...

I could not find rpcmin string in the file :(
The only fix I found is reattaching to the project. But this aborts work units already downloaded. And the project knows nothing about it - meaning it still waits for the results.

ALX
ID: 93734 · Report as offensive
raghu

Send message
Joined: 5 Mar 01
Posts: 13
Credit: 172,588
RAC: 0
United States
Message 93828 - Posted: 1 Apr 2005, 23:28:50 UTC - in response to Message 93734.  
Last modified: 1 Apr 2005, 23:37:24 UTC

Sorry, I was a bit off. The string is called min_rpc_time. It's under a subheading called project in the client_state.xml file (should be in the parent boinc directory). In the file, min_rpc_time will be set to some huge number (in my file, it is 1112442888. This can be safely set to zero. Start boinc again - it should connect immediately.

Data on workunits (name of file and status comes at the bottom of the same file.
ID: 93828 · Report as offensive

Questions and Answers : Macintosh : 2005-03-28 11:08:37 [SETI@home] Deferring communication with project for 1 weeks, 3 days, 6 hours, 41 minutes, and 21 seconds


 
©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.