Questions and Answers :
Windows :
UPLOAD/DOWNLOAD Seems working now...
Message board moderation
Author | Message |
---|---|
Misfit Send message Joined: 21 Jun 01 Posts: 21804 Credit: 2,815,091 RAC: 0 |
|
Fuzzy Hollynoodles Send message Joined: 3 Apr 99 Posts: 9659 Credit: 251,998 RAC: 0 |
Thumper (the master science database server) has been replaced and is up and running again. There are huge problems with upload/download most probably because the servers are being clobbered with requests. So please have patience. And please let your BOINC manager(s) do what they are made to, to contact when it's time. Please don't hit the Update button, your uploads/downloads will get through eventually. Thank you. "I'm trying to maintain a shred of dignity in this world." - Me |
Roy Wall (shiny sides) Send message Joined: 8 Nov 99 Posts: 5 Credit: 5,099,610 RAC: 0 |
Thumper (the master science database server) has been replaced and is up and running again. Fuzzy, I got a new WU this morning but BOINC says it is still idle any suggests? Thanks. |
DarkRyder Send message Joined: 10 Sep 01 Posts: 5 Credit: 25,554,963 RAC: 27 |
i've maybe gotten like 5 WU's since monday on all of my machines. Mostly i have a bunch of WU's in my Transfer tab that can neither send nor receive. |
dad10090 Send message Joined: 14 Apr 06 Posts: 3 Credit: 56,339 RAC: 0 |
Thumper (the master science database server) has been replaced and is up and running again. Thanks for the info! do you have any estimates re: how long we can expect it to take to 'get through'? I've not been able to get any response from the server (both seti@home and seti@home beta test) for ~2 weeka now. Thank you Don dad10090@bresnan.net |
Polarit Send message Joined: 21 Jun 06 Posts: 1 Credit: 72,878 RAC: 0 |
Me neither, no WU for ~14 days |
Aurora Borealis Send message Joined: 14 Jan 01 Posts: 3075 Credit: 5,631,463 RAC: 0 |
Estimate Things will continue to be hit and miss until they aren't. |
Rndmacts Send message Joined: 18 Aug 99 Posts: 4 Credit: 122,806 RAC: 0 |
I was having the same problem of sending or recieving work units, finally figured it would not hurt and reboot system that runs SETI. BOINC started up and qued WUs uploaded and new work recieved and processing. Sometimes the simplest solution is the easiest. Can a whisper be heard across the universe? |
Tomsz Send message Joined: 25 Aug 00 Posts: 6 Credit: 73,770,232 RAC: 0 |
I am not getting any work from the server on many of my SETI clients. I see the message: "Scheduler request failed: HTTP internal server error" Stopping and starting BOINC has no effect. Rebooting the PC also has no effect. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13736 Credit: 208,696,464 RAC: 304 |
I am not getting any work from the server on many of my SETI clients. I see the message: Since your computers are hidden i'm just guessing- you're running an enhanced application. There is a work around in the Number Crunching forum, "Ghost Work units" (and some other stuff) thread. Grant Darwin NT |
B1ackBoX Send message Joined: 31 May 03 Posts: 2 Credit: 25,362,057 RAC: 0 |
I've got a few computers running S@H, only the slowest of them have managed to get work units after the Thumper came back online. The others just gives me this message in BIONC's message window: 19.05.2007 15:28:16|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 19.05.2007 15:28:16|SETI@home|No schedulers responded is this response related to the overwhelming amounts of requests the servers are getting? |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13736 Credit: 208,696,464 RAC: 304 |
is this response related to the overwhelming amounts of requests the servers are getting? That & the fact there are some bottlenecks that have developed as the result of some recent changes. End result- even more load on the servers for an even longer period of tiume than there would normally be. Grant Darwin NT |
derbewahrer Send message Joined: 4 Jan 02 Posts: 3 Credit: 1,018,441 RAC: 41 |
I dont no ive been right here but i will write it On three of my PCs i became no workunits only : 22.05.2007 11:28:40|SETI@home|Requesting 414892 seconds of new work 22.05.2007 11:28:45|SETI@home|Scheduler request failed: HTTP internal server error 22.05.2007 11:28:45|SETI@home|Deferring communication for 38 min 46 sec 22.05.2007 11:28:45|SETI@home|Reason: scheduler request failed If i look in my Account about seti "your computers" there are staying for my 3 PCs over 10 new Wus sending to my PCs, but on my PCs is nothing, no WUs ?? If you have an answer about this ?? Sorry for my bad english, but i hope you all understand it ;-) greatings derbewahrer |
vandellia Send message Joined: 18 Dec 05 Posts: 6 Credit: 48,200 RAC: 0 |
http://setiathome.berkeley.edu/forum_thread.php?id=39219&nowrap=true#558553 5/14/2007 10:25:18 PM||Starting BOINC client version 5.4.11 for windows_intelx86 5/14/2007 10:25:18 PM||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3 5/14/2007 10:25:18 PM||Data directory: C:\\Program Files\\BOINC 5/14/2007 10:25:18 PM||Processor: 1 AuthenticAMD AMD Athlon(tm) 64 Processor 3200+ 5/14/2007 10:25:18 PM||Memory: 2.00 GB physical, 2.60 GB virtual 5/14/2007 10:25:18 PM||Disk: 37.26 GB total, 6.22 GB free 5/14/2007 10:25:19 PM|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 2017259; location: home; project prefs: default 5/14/2007 10:25:19 PM||General prefs: from SETI@home (last modified 2006-10-08 19:25:29) 5/14/2007 10:25:19 PM||General prefs: using separate prefs for home 5/14/2007 10:25:19 PM||Local control only allowed 5/14/2007 10:25:19 PM||Listening on port 31416 5/14/2007 10:35:37 PM|SETI@home|Started download of file 18fe05aa.26345.14400.34650.3.27 5/14/2007 10:35:52 PM||Project communication failed: attempting access to reference site 5/14/2007 10:35:53 PM|SETI@home|Temporarily failed download of 18fe05aa.26345.14400.34650.3.27: http error 5/14/2007 10:35:53 PM|SETI@home|Backing off 1 hours, 25 minutes and 11 seconds on download of file 18fe05aa.26345.14400.34650.3.27 5/14/2007 10:36:12 PM||Access to reference site failed - check network connection or proxy configuration. 5/15/2007 12:01:06 AM|SETI@home|Started download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 12:01:28 AM|SETI@home|Temporarily failed download of 18fe05aa.26345.14400.34650.3.27: http error 5/15/2007 12:01:28 AM|SETI@home|Backing off 50 minutes and 47 seconds on download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 12:52:16 AM|SETI@home|Started download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 12:52:38 AM|SETI@home|Temporarily failed download of 18fe05aa.26345.14400.34650.3.27: http error 5/15/2007 12:52:38 AM|SETI@home|Backing off 1 hours, 17 minutes and 3 seconds on download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 1:32:09 AM|SETI@home|Started download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 1:33:43 AM|SETI@home|Temporarily failed download of 18fe05aa.26345.14400.34650.3.27: http error 5/15/2007 1:33:43 AM|SETI@home|Backing off 3 hours, 12 minutes and 2 seconds on download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 1:35:08 AM|SETI@home|Started download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 1:35:31 AM|SETI@home|Temporarily failed download of 18fe05aa.26345.14400.34650.3.27: http error 5/15/2007 1:35:31 AM|SETI@home|Backing off 3 hours, 33 minutes and 16 seconds on download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 1:35:57 AM|SETI@home|Started download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 1:36:13 AM|SETI@home|Finished download of file 18fe05aa.26345.14400.34650.3.27 5/15/2007 1:36:13 AM|SETI@home|Throughput 23678 bytes/sec 5/15/2007 1:36:14 AM||Rescheduling CPU: files downloaded 5/15/2007 1:36:14 AM|SETI@home|Starting task 18fe05aa.26345.14400.34650.3.27_2 using setiathome_enhanced version 515 5/15/2007 4:37:13 PM|SETI@home|Task 18fe05aa.26345.14400.34650.3.27_2 exited with zero status but no 'finished' file 5/15/2007 4:37:13 PM|SETI@home|If this happens repeatedly you may need to reset the project. 5/15/2007 4:37:13 PM||Rescheduling CPU: application exited 5/15/2007 4:37:19 PM|SETI@home|Restarting task 18fe05aa.26345.14400.34650.3.27_2 using setiathome_enhanced version 515 5/17/2007 9:27:40 PM||Suspending computation - running CPU benchmarks 5/17/2007 9:27:40 PM|SETI@home|Pausing task 18fe05aa.26345.14400.34650.3.27_2 (removed from memory) 5/17/2007 9:27:40 PM||Suspending network activity - running CPU benchmarks 5/17/2007 9:27:43 PM||Running CPU benchmarks 5/17/2007 9:28:38 PM||Failed to stop applications; aborting CPU benchmarks 5/17/2007 9:28:39 PM||Resuming computation 5/17/2007 9:28:39 PM||Rescheduling CPU: Resuming computation 5/17/2007 9:28:39 PM||Resuming network activity 5/19/2007 4:28:49 AM||Using earliest-deadline-first scheduling because computer is overcommitted. thjis is what ive been seeing for days |
CElliott Send message Joined: 19 Jul 99 Posts: 178 Credit: 79,285,961 RAC: 0 |
Communicating with the Beta site worked on 3 of 4 computers. Here are the relevant messages from the computer on which communication did not work: 5/24/2007 11:17:52 AM|SETI@home Beta Test|Sending scheduler request: Requested by user 5/24/2007 11:17:52 AM|SETI@home Beta Test|Requesting 243648 seconds of new work, and reporting 35 completed tasks 5/24/2007 11:21:04 AM||Project communication failed: attempting access to reference site 5/24/2007 11:21:05 AM||Access to reference site succeeded - project servers may be temporarily down. 5/24/2007 11:21:05 AM|SETI@home Beta Test|Scheduler request failed: failed sending data to the peer 5/24/2007 11:21:05 AM|SETI@home Beta Test|Deferring communication for 6 min 13 sec 5/24/2007 11:21:05 AM|SETI@home Beta Test|Reason: scheduler request failed 5/24/2007 11:27:04 AM|SETI@home Beta Test|Sending scheduler request: Requested by user 5/24/2007 11:27:04 AM|SETI@home Beta Test|Requesting 243648 seconds of new work, and reporting 35 completed tasks 5/24/2007 11:32:10 AM||Project communication failed: attempting access to reference site 5/24/2007 11:32:11 AM||Access to reference site succeeded - project servers may be temporarily down. 5/24/2007 11:32:14 AM|SETI@home Beta Test|Scheduler request failed: a timeout was reached 5/24/2007 11:32:14 AM|SETI@home Beta Test|Deferring communication for 11 min 25 sec 5/24/2007 11:32:14 AM|SETI@home Beta Test|Reason: scheduler request failed |
CElliott Send message Joined: 19 Jul 99 Posts: 178 Credit: 79,285,961 RAC: 0 |
Tried it again, and it worked. Communicating with the Beta site worked on 3 of 4 computers. Here are the relevant messages from the computer on which communication did not work: |
Fuzzy Hollynoodles Send message Joined: 3 Apr 99 Posts: 9659 Credit: 251,998 RAC: 0 |
It seems WU's are flowing now, even with the Chicken app. I'll rename this thread and unsticky it. "I'm trying to maintain a shred of dignity in this world." - 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.