NO WORK FROM SETI

Author	Message
Fuzzy Hollynoodles Volunteer tester Send message Joined: 3 Apr 99 Posts: 9659 Credit: 251,998 RAC: 0	Message 558553 - Posted: 3 May 2007, 4:39:38 UTC From the frontpage: May 1, 2007 Happy May Day. Unfortunately for us it's been "Mayday! Mayday!" At 4:43 (PDT) this morning, our science database machine, thumper, became hasenfeffer. It currently refuses to acknowledge that it has any disk drives. Since the controllers are attached to the motherboard, major repairs will probably be required. No work can be created until this machine gets fixed. We are on the phone with Sun now in hopes of securing repair or a replacement. More info in Technical News. Se Matt Lebofsky's posts here: http://setiathome.berkeley.edu/forum_thread.php?id=39188&nowrap=true#557665 and here: http://setiathome.berkeley.edu/forum_thread.php?id=39211&nowrap=true#558284 A good idea is to read through the threads and else keep an eye on the Technical News board. "I'm trying to maintain a shred of dignity in this world." - Me ID: 558553 ·

Dune_Finkleberry Send message Joined: 25 Feb 06 Posts: 6454 Credit: 198,656 RAC: 0	Message 558611 - Posted: 3 May 2007, 8:29:43 UTC The ol' processor probably appreciates the break, but I'll be looking forward to more work when it becomes available. Account frozen... ID: 558611 ·

Rockstar Send message Joined: 31 Mar 01 Posts: 7 Credit: 230,570 RAC: 0	Message 558811 - Posted: 3 May 2007, 21:48:59 UTC - in response to Message 558611. The ol' processor probably appreciates the break, but I'll be looking forward to more work when it becomes available. I agree -- we want the work !!!!!!!!!!! ID: 558811 ·

Jerry S Zelinske Send message Joined: 24 Sep 06 Posts: 59 Credit: 78,067 RAC: 0	Message 558861 - Posted: 3 May 2007, 23:29:47 UTC Great, now I'm going to have to attach to einstein@home, the Anti-seti@home. Looks for the complete oppostie signal if I understand the write up correctly... ID: 558861 ·

LoNero.net Send message Joined: 26 Oct 02 Posts: 1 Credit: 59,126 RAC: 0	Message 558971 - Posted: 4 May 2007, 3:22:23 UTC I know there were some server issues over the last couple of days but I was wondering if the problem I'm having is related to that. Here is the message I get: Thu May 3 10:39:17 2007\|\|Starting BOINC client version 5.4.9 for powerpc-apple-darwin Thu May 3 10:39:17 2007\|\|libcurl/7.15.3 OpenSSL/0.9.7l zlib/1.2.3 Thu May 3 10:39:17 2007\|\|Data directory: /Library/Application Support/BOINC Data Thu May 3 10:39:17 2007\|\|Processor: 2 Power Macintosh PowerMac3,6 Thu May 3 10:39:17 2007\|\|Memory: 1.00 GB physical, 0 bytes virtual Thu May 3 10:39:17 2007\|\|Disk: 74.41 GB total, 13.27 GB free Thu May 3 10:39:17 2007\|SETI@home\|URL: http://setiathome.berkeley.edu/; Computer ID: 2718511; location: home; project prefs: home Thu May 3 10:39:17 2007\|\|General prefs: from SETI@home (last modified 2005-06-30 22:55:06) Thu May 3 10:39:17 2007\|\|General prefs: no separate prefs for home; using your defaults Thu May 3 10:39:17 2007\|\|Listening on port 31416 Thu May 3 11:02:31 2007\|\|Rescheduling CPU: project reset by user Thu May 3 11:02:31 2007\|SETI@home\|Resetting project Thu May 3 11:02:31 2007\|\|Rescheduling CPU: exit_tasks Thu May 3 13:58:25 2007\|SETI@home\|Fetching scheduler list Thu May 3 13:58:30 2007\|SETI@home\|Scheduler list download succeeded Thu May 3 13:58:35 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 13:58:35 2007\|SETI@home\|Reason: Requested by user Thu May 3 13:58:35 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 13:59:40 2007\|SETI@home\|Scheduler request succeeded Thu May 3 13:59:55 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 13:59:55 2007\|SETI@home\|Reason: To fetch work Thu May 3 13:59:55 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:01:15 2007\|SETI@home\|Scheduler request succeeded Thu May 3 14:01:15 2007\|SETI@home\|No work from project Thu May 3 14:01:15 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 14:02:15 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 14:02:15 2007\|SETI@home\|Reason: To fetch work Thu May 3 14:02:15 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:04:15 2007\|\|Project communication failed: attempting access to reference site Thu May 3 14:04:16 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 14:04:20 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 14:04:20 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 14:05:20 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 14:05:20 2007\|SETI@home\|Reason: To fetch work Thu May 3 14:05:20 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:07:20 2007\|\|Project communication failed: attempting access to reference site Thu May 3 14:07:20 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 14:07:20 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 14:07:21 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 14:08:20 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 14:08:20 2007\|SETI@home\|Reason: To fetch work Thu May 3 14:08:20 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:09:11 2007\|SETI@home\|Scheduler request succeeded Thu May 3 14:09:11 2007\|SETI@home\|No work from project Thu May 3 14:09:11 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 14:10:11 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 14:10:11 2007\|SETI@home\|Reason: To fetch work Thu May 3 14:10:11 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:12:11 2007\|\|Project communication failed: attempting access to reference site Thu May 3 14:12:12 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 14:12:16 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 14:12:16 2007\|SETI@home\|Deferring scheduler requests for 2 minutes and 16 seconds Thu May 3 14:14:36 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 14:14:36 2007\|SETI@home\|Reason: To fetch work Thu May 3 14:14:36 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:16:36 2007\|\|Project communication failed: attempting access to reference site Thu May 3 14:16:37 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 14:16:41 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 14:16:41 2007\|SETI@home\|Deferring scheduler requests for 4 minutes and 23 seconds Thu May 3 14:21:07 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 14:21:07 2007\|SETI@home\|Reason: To fetch work Thu May 3 14:21:07 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:23:07 2007\|\|Project communication failed: attempting access to reference site Thu May 3 14:23:07 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 14:23:07 2007\|SETI@home\|Deferring scheduler requests for 15 minutes and 1 seconds Thu May 3 14:23:08 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 14:38:10 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 14:38:10 2007\|SETI@home\|Reason: To fetch work Thu May 3 14:38:10 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 14:40:10 2007\|\|Project communication failed: attempting access to reference site Thu May 3 14:40:11 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 14:40:15 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 14:40:15 2007\|SETI@home\|Deferring scheduler requests for 47 minutes and 18 seconds Thu May 3 15:27:38 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 15:27:38 2007\|SETI@home\|Reason: To fetch work Thu May 3 15:27:38 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 15:29:38 2007\|\|Project communication failed: attempting access to reference site Thu May 3 15:29:40 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 15:29:43 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 15:29:43 2007\|SETI@home\|Deferring scheduler requests for 47 minutes and 15 seconds Thu May 3 16:17:02 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 16:17:02 2007\|SETI@home\|Reason: To fetch work Thu May 3 16:17:02 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 16:19:02 2007\|\|Project communication failed: attempting access to reference site Thu May 3 16:19:03 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 16:19:07 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 16:19:07 2007\|SETI@home\|Deferring scheduler requests for 1 hours, 42 minutes and 43 seconds Thu May 3 18:01:53 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:01:53 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:01:53 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:03:53 2007\|\|Project communication failed: attempting access to reference site Thu May 3 18:03:54 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 18:03:58 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 18:03:58 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 18:04:58 2007\|SETI@home\|Fetching scheduler list Thu May 3 18:05:03 2007\|SETI@home\|Scheduler list download succeeded Thu May 3 18:05:08 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:05:08 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:05:08 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:06:03 2007\|SETI@home\|Scheduler request succeeded Thu May 3 18:06:03 2007\|SETI@home\|No work from project Thu May 3 18:06:03 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 18:07:04 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:07:04 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:07:04 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:07:44 2007\|SETI@home\|Scheduler request succeeded Thu May 3 18:07:44 2007\|SETI@home\|No work from project Thu May 3 18:07:44 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 18:08:44 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:08:44 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:08:44 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:10:44 2007\|\|Project communication failed: attempting access to reference site Thu May 3 18:10:45 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 18:10:49 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 18:10:49 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 18:11:49 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:11:49 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:11:49 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:12:44 2007\|SETI@home\|Scheduler request succeeded Thu May 3 18:12:44 2007\|SETI@home\|No work from project Thu May 3 18:12:44 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 18:13:45 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:13:45 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:13:45 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:15:45 2007\|\|Project communication failed: attempting access to reference site Thu May 3 18:15:45 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 18:15:45 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 29 seconds Thu May 3 18:15:46 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 18:17:15 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:17:15 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:17:15 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:19:15 2007\|\|Project communication failed: attempting access to reference site Thu May 3 18:19:16 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 18:19:20 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 18:19:20 2007\|SETI@home\|Deferring scheduler requests for 2 minutes and 41 seconds Thu May 3 18:22:06 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:22:06 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:22:06 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:24:06 2007\|\|Project communication failed: attempting access to reference site Thu May 3 18:24:06 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 18:24:06 2007\|SETI@home\|Deferring scheduler requests for 9 minutes and 44 seconds Thu May 3 18:24:07 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 18:33:52 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:33:52 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:33:52 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:35:52 2007\|\|Project communication failed: attempting access to reference site Thu May 3 18:35:52 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 18:35:52 2007\|SETI@home\|Deferring scheduler requests for 12 minutes and 32 seconds Thu May 3 18:35:53 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 18:48:29 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:48:29 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:48:29 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 18:49:30 2007\|SETI@home\|Scheduler request succeeded Thu May 3 18:49:30 2007\|SETI@home\|No work from project Thu May 3 18:49:30 2007\|SETI@home\|Deferring scheduler requests for 9 minutes and 40 seconds Thu May 3 18:59:11 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 18:59:11 2007\|SETI@home\|Reason: To fetch work Thu May 3 18:59:11 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 19:01:11 2007\|\|Project communication failed: attempting access to reference site Thu May 3 19:01:12 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 19:01:16 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 19:01:16 2007\|SETI@home\|Deferring scheduler requests for 2 hours, 17 minutes and 55 seconds Thu May 3 20:04:21 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 20:04:21 2007\|SETI@home\|Reason: Requested by user Thu May 3 20:04:21 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 20:05:16 2007\|SETI@home\|Scheduler request succeeded Thu May 3 20:05:31 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 20:05:31 2007\|SETI@home\|Reason: To fetch work Thu May 3 20:05:31 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 20:07:31 2007\|\|Project communication failed: attempting access to reference site Thu May 3 20:07:32 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 20:07:36 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 20:07:36 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 20:08:36 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 20:08:36 2007\|SETI@home\|Reason: Requested by user Thu May 3 20:08:36 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 20:10:36 2007\|\|Project communication failed: attempting access to reference site Thu May 3 20:10:37 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 20:10:41 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 20:10:41 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 20:11:41 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 20:11:41 2007\|SETI@home\|Reason: Requested by user Thu May 3 20:11:41 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 20:13:41 2007\|\|Project communication failed: attempting access to reference site Thu May 3 20:13:42 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 20:13:46 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 20:13:46 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 20:14:46 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 20:14:46 2007\|SETI@home\|Reason: Requested by user Thu May 3 20:14:46 2007\|SETI@home\|Requesting 17280 seconds of new work Thu May 3 20:16:46 2007\|\|Project communication failed: attempting access to reference site Thu May 3 20:16:47 2007\|\|Access to reference site succeeded - project servers may be temporarily down. Thu May 3 20:16:51 2007\|SETI@home\|Scheduler request failed: a timeout was reached Thu May 3 20:16:51 2007\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds Thu May 3 20:17:51 2007\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Thu May 3 20:17:51 2007\|SETI@home\|Reason: Requested by user Thu May 3 20:17:51 2007\|SETI@home\|Requesting 17280 seconds of new work ID: 558971 ·

Misfit Volunteer tester Send message Joined: 21 Jun 01 Posts: 21804 Credit: 2,815,091 RAC: 0	Message 558975 - Posted: 4 May 2007, 3:31:27 UTC - in response to Message 558971. I know there were some server issues over the last couple of days but I was wondering if the problem I'm having is related to that. In a word, yes. me@rescam.org ID: 558975 ·

Geek@Play Volunteer tester Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0	Message 558992 - Posted: 4 May 2007, 3:55:24 UTC There IS something you can do to help Seti!!! While your waiting for work to appear go to donate and give Seti a boost in the financial department. With enough donations Seti could go out and purchase the modern server equipment we all want them to have. Who knows......it may be your dollar that keeps Seti online for another year. Boinc....Boinc....Boinc....Boinc.... ID: 558992 ·

Pappa Volunteer tester Send message Joined: 9 Jan 00 Posts: 2562 Credit: 12,301,681 RAC: 0	Message 559003 - Posted: 4 May 2007, 4:04:24 UTC - in response to Message 558992. I have to add to this, it could be Your Dollar Donated to Seti that Finds ET! There IS something you can do to help Seti!!! While your waiting for work to appear go to donate and give Seti a boost in the financial department. With enough donations Seti could go out and purchase the modern server equipment we all want them to have. Who knows......it may be your dollar that keeps Seti online for another year. Please consider a Donation to the Seti Project. ID: 559003 ·

Dirk and LoriEllen Send message Joined: 13 Feb 07 Posts: 27 Credit: 27,573 RAC: 0	Message 559004 - Posted: 4 May 2007, 4:08:09 UTC 4/05/2007 2:05:16 PM\|\|Starting BOINC client version 5.2.13 for windows_intelx86 4/05/2007 2:05:16 PM\|\|libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3 4/05/2007 2:05:16 PM\|\|Data directory: C:\\Program Files\\BOINC 4/05/2007 2:05:16 PM\|\|Processor: 1 GenuineIntel Intel(R) Celeron(R) D CPU 3.20GHz 4/05/2007 2:05:16 PM\|\|Memory: 447.36 MB physical, 1.03 GB virtual 4/05/2007 2:05:16 PM\|\|Disk: 68.26 GB total, 59.67 GB free 4/05/2007 2:05:16 PM\|SETI@home\|Computer ID: 3243427; location: ; project prefs: default 4/05/2007 2:05:16 PM\|\|General prefs: from SETI@home (last modified 2007-05-03 02:34:05) 4/05/2007 2:05:16 PM\|\|General prefs: using your defaults 4/05/2007 2:05:17 PM\|\|Remote control not allowed; using loopback address 4/05/2007 2:05:17 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 4/05/2007 2:05:17 PM\|SETI@home\|Reason: To fetch work 4/05/2007 2:05:17 PM\|SETI@home\|Requesting 86400 seconds of new work 4/05/2007 2:05:38 PM\|\|request_reschedule_cpus: project op 4/05/2007 2:05:40 PM\|\|Couldn't connect to hostname [setiboinc.ssl.berkeley.edu] 4/05/2007 2:05:43 PM\|SETI@home\|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106 4/05/2007 2:05:43 PM\|SETI@home\|No schedulers responded This is the view from Redcliffe Queensland Australia 2:07PM local time. ID: 559004 ·

Misfit Volunteer tester Send message Joined: 21 Jun 01 Posts: 21804 Credit: 2,815,091 RAC: 0	Message 559006 - Posted: 4 May 2007, 4:09:13 UTC - in response to Message 559003. I have to add to this, it could be Your Dollar Donated to Seti that Finds ET! And here I was hoping it would be my CPU. ;) me@rescam.org ID: 559006 ·

Pappa Volunteer tester Send message Joined: 9 Jan 00 Posts: 2562 Credit: 12,301,681 RAC: 0	Message 559018 - Posted: 4 May 2007, 4:22:28 UTC - in response to Message 559006. Misfit I recently responded to the Tech News Forum, about those that want to be EXHALTED... So with things that have happened this week at Seti to see someone make those statements... I am a bit Miffed... So at this point getting the Server that does Real Time Persistency Checking is Job #1... I fills the answers that we do not have... I see that Kevin is doing with MultiBeam even More Science... No I do not know taht it is funded that would support Seti that collected the data... Right now, Thumper is Dead! "we" are in a waiting pattern... Regards Pappa I have to add to this, it could be Your Dollar Donated to Seti that Finds ET! And here I was hoping it would be my CPU. ;) Please consider a Donation to the Seti Project. ID: 559018 ·

MrGray Send message Joined: 17 Aug 05 Posts: 3170 Credit: 60,411 RAC: 0	Message 559168 - Posted: 4 May 2007, 9:07:36 UTC Last modified: 4 May 2007, 9:08:56 UTC What kind of Sun processor do you need? I used to work for a Sun VAR in Silicon Valley. I can see if they want to donate one/some. "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss ID: 559168 ·

NewtonianRefractor Volunteer tester Send message Joined: 19 Sep 04 Posts: 495 Credit: 225,412 RAC: 0	Message 559329 - Posted: 4 May 2007, 15:43:42 UTC - in response to Message 559168. What kind of Sun processor do you need? I used to work for a Sun VAR in Silicon Valley. I can see if they want to donate one/some. I have no real knowlege of servers, but what is the advantage of Sun's microprocessors, in performance, versus something like the quad core xeon? ID: 559329 ·

nairb Send message Joined: 18 Mar 03 Posts: 201 Credit: 5,447,501 RAC: 5	Message 559342 - Posted: 4 May 2007, 16:09:31 UTC Just a question on reporting w/u. I have not been able to report w/u for 4 or 5 days. So does anybody know if its not possible at the moment to report w/u or is it just very hit and miss. If its not possible then I will stop trying until all is fixed. thanks Nairb ID: 559342 ·

CAPTAIN FUTURE Send message Joined: 22 Dec 06 Posts: 184 Credit: 0 RAC: 0	Message 559352 - Posted: 4 May 2007, 16:26:29 UTC - in response to Message 559342. Just a question on reporting w/u. I have not been able to report w/u for 4 or 5 days. So does anybody know if its not possible at the moment to report w/u or is it just very hit and miss. If its not possible then I will stop trying until all is fixed. thanks Nairb I can upload all the time... But reporting maybe only one/two times a day (with 24h network-connection) ID: 559352 ·

zoom3+1=4 Volunteer tester Send message Joined: 30 Nov 03 Posts: 65745 Credit: 55,293,173 RAC: 49	Message 559356 - Posted: 4 May 2007, 16:31:44 UTC - in response to Message 559342. Just a question on reporting w/u. I have not been able to report w/u for 4 or 5 days. So does anybody know if its not possible at the moment to report w/u or is it just very hit and miss. If its not possible then I will stop trying until all is fixed. thanks Nairb It's very hard to report as there is a lot of PCs still requesting New Work that should be set to "No New Tasks" that aren't and so It makes It nearly impossible to report any results. It can be done, It's just something that requires a lot of persistence at right now and I'm waiting for each PCs work to run out before I try and report right now(As each PC runs dry, I will try and report Its WU's, I have only 3 PCs to do out of 4, 1 has been fully reported to Seti, In less than 4 hours another one will be ready to report and then one in about 15 hours and then the last in 18 hours or so). The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's ID: 559356 ·

Heflin Send message Joined: 22 Sep 99 Posts: 81 Credit: 640,242 RAC: 0	Message 559362 - Posted: 4 May 2007, 16:43:01 UTC - in response to Message 558861. Great, now I'm going to have to attach to einstein@home, the Anti-seti@home. Looks for the complete oppostie signal if I understand the write up correctly... [/smile on] if both seti & einstein are running at the same time, is that equivalent to having the machine powered off? [/roll_eyes on] I had already taken advantage of the beauty of BOINC ... attached to more than ONE project with drastically different 'Resource Shares' When the 100 share project (seti) has nothing, the 10 share project picks up the slack, then the 1 share project is secondary backup. And I make use of the 'location' of machine [work, school, home] so different machines have different project share orders. My machines go along happily without me, without intervention, so I can be lazy! ;) SETI@home since 1999 "Set it, and Forget it!" ID: 559362 ·

Martin Johnson Send message Joined: 9 Jun 01 Posts: 201 Credit: 224,995 RAC: 0	Message 559364 - Posted: 4 May 2007, 16:46:05 UTC MrGray, If you look on the server status page, down near the bottom, it tels us that Thumper (the dead one) is a SunFire X4500. I have seen in another thread that these are priced at $25,000 in an anniversary sale, normal price just under $50,000. ID: 559364 ·

n5xmt Send message Joined: 7 Mar 07 Posts: 3 Credit: 136,625 RAC: 0	Message 559398 - Posted: 4 May 2007, 17:46:57 UTC - in response to Message 559372. MrGray, If you look on the server status page, down near the bottom, it tels us that Thumper (the dead one) is a SunFire X4500. I have seen in another thread that these are priced at $25,000 in an anniversary sale, normal price just under $50,000. http://www.sun.com/servers/x64/x4500/ Wonder what the price is of an IBM x366 server? Just installed one here at work with RHEL3, 4 Dual core 3.6GHz Xeons, 8G ram and 4 136G SCSI drives on the internal ServeRaid controller... that is one SMOKING fast machine! ID: 559398 ·

MrGray Send message Joined: 17 Aug 05 Posts: 3170 Credit: 60,411 RAC: 0	Message 559400 - Posted: 4 May 2007, 17:49:25 UTC Last modified: 4 May 2007, 18:24:53 UTC Ok, I'll give them a call. I'm sure they could use the tax write-off. Well... they apparently sold out to some company that doesn't seem to be doing anything with it at the moment. I called the old owners and they are in France for the summer, but I left a message. Can someone with access and knowledge email me the exact components needed so I know what to say when they call me back? . "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss ID: 559400 ·

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