Can someone please help me?

Questions and Answers : Preferences : Can someone please help me?
Message board moderation

To post messages, you must log in.

AuthorMessage
Camel Guy

Send message
Joined: 3 Feb 07
Posts: 34
Credit: 24,261
RAC: 0
United States
Message 514686 - Posted: 7 Feb 2007, 20:10:57 UTC

I had this problem all of last night, so I finally closed BOINC and powered off my PC for the night. This morning, I've continued to have the problem and I've turned BOIN off and on and off and on and I've even uninstalled and reinstalled it. Nothing that I'm doing is fixing this and I don't know what to do. This is what I keep getting:

2/7/2007 11:39:28 AM||Starting BOINC client version 5.8.8 for windows_intelx86
2/7/2007 11:39:28 AM||log flags: task, file_xfer, sched_ops
2/7/2007 11:39:28 AM||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3
2/7/2007 11:39:28 AM||Data directory: C:\\Program Files\\BOINC
2/7/2007 11:39:28 AM||Processor: 1 AuthenticAMD AMD Athlon(tm) 64 Processor 3700+ [x86 Family 15 Model 39 Stepping 1] [fpu tsc pae nx sse sse2 3dnow mmx]
2/7/2007 11:39:28 AM||Memory: 958.48 MB physical, 2.26 GB virtual
2/7/2007 11:39:28 AM||Disk: 178.30 GB total, 121.49 GB free
2/7/2007 11:39:28 AM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 3064068; location: home; project prefs: default
2/7/2007 11:39:28 AM||General prefs: from SETI@home (last modified 2007-02-03 07:08:16)
2/7/2007 11:39:28 AM||Host location: home
2/7/2007 11:39:28 AM||General prefs: no separate prefs for home; using your defaults
2/7/2007 11:39:28 AM||Reading preferences override file
2/7/2007 11:40:13 AM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 11:40:13 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 11:40:35 AM||Project communication failed: attempting access to reference site
2/7/2007 11:40:36 AM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 11:40:38 AM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 11:40:38 AM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 11:40:38 AM|SETI@home|Reason: scheduler request failed
2/7/2007 11:41:38 AM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 11:41:38 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 11:42:03 AM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 11:42:03 AM|SETI@home|Deferring communication for 11 sec
2/7/2007 11:42:03 AM|SETI@home|Reason: requested by project
2/7/2007 11:42:03 AM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 11:42:03 AM|SETI@home|Reason: no work from project
2/7/2007 11:43:03 AM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 11:43:03 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 11:43:25 AM||Project communication failed: attempting access to reference site
2/7/2007 11:43:26 AM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 11:43:28 AM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 11:43:28 AM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 11:43:28 AM|SETI@home|Reason: scheduler request failed
2/7/2007 11:44:34 AM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 11:44:34 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 11:44:59 AM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 11:44:59 AM|SETI@home|Deferring communication for 11 sec
2/7/2007 11:44:59 AM|SETI@home|Reason: requested by project
2/7/2007 11:44:59 AM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 11:44:59 AM|SETI@home|Reason: no work from project
2/7/2007 11:46:04 AM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 11:46:04 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 11:46:34 AM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 11:46:34 AM|SETI@home|Deferring communication for 11 sec
2/7/2007 11:46:34 AM|SETI@home|Reason: requested by project
2/7/2007 11:46:34 AM|SETI@home|Deferring communication for 1 min 21 sec
2/7/2007 11:46:34 AM|SETI@home|Reason: no work from project
2/7/2007 11:47:59 AM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 11:47:59 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 11:48:29 AM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 11:48:29 AM|SETI@home|Deferring communication for 11 sec
2/7/2007 11:48:29 AM|SETI@home|Reason: requested by project
2/7/2007 11:48:29 AM|SETI@home|Deferring communication for 1 min 12 sec
2/7/2007 11:48:29 AM|SETI@home|Reason: no work from project
2/7/2007 11:49:44 AM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 11:49:44 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 11:50:06 AM||Project communication failed: attempting access to reference site
2/7/2007 11:50:07 AM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 11:50:09 AM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 11:50:09 AM|SETI@home|Deferring communication for 9 min 21 sec
2/7/2007 11:50:09 AM|SETI@home|Reason: scheduler request failed
2/7/2007 11:59:35 AM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 11:59:35 AM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 12:00:00 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 12:00:00 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 12:00:00 PM|SETI@home|Reason: requested by project
2/7/2007 12:00:00 PM|SETI@home|Deferring communication for 38 min 56 sec
2/7/2007 12:00:00 PM|SETI@home|Reason: no work from project
2/7/2007 12:39:03 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 12:39:03 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 12:39:08 PM|SETI@home|Scheduler request failed: HTTP internal server error
2/7/2007 12:39:08 PM|SETI@home|Deferring communication for 1 hr 21 min 33 sec
2/7/2007 12:39:08 PM|SETI@home|Reason: scheduler request failed
2/7/2007 1:04:10 PM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 1:04:10 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:04:32 PM||Project communication failed: attempting access to reference site
2/7/2007 1:04:33 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 1:04:35 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 1:04:35 PM|SETI@home|Deferring communication for 3 hr 15 min 16 sec
2/7/2007 1:04:35 PM|SETI@home|Reason: scheduler request failed
2/7/2007 1:31:07 PM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 1:31:07 PM|SETI@home|(not requesting new work or reporting completed tasks)
2/7/2007 1:31:22 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 1:31:22 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 1:31:22 PM|SETI@home|Reason: requested by project
2/7/2007 1:31:22 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 1:31:22 PM|SETI@home|Reason: no work from project
2/7/2007 1:32:22 PM|SETI@home|Fetching scheduler list
2/7/2007 1:32:27 PM|SETI@home|Master file download succeeded
2/7/2007 1:32:32 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:32:32 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:32:54 PM||Project communication failed: attempting access to reference site
2/7/2007 1:32:55 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 1:32:57 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 1:32:57 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 1:32:57 PM|SETI@home|Reason: scheduler request failed
2/7/2007 1:34:02 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:34:02 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:34:24 PM||Project communication failed: attempting access to reference site
2/7/2007 1:34:25 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 1:34:27 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 1:34:27 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 1:34:27 PM|SETI@home|Reason: scheduler request failed
2/7/2007 1:35:32 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:35:32 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:36:02 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 1:36:02 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 1:36:02 PM|SETI@home|Reason: requested by project
2/7/2007 1:36:02 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 1:36:02 PM|SETI@home|Reason: no work from project
2/7/2007 1:37:03 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:37:03 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:37:25 PM||Project communication failed: attempting access to reference site
2/7/2007 1:37:26 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 1:37:28 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 1:37:28 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 1:37:28 PM|SETI@home|Reason: scheduler request failed
2/7/2007 1:38:33 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:38:33 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:39:03 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 1:39:03 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 1:39:03 PM|SETI@home|Reason: requested by project
2/7/2007 1:39:03 PM|SETI@home|Deferring communication for 1 min 45 sec
2/7/2007 1:39:03 PM|SETI@home|Reason: no work from project
2/7/2007 1:40:53 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:40:53 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:41:15 PM||Project communication failed: attempting access to reference site
2/7/2007 1:41:16 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 1:41:18 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 1:41:18 PM|SETI@home|Deferring communication for 3 min 57 sec
2/7/2007 1:41:18 PM|SETI@home|Reason: scheduler request failed
2/7/2007 1:45:21 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:45:21 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:45:56 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 1:45:56 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 1:45:56 PM|SETI@home|Reason: requested by project
2/7/2007 1:45:56 PM|SETI@home|Deferring communication for 7 min 20 sec
2/7/2007 1:45:56 PM|SETI@home|Reason: no work from project
2/7/2007 1:53:17 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 1:53:17 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:53:39 PM||Project communication failed: attempting access to reference site
2/7/2007 1:53:40 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 1:53:42 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 1:53:42 PM|SETI@home|Deferring communication for 10 min 59 sec
2/7/2007 1:53:42 PM|SETI@home|Reason: scheduler request failed
2/7/2007 1:57:53 PM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 1:57:53 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 1:58:14 PM||Project communication failed: attempting access to reference site
2/7/2007 1:58:15 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 1:58:18 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 1:58:18 PM|SETI@home|Deferring communication for 12 min 51 sec
2/7/2007 1:58:18 PM|SETI@home|Reason: scheduler request failed
2/7/2007 2:11:13 PM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 2:11:13 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:11:39 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:11:39 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:11:39 PM|SETI@home|Reason: requested by project
2/7/2007 2:11:39 PM|SETI@home|Deferring communication for 15 min 56 sec
2/7/2007 2:11:39 PM|SETI@home|Reason: no work from project
2/7/2007 2:27:40 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:27:40 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:28:10 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:28:10 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:28:10 PM|SETI@home|Reason: requested by project
2/7/2007 2:28:10 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 2:28:10 PM|SETI@home|Reason: no work from project
2/7/2007 2:29:10 PM|SETI@home|Fetching scheduler list
2/7/2007 2:29:15 PM|SETI@home|Master file download succeeded
2/7/2007 2:29:20 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:29:20 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:29:45 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:29:45 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:29:45 PM|SETI@home|Reason: requested by project
2/7/2007 2:29:45 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 2:29:45 PM|SETI@home|Reason: no work from project
2/7/2007 2:30:50 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:30:50 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:31:20 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:31:20 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:31:20 PM|SETI@home|Reason: requested by project
2/7/2007 2:31:20 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 2:31:20 PM|SETI@home|Reason: no work from project
2/7/2007 2:32:20 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:32:20 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:32:55 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:32:55 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:32:55 PM|SETI@home|Reason: requested by project
2/7/2007 2:32:55 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 2:32:55 PM|SETI@home|Reason: no work from project
2/7/2007 2:34:01 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:34:01 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:34:31 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:34:31 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:34:31 PM|SETI@home|Reason: requested by project
2/7/2007 2:34:31 PM|SETI@home|Deferring communication for 1 min 0 sec
2/7/2007 2:34:31 PM|SETI@home|Reason: no work from project
2/7/2007 2:35:31 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:35:31 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:35:56 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:35:56 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:35:56 PM|SETI@home|Reason: requested by project
2/7/2007 2:35:56 PM|SETI@home|Deferring communication for 1 min 27 sec
2/7/2007 2:35:56 PM|SETI@home|Reason: no work from project
2/7/2007 2:37:26 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:37:26 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:37:47 PM||Project communication failed: attempting access to reference site
2/7/2007 2:37:48 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 2:37:51 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 2:37:51 PM|SETI@home|Deferring communication for 3 min 32 sec
2/7/2007 2:37:51 PM|SETI@home|Reason: scheduler request failed
2/7/2007 2:41:27 PM|SETI@home|Sending scheduler request: To fetch work
2/7/2007 2:41:27 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:41:52 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 2:41:52 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 2:41:52 PM|SETI@home|Reason: requested by project
2/7/2007 2:41:52 PM|SETI@home|Deferring communication for 14 min 35 sec
2/7/2007 2:41:52 PM|SETI@home|Reason: no work from project
2/7/2007 2:48:52 PM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 2:48:52 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 2:49:14 PM||Project communication failed: attempting access to reference site
2/7/2007 2:49:15 PM||Access to reference site succeeded - project servers may be temporarily down.
2/7/2007 2:49:17 PM|SETI@home|Scheduler request failed: couldn't connect to server
2/7/2007 2:49:17 PM|SETI@home|Deferring communication for 45 min 55 sec
2/7/2007 2:49:17 PM|SETI@home|Reason: scheduler request failed
2/7/2007 3:06:24 PM|SETI@home|Sending scheduler request: Requested by user
2/7/2007 3:06:24 PM|SETI@home|Requesting 8640 seconds of new work
2/7/2007 3:06:54 PM|SETI@home|Scheduler RPC succeeded [server version 507]
2/7/2007 3:06:54 PM|SETI@home|Deferring communication for 11 sec
2/7/2007 3:06:54 PM|SETI@home|Reason: requested by project
2/7/2007 3:06:54 PM|SETI@home|Deferring communication for 40 min 27 sec
2/7/2007 3:06:54 PM|SETI@home|Reason: no work from project


Now, those are just the messages that I've seen since just before noon. Surely SETI hasn't run out of work, so why does it keep telling me that there is no work to be done? What can I do to fix this? I'd like to get back to helping out, but I am about to give up, because I don't know what else to do. Can someone please help me? Thank you in advance for your time.
ID: 514686 · Report as offensive
John McLeod VII
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 15 Jul 99
Posts: 24806
Credit: 790,712
RAC: 0
United States
Message 514690 - Posted: 7 Feb 2007, 20:32:17 UTC

S@H has been having some server problems. It is likely that the problem is not on your end.

There are some failure to contact the server messages mixed in with successfull contact but no work supplied. This looks like the scheduler (one of the servers) and the database (another of the servers) are having come troubles.


BOINC WIKI
ID: 514690 · Report as offensive
Profile Shadow
Avatar

Send message
Joined: 17 May 99
Posts: 88
Credit: 2,880,148
RAC: 0
United Kingdom
Message 514872 - Posted: 8 Feb 2007, 7:31:21 UTC

there is problem on seti end the are doing something to the database. If you want on carry while seti has these problems setup in you preferences to get about 3 or 4 days work.


Sapiens dominabitur astris.
The wise shall exercise dominion over the stars.
ID: 514872 · Report as offensive
Camel Guy

Send message
Joined: 3 Feb 07
Posts: 34
Credit: 24,261
RAC: 0
United States
Message 514885 - Posted: 8 Feb 2007, 8:17:12 UTC

Thank you so very much John and Shadow! This afternoon, when I was trying to figure all of this out, I was really frustrated. I'm very new at this, but have taken some pride in pretty much being able to figure it all out for the most part, on my own. That definitely wasn't the case today. The reassurane from you guys that I wasn't doing anything wrong, is/was VERY helpful. Thanks again friends!


Shadow, I will look into implementing your suggestion right away. I must have missed that option, as I do not mind at all for my system to store several days worth of work at a time. Indeed, this suggestion will make it possible for me to continue to run tasks when there are server problems like these. Sadly, it looks as if I missed more than a day's worth of work. No big deal, live and learn, but at least it won't happen again.

If I may, I also want to thank you for joining with me on the "Friends of SETI" team. I'm so pleased to not feel so alone in this big community. As I said, I'm new at this. I really didn't want to involve myself with all of the politics of teams and competition and what not. I couldn't find a team that was interested in nothing more than just helping out and not making this into a bunch of clap trap regarding which team is better than another, so I formed my own. It's ideal for me to just let SETI@home run and to belong to a team of like-minded friends. I digress, but I wanted to make sure that I said hello and thank you for teaming up with me!
ID: 514885 · Report as offensive
Profile Graeme Stretton
Avatar

Send message
Joined: 2 Nov 01
Posts: 392
Credit: 349,012
RAC: 0
Australia
Message 541747 - Posted: 6 Apr 2007, 9:17:28 UTC - in response to Message 514872.  

there is problem on seti end the are doing something to the database. If you want on carry while seti has these problems setup in you preferences to get about 3 or 4 days work.



Could you give me a step by step guide on how to do this please?
ID: 541747 · Report as offensive
Profile mikey
Volunteer tester
Avatar

Send message
Joined: 17 Dec 99
Posts: 4215
Credit: 3,474,603
RAC: 0
United States
Message 541763 - Posted: 6 Apr 2007, 10:11:30 UTC - in response to Message 541747.  

there is problem on seti end the are doing something to the database. If you want on carry while seti has these problems setup in you preferences to get about 3 or 4 days work.



Could you give me a step by step guide on how to do this please?

Click on Your Account, general preferences, Connect to network about every. Anything from .1 to 10 days is acceptable. If you have a really fast computer you will need to play with the settings to get a full 3 or 4 days. Boinc seems to have issues with the estimation algorythym.
ID: 541763 · Report as offensive
Profile Graeme Stretton
Avatar

Send message
Joined: 2 Nov 01
Posts: 392
Credit: 349,012
RAC: 0
Australia
Message 541785 - Posted: 6 Apr 2007, 11:16:05 UTC - in response to Message 541763.  

there is problem on seti end the are doing something to the database. If you want on carry while seti has these problems setup in you preferences to get about 3 or 4 days work.



Could you give me a step by step guide on how to do this please?

Click on Your Account, general preferences, Connect to network about every. Anything from .1 to 10 days is acceptable. If you have a really fast computer you will need to play with the settings to get a full 3 or 4 days. Boinc seems to have issues with the estimation algorythym.



Thanks mate.
I did look but couldn't find it. Silly me :P
ID: 541785 · Report as offensive
Profile AspirationTower

Send message
Joined: 4 Jan 06
Posts: 97
Credit: 946,069
RAC: 0
United Kingdom
Message 589603 - Posted: 20 Jun 2007, 19:26:48 UTC

If you use your pc for CPU intensive things other than Boinc you might find that downloading 3 or 4 days worth of work takes longer than 3 or 4 days to complete, in this case you may find your WU's not completing by the deadline, (I found this to be the case on mine) and so reduced the rate again and instead added another Boinc related project to cover the times that Seti has server problems.
Resistence is futile! {evil cackle}
ID: 589603 · Report as offensive

Questions and Answers : Preferences : Can someone please help me?


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