Try looking at who #28 is listed as belonging to, https://setiathome.berkeley.edu/top_hosts.php?sort_by=expavg_credit&offset=20
ID: 8682108
#28 Magne 171,989.52 8,889,326 7.8.3
GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz [Family 6 Model 60 Stepping 3] (8 processors)
NVIDIA GeForce GTX 1060 6GB (4095MB) driver: 418.43 OpenCL: 1.2
Linux Ubuntu Ubuntu 18.04.2 LTS [4.15.0-46-generic]

Now look at #8, https://setiathome.berkeley.edu/top_hosts.php
ID: 8690734
#8 Magne 363,269.95 18,080,802 7.4.44
GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz [Family 6 Model 60 Stepping 3] (8 processors)
[5] NVIDIA GeForce GTX 1060 6GB (4095MB) driver: 418.43
Linux 4.15.0-46-generic

Now note Magne only has One Linux Machine, https://setiathome.berkeley.edu/hosts_user.php?userid=118177
You should also note the RAC on his User page, Recent average credit 199,322.93
Most people would conclude it is the SAME machine.

You can also look at Juan's page and note the Credit; https://setiathome.berkeley.edu/show_user.php?userid=8606388
Total credit: 450,616,983
But when you look at his host, https://setiathome.berkeley.edu/hosts_user.php?userid=8606388
ID: 8662921: Total credit: 1,375,790,492
So, how does a Total of 450,616k translate to a Host of 1,375,790k?
Strange things around here...

Results received in last hour ** 0 1,478 146,664

The results received in the last hour is higher than our usual 120k. It is surprising to me that the number is higher than usual even with the high amount of AP results returned as well. Are we getting garbage WUs right now? or have more fast machines joined the cause?? I'm really happy that the seti system seems to be handling things well and that the replica is also keeping up.

. . I have had some large numbers of noise bombs so I am guessing it is the former ...

Stephen

<shrug>

Ah I see now. I had only clicked the links you provided and they showed different Owners.

But since stats on the second page haven’t updated yet that’s why it’s still there. (And shows anonymous when you actually click on it from the second page)

The anonymous setting must be what happens when a host gets deleted. I believe when this happened to Juan also, it deleted his old host too. I’m aware of the contradiction between Juan’s host and user stats. I posted about that some time ago in another thread.

Edit: found the old post where it was discussed previously.

https://setiathome.berkeley.edu/forum_thread.php?id=83833&postid=1978139#1978139

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

. . Aaahh! Here we go again, 24 hours (or so) to maintenance outage and the uploads are playing up .... :(

Stephen

:(

. . Aaahh! Here we go again, 24 hours (or so) to maintenance outage and the uploads are playing up .... :(

Stephen

:(

Just like a switch was flipped ...

---

. . Aaahh! Here we go again, 24 hours (or so) to maintenance outage and the uploads are playing up .... :(

Stephen

:(

Just like a switch was flipped ...

Mon 25 Mar 2019 08:32:57 AM CDT | SETI@home | Temporarily failed upload of blc23_2bit_guppi_58405_84300_HIP86137_0023.13785.818.21.44.234.vlar_0_r1167924088_0: transient HTTP error

Or maybe it is a "Friday issue". The servers get "congested" right before maintenance?

Tom

---

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

Hopeful that the elves in the lab notice the upload server is acting up and fix it today when they get in.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

For those of you who never bother to ask yourselves which transient error:

25/03/2019 14:17:58 | SETI@home | [http] [ID#3033] Info:  Failed to connect to setiboincdata.ssl.berkeley.edu port 80: Timed out

That's one we can't do anything about - don't mess with any files.

Up loads have started working again but it is a painful process.

---

i can mostly stay on top of my uploads on the 2 slower machines, but the beast is just too fast. uploads go slower than the machine can process the WUs. the the pending uploads is just growing and growing. this is with max file transfers set to it's max of 8.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

I'm also getting a lot of my uploads stuck at 100% while others timeout and just go into retry loops.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

PANIC! The ready to send queue is low, and people are having time out issues for a while, something is wrong!!

Can we tell if it is a Berkeley connection issue or a seti one?? is it a problem with the upload machine??

Time for someone to check the cables or kick the machine.

PANIC! The ready to send queue is low, and people are having time out issues for a while, something is wrong!!

Can we tell if it is a Berkeley connection issue or a seti one?? is it a problem with the upload machine??

Time for someone to check the cables or kick the machine.

Richard, already posted the issue is with the upload server.

25/03/2019 14:17:58 | SETI@home | [http] [ID#3033] Info: Failed to connect to setiboincdata.ssl.berkeley.edu port 80: Timed out

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Greetings,

I don't get it! WUs are at 100% progress and then go into resend mode. How the heck does THAT work? The only thing I can think of, which doesn't sound logical, is that the data was sent 100% from the host yet the recipient has not gotten it so the WU goes back into resend mode.

Have a nice day, if you can. ;)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Hi Siran.
From the technical side of the Internet, this most likely means either the receiver never sent the acknowledgement that the final packet in the file was received properly, or that the last packet was not received before the time limit was reached. Of course, there could be a number of reasons why the file was not received correctly or within the required time fame. That is most likely what someone is, or soon will be, researching at Berkeley.

I hope that they will find the problem quickly, and that the fix is easy to do.

I have found today that (if you have the time), going into the Transfer tab, selecting all the units trying to upload, then clicking the "Retry Now" button each time all have backed off, will get them completed within a few minutes of retrying. This only works when the cause of the failed updates is related to certain types of technical problems. Unfortunately, many times the issue at hand during one of these events will preclude the success of this retry procedure. Today, though, we are in luck, i.e., the retry6 does work.

I hope this helps.

Hi Siran.
From the technical side of the Internet, this most likely means either the receiver never sent the acknowledgement that the final packet in the file was received properly, or that the last packet was not received before the time limit was reached. Of course, there could be a number of reasons why the file was not received correctly or within the required time fame. That is most likely what someone is, or soon will be, researching at Berkeley.

I hope that they will find the problem quickly, and that the fix is easy to do.

I have found today that (if you have the time), going into the Transfer tab, selecting all the units trying to upload, then clicking the "Retry Now" button each time all have backed off, will get them completed within a few minutes of retrying. This only works when the cause of the failed updates is related to certain types of technical problems. Unfortunately, many times the issue at hand during one of these events will preclude the success of this retry procedure. Today, though, we are in luck, i.e., the retry6 does work.

I hope this help.

Hi Cherokee,

Yeah, that's about what I was getting at. I guess it was more logical than I thought. ;)

I do try the "Retry Now" and some do get through. I don't like to do it too often though since there are thousands of us trying to upload our finished work. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

splitting isn't happening properly either from the looks of it. It is around lunchtime for the Seti crew. Does anyone know if they are aware there is an issue??

I don't get it! WUs are at 100% progress and then go into resend mode. How the heck does THAT work?

That last Ack/Nak to finish the transfer either didn't get sent or got eaten by a router. Quite a few also die in mid-stream. All it takes is to time out on retries looking for that last handshake.

---

I haven't seen any notice or post that anyone has contacted staff. So they might not be aware of the issue if they haven't looked at the forums or the servers stats.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

My avg. work done as is reported on Boinc manager has been stuck for several hrs. This is not normal. Here on the web site it moves around as is normal.

---