I now have 10 work files that I've finished but which are not being sent back to Seti@home. It either says "Sending" and nothing happens, or it says "try again".

In the messages section it says "Remote control not allowed, using loopback adress".
I don't see why it shouldn't be allowed to connect... I have modified my firewall so that the program has maximum access to the internet.

What can I try?

---

That message is normal unless you are monitoring a computer farm.
As for the upload problem it is related to this message

From the home Page.
----------
December 4, 2005
We are experiencing heavy traffic on our data server. This is preventing some workunit/core client downloads. We are working on the problem.
----------
The backlog created by the surge of new users is also affecting uploads. It may take as much as 24 hr for things to get back to normal.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

Hi,
The servers are overloaded at the moment due to a software failure yesterday.
It may take upto 24 hours more to completely clear, but don't worry BOINC will sort it out eventually.

This has nothing to do with "Remote Control Not Allowed". This is a feature that allows you to control BOINC on several computers from on BOINC Manager (or with BOINCView).

---

Hi,
The servers are overloaded at the moment due to a software failure yesterday.
It may take upto 24 hours more to completely clear, but don't worry BOINC will sort it out eventually.

This has nothing to do with "Remote Control Not Allowed". This is a feature that allows you to control BOINC on several computers from on BOINC Manager (or with BOINCView).

thanks for the help, i am experiencing the same thing. i have many work units from 5 computers waiting in limbo to be uploaded. i am, however, able to get new work units to crunch, just cant upload the ones that have finished

---

That message is normal unless you are monitoring a computer farm.
As for the upload problem it is related to this message

From the home Page.
----------
December 4, 2005
We are experiencing heavy traffic on our data server. This is preventing some workunit/core client downloads. We are working on the problem.
----------
The backlog created by the surge of new users is also affecting uploads. It may take as much as 24 hr for things to get back to normal.

Same as for me. I have lots of messages like:
2005-12-6 14:08:46||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
2005-12-6 14:08:46|SETI@home|Temporarily failed upload of 13au01aa.6597.16224.790882.87_2_0: system I/O
2005-12-6 14:14:24|SETI@home|Temporarily failed upload of 13au01aa.6597.16224.790882.87_2_0: error 500

---

That message is normal unless you are monitoring a computer farm.
As for the upload problem it is related to this message

From the home Page.
----------
December 4, 2005
We are experiencing heavy traffic on our data server. This is preventing some workunit/core client downloads. We are working on the problem.
----------
The backlog created by the surge of new users is also affecting uploads. It may take as much as 24 hr for things to get back to normal.

Same as for me. I have lots of messages like:
2005-12-6 14:08:46||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
2005-12-6 14:08:46|SETI@home|Temporarily failed upload of 13au01aa.6597.16224.790882.87_2_0: system I/O
2005-12-6 14:14:24|SETI@home|Temporarily failed upload of 13au01aa.6597.16224.790882.87_2_0: error 500

Latest news is at Technical News

---

yestarday i have problem with:

2005-12-06 09:43:54||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]

today its look like i can connect but i cannot upload my results:

2005-12-06 11:48:42|SETI@home|Started download of 15ap04aa.22158.32978.854828.136
2005-12-06 11:48:43|SETI@home|Temporarily failed download of 15ap04aa.22158.32978.854828.136: error 500

error 500:?
looks like server down. :/

---

yestarday i have problem with:

2005-12-06 09:43:54||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]

today its look like i can connect but i cannot upload my results:

2005-12-06 11:48:42|SETI@home|Started download of 15ap04aa.22158.32978.854828.136
2005-12-06 11:48:43|SETI@home|Temporarily failed download of 15ap04aa.22158.32978.854828.136: error 500

error 500:?
looks like server down. :/

---

Please read the front page news:

December 5, 2005
We are experiencing heavy traffic on our data server. This is preventing some result uploads/workunit downloads. We are working on the problem. More in Technical News.

See also Server Status.

---

I too have been experiencing the problem (Yes, I read the news page) for the last three days or so, but I have a different question. Before I saw the news posting I was doing a little digging to see if the problem was on my end (COX cable has had some problems in my area) and I saw something that raised a few question marks and little concern.

Everytime I hit 'retry' on the transfer, the server makes a connection to the IP 66.28.250.125 which does not resolve to anything in DNS. This machine is running Windows 2000.

More: I also run SETI@home on my Linux machine (which has had no problems uploading/downloading). In fact when I watched a transfer on the Linux box, it connected to galileo.ssl.berkeley.edu (128.32.18.73) and not 66.28.250.125

But this does not seem to jibe with the site information which seems to indicate that the uploads/downloads should be with kryten, not galileo.

So can someone tell me if 66.28.250.128 belongs to berkeley.edu? I do not have any luck with reverse queries so I need another source to confirm. It helps to know when t/s problems such as these.

Also (off-topic), is it documented somewhere how the each system is supposed to communicate with the servers?

---

66.28.250.125 is setiboincdata.ssl.berkeley.edu "kryten" this is the ul/dl server.

128.32.18.73 is setiboinc.ssl.berkeley.edu "galileo" used to be the ul/dl server, and they've been doing some moving around of gear and as the tech news reports have made dns changes. Read the "tech news" as linked from the front page.

tony

---

66.28.250.125 is setiboincdata.ssl.berkeley.edu "kryten" this is the ul/dl server.

128.32.18.73 is setiboinc.ssl.berkeley.edu "galileo" used to be the ul/dl server, and they've been doing some moving around of gear and as the tech news reports have made dns changes. Read the "tech news" as linked from the front page.

tony

I did read the tech news so I am aware of the equipment move but it did not answer my first question. Thank you for your reply which did.

---

How long time can finished work "sit" on my drive without being sent back?

Do they have an expiration date?
I have now 20 finished units and cant upload still :(

---

How long time can finished work "sit" on my drive without being sent back?

Do they have an expiration date?
I have now 20 finished units and cant upload still :(

They have a deadline which is 14 days after having been send.
This deadline can be seen when opening the manager, going to the tab "Work". There is a column named "report deadline".

That message is normal unless you are monitoring a computer farm.
As for the upload problem it is related to this message

From the home Page.
----------
December 4, 2005
We are experiencing heavy traffic on our data server. This is preventing some workunit/core client downloads. We are working on the problem.
----------
The backlog created by the surge of new users is also affecting uploads. It may take as much as 24 hr for things to get back to normal.

I also have the problem of not being able to upload my results to Seti. They are piling up.

---

I also have the problem of not being able to upload my results to Seti. They are piling up.

join the party, everyone is in the same boat.

---

I also have the problem of not being able to upload my results to Seti. They are piling up.

join the party, everyone is in the same boat.

I hope it's more of a ship than a boat! Mine are stacking up too!

---

That message is normal unless you are monitoring a computer farm.
As for the upload problem it is related to this message

From the home Page.
----------
December 4, 2005
We are experiencing heavy traffic on our data server. This is preventing some workunit/core client downloads. We are working on the problem.
----------
The backlog created by the surge of new users is also affecting uploads. It may take as much as 24 hr for things to get back to normal.

Same as for me. I have lots of messages like:
2005-12-6 14:08:46||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
2005-12-6 14:08:46|SETI@home|Temporarily failed upload of 13au01aa.6597.16224.790882.87_2_0: system I/O
2005-12-6 14:14:24|SETI@home|Temporarily failed upload of 13au01aa.6597.16224.790882.87_2_0: error 500

I have much of the same prob. Being new to this I'm glad I found this thread. Now I know it's not something wrong with my settings or I was doing something wrong. The one thing that has happened is the few work pieces that I did manage to upload I've recieved no credit for, plus my DL's are corrupted at the end. s this part of the outage I've read about?
ABB

---

I have much of the same prob. Being new to this I'm glad I found this thread. Now I know it's not something wrong with my settings or I was doing something wrong. The one thing that has happened is the few work pieces that I did manage to upload I've recieved no credit for, plus my DL's are corrupted at the end. s this part of the outage I've read about?
ABB

To make the ul/dl servers work better they shut down the back end servers, and while those are down they're taking the opportunity to merge the classic data with the Boinc data. It iw supposed to take several days, but they plan to start making new work after two days and that was yesterday. This merge was scheduled for November 15th, but the software or something different between the two databases was causing trouble so the put if off.

Since the back end is down there is no validator running, no validator, no credit. Once they turn it back on ALL the work should validate quickly and your credit should jump pretty good

thanks for you understanding

tony

---