not a panic, but an observation.

I've noticed all of my systems experiencing a handful of stuck downloads. it's fixed easily just hitting the "Retry Now" button.

Been occurring for a while, along with the occasional upload taking a second attempt to get through, although it has been occurring more often over the last couple of days.

---

Grant
Darwin NT

Was clear for a while but starting to get sticky again ...

---

still seeing download issues persisting.

someone want to shoot off a bat signal?

---

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

I see half of each download request go to immediate backoff at the start of the download. I assume this is caused by the added new strain to the servers from the cache limit adjustment.

Any server fine tuning that can ameliorate the issue?

---

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

A proud member of the OFA (Old Farts Association)

I see half of each download request go to immediate backoff at the start of the download. I assume this is caused by the added new strain to the servers from the cache limit adjustment.

Same here, occurs on my Linux system (no Hosts file setting). No issues on Windows system (Hosts file set to Georgem).
I can't see it having anything to do with the cache limit adjustment unless somehow the larger Work in progress has an impact on Vader- while it does to transition work, I can't see the increase in Work-in-progress affecting that unless it's resulting in data no longer being cached. Likewise for it's Assimilator work.
When it comes to downloads, Vader has always had issues over the years.


Edit- just as I was about to go hunting for my Linux Hosts file & edit it, the downloads started downloading without assistance again.

---

Grant
Darwin NT

Yes I just brought the daily driver back online and had to download over a hundred tasks to try and refill the cache depleted by the backed off downloads. They came down with no issues.

---

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

A proud member of the OFA (Old Farts Association)

Splitters struggling again.
After a large overshoot the Ready-to-send has fallen by over 300k in under 2 hours, and still heading south.

---

Grant
Darwin NT

We have between 1-2 hours (262k) in the RTS queue, plus whatever it can split, but it isn't splitting fast enough. There is over 7.2 million out in the field, so hopefully everyone has enough WUs for a bit while the system is slow to split. I can only assume it is busy validating or assimilating or deleting and that is why splitting has slowed down. Hopefully splitting will pick up again when whatever is keeping it busy now is done.

Hi Grant,

I see we're still experiencing server problems, and I've not heard anything about a shortage of CPU tasks, but I have not been able to get any on one of my systems. Getting plenty of GPU tasks , but no CPU tasks. Anyone else having this problem? I did install the new Boinc update but I doubt that that is the problem.

Allen

---

Which host is giving you issues? I see cpu tasks received today on your hosts.

---

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

A proud member of the OFA (Old Farts Association)

Yes, all others are doing okay for now. The one in question is ID: 8048221. Last server response says that it is out of work, but I have no CPU work.

Allen

---

Your CPU requests were likely in "back off request mode" and that can be for as long as 4 odd days.

There was a simple way to check and rectify that with the ancient BOINC version that I use to use, but I can't seem find out how to do that yet with the much newer version that I'm using now.

Cheers.

I guess I should explain my whole situation, just so there is nothing left to chance. For the last two days I have been given the response from the servers on request for work, that the servers may be down. I had had about 25 tasks to report, but it would not report them. Not knowing what else to do, I did a reset, as much as I hated to and loaded the newest version of Boinc. That got me connected again, but only able to receive GPU tasks.
Well, that's the whole sad story. I was using version 7.6.2, I think.

Allen

---

Your CPU requests were likely in "back off request mode" and that can be for as long as 4 odd days.

There was a simple way to check and rectify that with the ancient BOINC version that I use to use, but I can't seem find out how to do that yet with the much newer version that I'm using now.

Cheers.

If you have the Manager running, highlight Seti in the projects tab and then select Properties. That shows you the backoff timeouts for both the cpu and gpu.

---

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

A proud member of the OFA (Old Farts Association)

General
URL
http://setiathome.berkeley.edu/
User name
AllenIN
Team name
Resource share
100
Disk usage
308.82 MB
Computer ID
8708442
Suspended via GUI
no
Don't request tasks
no
Host location
home
Tasks completed
5,683
Tasks failed
1
Credit
User
54,237,194 total, 30,464.61 average
Host
384,969 total, 1,542.58 average
Scheduling
Scheduling priority
-1.04
Last scheduler reply
12/15/2019 8:17:36 PM
This is all I see there.

Allen

---

I guess I should explain my whole situation, just so there is nothing left to chance. For the last two days I have been given the response from the servers on request for work, that the servers may be down. I had had about 25 tasks to report, but it would not report them. Not knowing what else to do, I did a reset, as much as I hated to and loaded the newest version of Boinc. That got me connected again, but only able to receive GPU tasks.
Well, that's the whole sad story. I was using version 7.6.2, I think.

Allen

You are running anonymous platform. Do you still have cpu applications defined in your app_info?

If running the Manager use the Event Logging flags to set cpu_sched_debug and see if you are even requesting cpu work. For a complete check, set work_fetch_debug and cpu_sched_status flags in the Event Log.

---

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

A proud member of the OFA (Old Farts Association)

I'm sorry,but the log I sent you is from the wrong system. I'll get on the other system.

---

Tasks failed
1

If you fail a task, BOINC gives you a 24 hour timeout and only sends you one task for the next day. You have to return that one task as valid before it will send you any more. You are likely in timeout.

---

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

A proud member of the OFA (Old Farts Association)

I think you are right.


General
URL
http://setiathome.berkeley.edu/
User name
AllenIN
Team name
Resource share
100
Scheduler RPC deferred for
00:03:26
Disk usage
302.61 MB
Computer ID
8048221
Suspended via GUI
no
Don't request tasks
no
Host location
home
Tasks completed
0
Tasks failed
0
Credit
User
54,238,004 total, 30,475.30 average
Host
8,253,718 total, 4,911.15 average
Scheduling
Scheduling priority
-0.05
CPU task request deferred for
00:05:23
CPU task request deferral interval
00:20:00
Last scheduler reply
12/15/2019 8:43:11 PM

---

I'm sorry,but the log I sent you is from the wrong system. I'll get on the other system.

Something strange about that system. You are up to 786 tasks currently and you should only have a maximum of 500. One cpu =200 tasks and one gpu =300 tasks. For the venue location that host is on, does it have cpu work enabled? Are you spoofing gpus that would give more work than a stock system?

[Edit] Forgot you said you reset the host. Likely the extra tasks are lost tasks or ghosts.

---

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

A proud member of the OFA (Old Farts Association)