Halp! BOINC can't connect?

[RoBorg]

My two Linux servers haven't sent any results back for a couple of days.
They've been working fine for months... I haven't changed anything (though that's not to say nobody else has changed anything...).

As far as I can tell, it's a network problem...
If I run

Code:

boinccmd --network_available

I get this in the log file:

Code:

01-Aug-2014 09:39:16 [---] Project communication failed: attempting access to reference site
01-Aug-2014 09:39:16 [rosetta@home] Scheduler request failed: Couldn't connect to server
01-Aug-2014 09:39:19 [---] Internet access OK - project servers may be temporarily down.

The rosatta@home sever status page reports everything ok, and other people seem to be submitting work ok, so it must be a problem at my end.

I'm not sure how to debug it... any ideas?

[RoBorg]

Argh, looks like my PC is having the same problem, so it may be the rosetta@home servers that are broken. Is anyone else having the same problem?

[PoNyePiC]

hmm.....I checked my rosetta software and noticed I had several things ready for upload, but nothing is uploading. Now, I'm really only familiar with the Folding@home software, but I do have rosetta running on my other computer. I never really got into the other projects, I just downloaded them, set them up, and ignored them. Good Luck.

[RoBorg]

Ah I just saw this on the site:

Jul 30, 2014
We are aware of significant network slow-down between the subnet upon which our servers sit and the Internet beyond the UW campus. We are working with the UW's Network Operations team to pinpoint the cause. We apologize for the frustration caused. -KEL

I guess that's it then. Would've been nice to see this on the Server Status page and their twitter...

[Sellyme]

I highly recommend running multiple projects to avoid your computers ever running dry if a single server goes down - you can set the resource share of the project you want (Rosetta) to 10,000, and then add 2-3 backup projects (theSkyNet POGS, NumberFields@Home, PrimeGrid, and NFS@Home are all reliable sources of CPU work) with 100 resource share - this will give you almost exclusively Rosetta WUs, but if Rosetta's servers die and can't send you work, it will default to the other projects.

If you'd prefer to run some other project instead of Rosetta as a primary the process is exactly the same, just change the resource share accordingly.

[RoBorg]

Yeah that's a good point. I had them all set to Rosetta for the last competition - probably time to update them

[SXRXE]

100 resource share - this will give you almost exclusively Rosetta WUs, but if Rosetta's servers die and can't send you work, it will default to the other projects.

0 resource share will give you complete exclusively to Rosetta WUs, but still receive work from other projects if Rosetta dies.