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

possibliy using more than one session of boinc and then make fusion between them ?

---

Eric is working on the problems.

Meow!

---

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

Eric is working on the problems.

Meow!

Thanks for the installation Mark

---

Uploads are definitely very iffy today.

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

Just like a switch was flipped ...

. . Yep, one minute everything is fine, then no uploads without kicking them over and over ... :(

Stephen

:(

Look at the User Stats. A User can't have a Host with better stats than the User. Here's Magne's stats, https://boincstats.com/en/stats/-1/user/detail/204994/lastDays
The machine that was at #28 had OpenCL installed, the machine that appeared at #8 Doesn't have OpenCL installed. Not having OpenCL is common on a New Build as the installer doesn't install OpenCL by default.
We Know what happened to Juan. He broke his One computer's networking and had to reinstall the OS. When it came back online with the New system the SETI Server gave it a New ID with an Extra One BILLION Credits and Over an Extra One MILLION RAC. Juan wasn't doing anything out of the ordinary, certainly not 'fusioning'. It appears the Exact same thing happened with Magne, it blinked out with an RAC of around 172k and blinked back in with an RAC of 363k which is impossible for that machine, and his User Stats.

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

possibliy using more than one session of boinc and then make fusion between them ?

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

. . They are the most frustrating, after kicking them and kicking them you see one get to 100%, then ... nada, it just sits there taunting you ... aaarrggghh!

Stephen

:(

We've seen this sort of things a few times when the database gets its bits in a twist, and that has been followed by a disk handing its notice in....

---

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

welp, the 1mil system is out of work, with about 2800 uploads just waiting to go through.

---

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

Are they all reported?

---

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

A proud member of the OFA (Old Farts Association)

Are they all reported?

Reporting happens after upload is complete, right? At least here :)

---

Nope. That’s the problem. They won’t upload (well they do eventually. Just a lot slower than normal). So I can’t report them. And with so many uploads pending, I haven’t been able to download new tasks all day. So I’ve run dry. Only the slower systems have been able to keep a low enough cache of pending uploads to still get downloads.

---

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

I've been babysitting the farm all day. As long as a couple get uploaded, I can then do an update to report 100 tasks. Then I can get more work.

---

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

A proud member of the OFA (Old Farts Association)

What I was trying to suggest is that Reporting is the act of telling the scheduling server that a task has been completed and uploaded to the upload server. True?

---

I've been babysitting the farm all day. As long as a couple get uploaded, I can then do an update to report 100 tasks. Then I can get more work.

I was babysitting it all day too. But I can only report them at the rate that they upload. Which is slower than the rate at which they are computed. So the pending cache just grew and grew and never let up

Yep uploads remain borked.

---

I've been babysitting the farm all day. As long as a couple get uploaded, I can then do an update to report 100 tasks. Then I can get more work.

Thank you for the hint. I tried a manual update and suddenly it started uploading......
--edit----------
Rats, it looks like it stalled again...
--edit---
Tried the 8 uploads trick. And that got something moving again. I even got some Seti downloads. Then it started timing out again so I dropped it back to 2. And it is still clumping along uploading.
--edit---
Apparently leaving it at 8 uploads/downloads keeps enough connections "active" that 1 or 2 get through every once in a while.

Tom

---

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

This is getting tiring ...
I up'd my transfer count to 16 which seems to have helped by having more connections open.

---

Why stop at 8? I put mine at 14 simultaneously long ago, and it has helped me through many of these bottlenecks. It's not 100% successful, but enough get through that I can usually get enough downloads to keep reasonably busy. Also, if your machines process units super fast, and you are completely unable to get new work because of too many downloads, you might try setting "No new tasks" and nurse all the uploads through. When they are all uploaded, you can turn new work back on and, hopefully, fill your caches completely, or nearly completely, all at once, before too many new units complete and build up the backlog, resulting in the old, frustrating message, "Not requesting tasks: too many uploads in progress" bites your machines from behind, so to speak.

Just a thought, eh?

Yes, Brent, you've got the right idea! (I was typing my response to Tom when you posted, so I didn't see it. ) I think I will boost mine from 14 1o 16, also. I made a bold move to 14 years ago, long before GPU processing took SETI to its "Next Generation". I guess it's time to add a couple more to mine, too. :-)