good day to you all,
new computer with win 7 pro x64, for the 1st time attached via Account manager,
next project correctly attached and running with WU:
- Collatz
- Enigma
- CPDN
- Ibercivis
two projects attached:
but computer not inserted in database and not started with work ?????????????????
Quote
64 http://milkyway.cs.rpi.edu/milkyway/ 24-06-2010 17:13:11 update requested by user
65 http://milkyway.cs.rpi.edu/milkyway/ 24-06-2010 17:13:13 Fetching scheduler list
66 http://setiathome.berkeley.edu/ 24-06-2010 17:13:19 update requested by user
67 http://setiathome.berkeley.edu/ 24-06-2010 17:13:20 Sending scheduler request: Requested by user.
68 http://setiathome.berkeley.edu/ 24-06-2010 17:13:20 Requesting new tasks for CPU and GPU
69 24-06-2010 17:13:42 Project communication failed: attempting access to reference site
70 http://setiathome.berkeley.edu/ 24-06-2010 17:13:42 Scheduler request failed: Couldn't connect to server
71 24-06-2010 17:13:44 Internet access OK - project servers may be temporarily down.
and no way to start the computer with these two projects, everything done, attach manually, etc. :'( :'( :'( :'(
Quote from: Corsair on June 24, 2010, 03:24:52 PM
good day to you all,
new computer with win 7 pro x64, for the 1st time attached via Account manager,
next project correctly attached and running with WU:
- Collatz
- Enigma
- CPDN
- Ibercivis
two projects attached:
but computer not inserted in database and not started with work ?????????????????
Quote
64 http://milkyway.cs.rpi.edu/milkyway/ 24-06-2010 17:13:11 update requested by user
65 http://milkyway.cs.rpi.edu/milkyway/ 24-06-2010 17:13:13 Fetching scheduler list
66 http://setiathome.berkeley.edu/ 24-06-2010 17:13:19 update requested by user
67 http://setiathome.berkeley.edu/ 24-06-2010 17:13:20 Sending scheduler request: Requested by user.
68 http://setiathome.berkeley.edu/ 24-06-2010 17:13:20 Requesting new tasks for CPU and GPU
69 24-06-2010 17:13:42 Project communication failed: attempting access to reference site
70 http://setiathome.berkeley.edu/ 24-06-2010 17:13:42 Scheduler request failed: Couldn't connect to server
71 24-06-2010 17:13:44 Internet access OK - project servers may be temporarily down.
and no way to start the computer with these two projects, everything done, attach manually, etc. :'( :'( :'( :'(
I don't know what's going on with Milkyway, but Seti's servers are definitely down, have been so for over 12 hours ;)
Quote from: jjwhalen on June 24, 2010, 03:49:52 PM
I don't know what's going on with Milkyway, but Seti's servers are definitely down, have been so for over 12 hours ;)
thanks, this has been for the last 36 hours, it's too long to get the computer ID for start crunching. ;)
Quote from: Corsair on June 24, 2010, 04:01:52 PM
Quote from: jjwhalen on June 24, 2010, 03:49:52 PM
I don't know what's going on with Milkyway, but Seti's servers are definitely down, have been so for over 12 hours ;)
thanks, this has been for the last 36 hours, it's too long to get the computer ID for start crunching. ;)
SETI has some problems. ;D But should be going any moment. Make sure you set up an adequate work buffer, so you don't run out of work.
Quote from: fred on June 24, 2010, 04:06:12 PM
Quote from: Corsair on June 24, 2010, 04:01:52 PM
Quote from: jjwhalen on June 24, 2010, 03:49:52 PM
I don't know what's going on with Milkyway, but Seti's servers are definitely down, have been so for over 12 hours ;)
thanks, this has been for the last 36 hours, it's too long to get the computer ID for start crunching. ;)
SETI has some problems. ;D But should be going any moment. Make sure you set up an adequate work buffer, so you don't run out of work.
Seti has long been a victim of its own success...it's a tribute to the dedicated staff at Berkeley that they have as as much uptime as they do.
Quote from: jjwhalen on June 24, 2010, 05:18:25 PM
Quote from: fred on June 24, 2010, 04:06:12 PM
Quote from: Corsair on June 24, 2010, 04:01:52 PM
Quote from: jjwhalen on June 24, 2010, 03:49:52 PM
I don't know what's going on with Milkyway, but Seti's servers are definitely down, have been so for over 12 hours ;)
thanks, this has been for the last 36 hours, it's too long to get the computer ID for start crunching. ;)
SETI has some problems. ;D But should be going any moment. Make sure you set up an adequate work buffer, so you don't run out of work.
At last attached the new computer to both projects, more than 48 hours for SETI and near 72 hours for Milkyway :)
Seti has long been a victim of its own success...it's a tribute to the dedicated staff at Berkeley that they have as as much uptime as they do.
Quote from: Corsair on June 25, 2010, 12:21:21 PM
Quote from: jjwhalen on June 24, 2010, 05:18:25 PM
Quote from: fred on June 24, 2010, 04:06:12 PM
Quote from: Corsair on June 24, 2010, 04:01:52 PM
Quote from: jjwhalen on June 24, 2010, 03:49:52 PM
I don't know what's going on with Milkyway, but Seti's servers are definitely down, have been so for over 12 hours ;)
thanks, this has been for the last 36 hours, it's too long to get the computer ID for start crunching. ;)
SETI has some problems. ;D But should be going any moment. Make sure you set up an adequate work buffer, so you don't run out of work.
At last attached the new computer to both projects, more than 48 hours for SETI and near 72 hours for Milkyway :)
Seti has long been a victim of its own success...it's a tribute to the dedicated staff at Berkeley that they have as as much uptime as they do.
Good news! However, note this quote from Matt Lebofsky in Seti's News thread:
QuoteStarting next week our servers will be turned off for several days a week - initially, Tuesday through Thursday. This will allow us to devote more time to scientific development.
Doubly important to bump up that work buffer ;)
Quote from: jjwhalen on June 25, 2010, 04:31:55 PM
Good news! However, note this quote from Matt Lebofsky in Seti's News thread: QuoteStarting next week our servers will be turned off for several days a week - initially, Tuesday through Thursday. This will allow us to devote more time to scientific development.
Doubly important to bump up that work buffer ;)
The bad news: They made another programming error with the WU distribution, causing -177 errors and cuda tasks that report a expected run time of 4 days. ;D And AP, that normally runs within a day, reporting 3 digits (357 days) run time. ;D
This should correct itself after a couple of 100+ WU.
So be warned if you use the <flops> statement, remove it at once.