Thread 'No results-- where did I break it?'

Author	Message
CroixDad Send message Joined: 11 Dec 05 Posts: 3	Message 1793 - Posted: 11 Dec 2005, 20:25:21 UTC ok -- Been with SETI 5+ years. saw that SETI client being shutdown so downloaded BOINC. I cant see any progress or even past results with SETI. connection to 'net not an issue unless I have to "select" a computer on the file tab. No clue what I am doing wrong altho its probably simple mistake.. but getting increasingly frustrated with this. seems to have downloaded but no uploads, no results.. help! lol Paul E. Lavelle San Francisco ID: 1793 ·

Jim K Send message Joined: 8 Sep 05 Posts: 168	Message 1794 - Posted: 11 Dec 2005, 20:59:49 UTC Read Seti Home Page Please... BOINC Wiki ID: 1794 ·

CroixDad Send message Joined: 11 Dec 05 Posts: 3	Message 1795 - Posted: 11 Dec 2005, 22:03:10 UTC ok -- <sigh> Here is the blasted log. is the program working as intended or is there some error in how I installed it. Please I understand you are all busy but unless you are versed in the WIKI and know where to look, all you do is hit links forever that generally tend to confuse simple minds like myself.. just some straightforward answers please.. is it working -- yes or no. If not, what did I do wrong (if anything) If program or servers are faulty or just not working the way you want, just say so. we all know this is work in progress so just say it.. sending me to the hell of 10000 links where I am inclined to read them all and waste my time and yours isnt helping. 12/12/2005 9:20:48 AM\|\|Starting BOINC client version 5.2.13 for windows_intelx86 12/12/2005 9:20:48 AM\|\|libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3 12/12/2005 9:20:48 AM\|\|Data directory: C:\\Program Files\\BOINC 12/12/2005 9:20:48 AM\|\|Processor: 2 GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz 12/12/2005 9:20:48 AM\|\|Memory: 2.00 GB physical, 3.85 GB virtual 12/12/2005 9:20:48 AM\|\|Disk: 74.52 GB total, 62.95 GB free 12/12/2005 9:20:48 AM\|SETI@home\|Computer ID: 1929216; location: home; project prefs: default 12/12/2005 9:20:48 AM\|\|General prefs: from SETI@home (last modified 2005-06-28 21:15:54) 12/12/2005 9:20:48 AM\|\|General prefs: no separate prefs for home; using your defaults 12/12/2005 9:20:49 AM\|\|Remote control not allowed; using loopback address 12/12/2005 9:20:49 AM\|SETI@home\|Started upload of 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 9:20:49 AM\|SETI@home\|Started upload of 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 9:20:49 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:20:49 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:20:49 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:21:04 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 9:21:04 AM\|SETI@home\|No schedulers responded 12/12/2005 9:22:04 AM\|SETI@home\|Fetching master file 12/12/2005 9:22:09 AM\|SETI@home\|Master file download succeeded 12/12/2005 9:22:14 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:22:14 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:22:14 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:22:24 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 9:22:24 AM\|SETI@home\|No schedulers responded 12/12/2005 9:23:24 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:23:24 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:23:24 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:23:47 AM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 9:23:49 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 9:23:49 AM\|SETI@home\|No schedulers responded 12/12/2005 9:23:59 AM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.16480.234634.81_3_0: error 500 12/12/2005 9:23:59 AM\|SETI@home\|Backing off 1 hours, 17 minutes, and 36 seconds on upload of file 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 9:23:59 AM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.19344.234660.231_1_0: error 500 12/12/2005 9:23:59 AM\|SETI@home\|Backing off 52 minutes and 1 seconds on upload of file 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 9:24:49 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:24:49 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:24:49 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:25:12 AM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 9:25:14 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 9:25:14 AM\|SETI@home\|No schedulers responded 12/12/2005 9:26:14 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:26:14 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:26:14 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:26:37 AM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 9:26:39 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 9:26:39 AM\|SETI@home\|No schedulers responded 12/12/2005 9:27:39 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:27:39 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:27:39 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:28:01 AM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 9:28:04 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 9:28:04 AM\|SETI@home\|No schedulers responded 12/12/2005 9:29:34 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:29:34 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:29:34 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:29:57 AM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 9:29:59 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 9:29:59 AM\|SETI@home\|No schedulers responded 12/12/2005 9:35:44 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:35:44 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:35:44 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:36:07 AM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 9:36:09 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 9:36:09 AM\|SETI@home\|No schedulers responded 12/12/2005 9:45:29 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 9:45:29 AM\|SETI@home\|Reason: Requested by user 12/12/2005 9:45:29 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 9:45:52 AM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 9:45:54 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 9:45:54 AM\|SETI@home\|No schedulers responded 12/12/2005 10:16:01 AM\|SETI@home\|Started upload of 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 10:16:24 AM\|\|Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu] 12/12/2005 10:16:24 AM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.19344.234660.231_1_0: system I/O 12/12/2005 10:16:24 AM\|SETI@home\|Backing off 16 minutes and 54 seconds on upload of file 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 10:20:24 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 10:20:24 AM\|SETI@home\|Reason: Requested by user 12/12/2005 10:20:24 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 10:20:34 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 10:20:34 AM\|SETI@home\|No schedulers responded 12/12/2005 10:33:19 AM\|SETI@home\|Started upload of 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 10:36:30 AM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.19344.234660.231_1_0: error 500 12/12/2005 10:36:30 AM\|SETI@home\|Backing off 1 hours, 57 minutes, and 36 seconds on upload of file 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 10:41:36 AM\|SETI@home\|Started upload of 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 10:42:23 AM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.16480.234634.81_3_0: error 500 12/12/2005 10:42:23 AM\|SETI@home\|Backing off 2 hours, 51 minutes, and 5 seconds on upload of file 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 11:57:54 AM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 11:57:54 AM\|SETI@home\|Reason: Requested by user 12/12/2005 11:57:54 AM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 11:58:04 AM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 11:58:04 AM\|SETI@home\|No schedulers responded 12/12/2005 12:01:28 PM\|SETI@home\|Started upload of 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 12:02:46 PM\|\|Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu] 12/12/2005 12:02:46 PM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.16480.234634.81_3_0: system I/O 12/12/2005 12:02:46 PM\|SETI@home\|Backing off 3 hours, 0 minutes, and 19 seconds on upload of file 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 12:11:50 PM\|SETI@home\|Started upload of 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 12:12:12 PM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.16480.234634.81_3_0: error 500 12/12/2005 12:12:12 PM\|SETI@home\|Backing off 18 minutes and 35 seconds on upload of file 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 12:30:48 PM\|SETI@home\|Started upload of 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 12:32:24 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:32:24 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:32:24 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:32:46 PM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 12:32:49 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 12:32:49 PM\|SETI@home\|No schedulers responded 12/12/2005 12:33:49 PM\|SETI@home\|Fetching master file 12/12/2005 12:33:54 PM\|SETI@home\|Master file download succeeded 12/12/2005 12:33:59 PM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.16480.234634.81_3_0: error 500 12/12/2005 12:33:59 PM\|SETI@home\|Backing off 2 hours, 29 minutes, and 32 seconds on upload of file 16ap04aa.11863.16480.234634.81_3_0 12/12/2005 12:33:59 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:33:59 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:33:59 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:34:07 PM\|SETI@home\|Started upload of 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 12:34:22 PM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 12:34:24 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 12:34:24 PM\|SETI@home\|No schedulers responded 12/12/2005 12:34:54 PM\|SETI@home\|Temporarily failed upload of 16ap04aa.11863.19344.234660.231_1_0: error 500 12/12/2005 12:34:54 PM\|SETI@home\|Backing off 3 hours, 50 minutes, and 40 seconds on upload of file 16ap04aa.11863.19344.234660.231_1_0 12/12/2005 12:35:24 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:35:24 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:35:24 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:35:47 PM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 12:35:49 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 12:35:49 PM\|SETI@home\|No schedulers responded 12/12/2005 12:36:49 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:36:49 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:36:49 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:37:11 PM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 12:37:14 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 12:37:14 PM\|SETI@home\|No schedulers responded 12/12/2005 12:38:14 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:38:14 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:38:14 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:38:36 PM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 12:38:39 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 12:38:39 PM\|SETI@home\|No schedulers responded 12/12/2005 12:39:39 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:39:39 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:39:39 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:39:49 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 12:39:49 PM\|SETI@home\|No schedulers responded 12/12/2005 12:42:09 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:42:09 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:42:09 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:42:19 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 12:42:19 PM\|SETI@home\|No schedulers responded 12/12/2005 12:44:04 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:44:04 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:44:04 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:44:14 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 12:44:14 PM\|SETI@home\|No schedulers responded 12/12/2005 12:52:09 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:52:09 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:52:09 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:52:24 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 12:52:24 PM\|SETI@home\|No schedulers responded 12/12/2005 12:56:24 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 12:56:24 PM\|SETI@home\|Reason: Requested by user 12/12/2005 12:56:24 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 12:56:39 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 12/12/2005 12:56:39 PM\|SETI@home\|No schedulers responded 12/12/2005 1:51:03 PM\|\|Suspending computation and network activity - running CPU benchmarks 12/12/2005 1:51:05 PM\|\|Running CPU benchmarks 12/12/2005 1:52:04 PM\|\|Benchmark results: 12/12/2005 1:52:04 PM\|\| Number of CPUs: 2 12/12/2005 1:52:04 PM\|\| 1330 double precision MIPS (Whetstone) per CPU 12/12/2005 1:52:04 PM\|\| 1615 integer MIPS (Dhrystone) per CPU 12/12/2005 1:52:04 PM\|\|Finished CPU benchmarks 12/12/2005 1:52:05 PM\|\|Resuming computation and network activity 12/12/2005 1:52:05 PM\|\|request_reschedule_cpus: Resuming activities 12/12/2005 1:52:52 PM\|\|request_reschedule_cpus: project op 12/12/2005 1:52:55 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 12/12/2005 1:52:55 PM\|SETI@home\|Reason: Requested by user 12/12/2005 1:52:55 PM\|SETI@home\|Requesting 17280 seconds of new work, and reporting 1 results 12/12/2005 1:53:17 PM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 12/12/2005 1:53:20 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 12/12/2005 1:53:20 PM\|SETI@home\|No schedulers responded Paul E. Lavelle San Francisco ID: 1795 ·

Bill Michael Send message Joined: 30 Aug 05 Posts: 297	Message 1797 - Posted: 11 Dec 2005, 22:35:44 UTC As Jim said, you need to read the SETI home page. You are on the BOINC boards, and your problem is with the SETI project, not BOINC. Forgive all of us for being "short" with you, but SETI's problems are causing very heavy "what's going on" traffic at EVERY project, and here, and it's all the same questions, with the same answer, which is all over the SETI boards. However, I'll give you the very short version - the SETI project's servers are down. You will not be able to communicate with them. Their home page and tech news and all of their boards go into great detail on the why's, but there is no estimated date for a fix yet. From your logs, everything looks fine, except for the expected SETI issues. If you are attached to another project, I would just "Suspend" SETI and let the other project run until the SETI problems are solved. If you are not attached to another project, this would be a good time to see if there are any you would be interested in. One of the main features of BOINC is the ability to "crunch" for multiple projects, so that when one is down, or has no work to send, your computers stay busy on the others. We really will do anything we can to help - but you have to realize that you'll get better help asking at the right place! ID: 1797 ·

S@NL - EJG Send message Joined: 2 Sep 05 Posts: 5	Message 1798 - Posted: 11 Dec 2005, 22:37:40 UTC Last modified: 11 Dec 2005, 22:39:17 UTC Your program is working as intended. ;-) Seti has problems with the upload/download servers at the moment. If you look at the seti front page ( http://setiweb.ssl.berkeley.edu/ ) you will see these news items: December 9, 2005 We have turned off work distribution for a bit to allow result uploads to catch up. We will be extending the deadline for returning results so that the troubles with the result upload handler will not result in lost credit. December 8, 2005 We are experiencing heavy traffic on our data server. This is currently preventing some result uploads, but is getting better over time. More in Technical News. We will have to wait until they solved the problems. You can just wait until it gets better, Boinc will upload your work automatically when it is possible. Or attach to another project in the mean time. :-) Edit: hmmm... Bill was first. I have to learn how to type faster. ;-) ;-) ID: 1798 ·

CroixDad Send message Joined: 11 Dec 05 Posts: 3	Message 1802 - Posted: 12 Dec 2005, 2:53:22 UTC Thanks for the assist -- sorry -- I know this is BOINC but was told to cancel SETI and join BOINC :( I would have preferred other wy actually but thanks for your time. Peace Paul E. Lavelle San Francisco ID: 1802 ·

Jim K Send message Joined: 8 Sep 05 Posts: 168	Message 1805 - Posted: 12 Dec 2005, 4:40:51 UTC I take it you did not read the front page, the part where it stated that the sever is under a heavy load and will take time to get back to normal and they have stopped downloading and other functions did you huh..... BOINC Wiki ID: 1805 ·

Les Bayliss Help desk expert Send message Joined: 25 Nov 05 Posts: 1654	Message 1806 - Posted: 12 Dec 2005, 5:10:30 UTC Just to confuse the issue, there are two SETI's: Classic SETI, (the original, and soon to die), and BOINC SETI, the new version. Enhanced, new color scheme, all mod cons. So you can continue to talk about SETI, but it is best to look at the SETI site for SETI news, and here at the BOINC site for news on the BOINC part. ID: 1806 ·

Dave Kimble Send message Joined: 24 Nov 05 Posts: 4	Message 1808 - Posted: 12 Dec 2005, 7:40:49 UTC - in response to Message 1806. Wouldn't it be smart if when the SETI servers are down, client requests are re-routed to a BOINC server that replies "The SETI servers are down, please don't panic" instead of "failed with a return value of -106" ? This is called basic user-friendliness. I first joined BOINC on 19/11/2003 but had to give it away because I was getting sick and tired of people asking the boards is the servers were up all the time. Nothing much seems to have changed. How can this be so hard ? ID: 1808 ·

Paul D. Buck Send message Joined: 29 Aug 05 Posts: 225	Message 1811 - Posted: 12 Dec 2005, 11:14:00 UTC - in response to Message 1808. Wouldn't it be smart if when the SETI servers are down, client requests are re-routed to a BOINC server that replies "The SETI servers are down, please don't panic" instead of "failed with a return value of -106" ? This is called basic user-friendliness. I first joined BOINC on 19/11/2003 but had to give it away because I was getting sick and tired of people asking the boards is the servers were up all the time. Nothing much seems to have changed. How can this be so hard ? Yes, but, this means that the server request has to complete so that the servers can tell the clients that they are down. The later builds of the BOINC Client software do have more friendly messages, but the response error can be any one of several. So, it is not practical to just show one message. ID: 1811 ·

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.