To me it appears the AP Splitter failures locked GeorgeM communicating with the AP Science database, halting the other processes along with it.

---

I'm having problems downloading, too. For one computer I shut it down earlier today, booted back up, and I'm still unable to download.

---

Seti@home classic: 1,456 results, 1.613 years CPU time

I'm having problems downloading, too. For one computer I shut it down earlier today, booted back up, and I'm still unable to download.

I am also having trouble with downloading. I have a large queue in my tranfer tab but no action.

Fri 08 Feb 2019 09:13:56 AM CST | SETI@home | Temporarily failed download of 12dc06af.24372.176616.8.35.126: transient HTTP error
Fri 08 Feb 2019 09:13:56 AM CST | SETI@home | Backing off 00:08:23 on download of 12dc06af.24372.176616.8.35.126
Fri 08 Feb 2019 09:13:56 AM CST | SETI@home | Temporarily failed download of blc21_2bit_guppi_58406_31368_HIP21036_0116.32751.0.22.45.254.vlar: transient HTTP error
Fri 08 Feb 2019 09:13:56 AM CST | SETI@home | Backing off 00:10:37 on download of blc21_2bit_guppi_58406_31368_HIP21036_0116.32751.0.22.45.254.vlar
Fri 08 Feb 2019 09:13:58 AM CST |  | Internet access OK - project servers may be temporarily down.

Is what I am seeing.

Tom

---

A proud member of the OFA (Old Farts Association).

Nobody is able to download right now.
I have sent word to both Eric and Jeff.
Don't know if either is available yet.

Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Hello everyone,
The solution explained a long time ago should help ???
https://setiathome.berkeley.edu/forum_user_posts.php?userid=683206&offset=20
To make short : adding manually the IP adress in the host file.
Are the next adresses still valid ?

That workround is ONLY useful when there's a DNS failure, resulting in the message "can't resolve hostname" in the Event Log.

This breakdown is different, so please don't mess with the hosts file.

Hello Richard,
Thank you for answer.
But If I good remember a (very) long time ago, you published this add in host file.
And If I good remember, it worked.
But very long time ago, perhaps 10 (ten) years ago. All can fully change.
So I have reset the original host file.
By the way, the change in host file, not solve the problem. Amways "transient error"

---

Just got word back from Jeff.
He is on the case.

Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

No problems at all here. I just shut down my computer, and all download problems went away.
It works like magic, I tell you.....

What happy you are !
What is your secret ?
I also did the same, but ....no !!!
Have a nice day, evening, crunching, Wizard of SETI.
Perhaps the Aliens known you have THE wu, THE wu with a real wow signal.
And they (the aliens) want the wu be crunched as soon as possible.
Joke of course.

---

Thanks Mark.

So we just sit back until Jeff's large boot gets the server(s) going again.
[leans back and sips coffee]

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Thanks Mark.

So we just sit back until Jeff's large boot gets the server(s) going again.
[leans back and sips coffee]

You are welcome.
I am just glad I when I am able to get through to somebody.
I am sure he'll get it kick started again, even if he has to take things down to reboot with his large kicking boots.

Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

By the way, the change in host file, not solve the problem. Always "transient error"

Yes, that's the problem. You have to work out WHICH transient error. My workround (yes, I remember, it was me) works for DNS failures ONLY. This one is a "Failed to connect: Timed out". They're different. They need different workrounds. And I don't know any workround for this type of problem.

And I don't know any workround for this type of problem.

That was true when I wrote it.

Since then I've thought of a workround, tested it, and got two empty components of my central heating back into action. Yay!

But I'm not going to share it now, because:

1) Jeff is already on the case
2) I got a significant number of errors on the downloads
3) The scheduler is now down for maintenance.

So I'll leave Jeff in peace to finish the job. But I'll keep the workround in mind for next time downloads fail at a less convenient time of the week.

But I'll keep the workround in mind for next time downloads fail at a less convenient time of the week.

It must be approaching pubo'clock

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

+1 Kittyman

Here is the official explanation of the problem, as quoted, from Eric.

"A rarely used machine hung last night, and georgem was mounting one of its drives which led to georgem partially hanging. It'll take a couple of reboots and some directory reconfiguration to fix."

So, we might be having some hiccups for a while, but the fix is in the works.
Thank you, Eric.

Meowmeowmeow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

+2 for Kittyman.

It is easier for a server if one host wants 100Wus , the ID gets cached in the server and serves it faster than if 100 hosts wants one WU. Is certainly more related to aging harddrives etc that "stalls" the server but doesn't report that it got bad blocks, only delays talking to it. If one hdd in a array starts to buckle, the whole array that it belongs to makes it throughput and responsetime just take a big nosedive.

---

_________________________________________________________________________
Addicted to SETI crunching!
Founder of GPU Users Group

i can't think of anyone here running their systems in a data center.

I can. Fortunately the real work for their shiny new cluster arrived before they overtook me as first in country. :-)

---

i can't think of anyone here running their systems in a data center.

I can. Fortunately the real work for their shiny new cluster arrived before they overtook me as first in country. :-)

Well, if anybody would like to contribute a data center budget to the Seti project, I for sure would like to hear about it.
Upgrades could happen very quickly.

Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

say you banned everyone in the top 10 in terms of RAC. that only accounts for 7.5% of the world wide RAC on SETI. it wouldn't reduce the load on the project servers that much. the effect of millions of users requesting work FAR outweighs the few people with high RAC.

There aren't millions of active users on SETI. There are millions of registered users, or rather 1,759.531 registered users, but only as of now around 94000 active users.

I think the 'millions of users' was a rhetorical argument to make the point that your argument of a few high demand users was off the mark.

Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

High output machines are a blessing not a curse IMO, let's stop bickering and crunch on.

---

The replies to my post strengthens the arguments even more.
I guess SETI has become an addiction of the RAC kind for some..
I wonder if there is a 12 step program to cure that?
Thanks for confirming that I was right. (buy Porsches instead) :-)

Keep it up. If you must.
You will notice, if you look a bit, that I am running much less hardware than I used to.
Simply due to the cost.
I still will reach a billion credits in the not too distant future.
But my RAC is not what it used to be.
And you would still lead others to believe that productive users contribute to problems with the servers?
I don't think many are listening to your arguments anymore.
If it still pleases you to continue, have at it.
Most of us know your logic falls very short of the truth.

As you were, carry on.

Meow.

---

"Time is simply the mechanism that keeps everything from happening all at once."