[Off Topic] Computer not attaching

[Corsair]

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:

• Milkyway
• Seti@home

but computer not inserted in database and not started with work ??

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.  

[jjwhalen]

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:

• Milkyway
• Seti@home

but computer not inserted in database and not started with work ??

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

[Corsair]

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. 

[fred]

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. But should be going any moment. Make sure you set up an adequate work buffer, so you don't run out of work.

[jjwhalen]

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

[Corsair]

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

[jjwhalen]

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

Starting 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

[fred]

Good news!  However, note this quote from Matt Lebofsky in Seti's News thread:

Starting 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. And AP, that normally runs within a day, reporting 3 digits (357 days) run time. 
This should correct itself after a couple of 100+ WU.
So be warned if you use the <flops> statement, remove it at once.