3/4/2021 22:34:07 PM | Einstein@Home | [work_fetch] request: CPU (18978.80 sec, 0.00 inst) NVIDIA GPU (0.00 sec, 0.00 inst)
3/4/2021 22:34:07 PM | Einstein@Home | Sending scheduler request: Requested by user.
3/4/2021 22:34:07 PM | Einstein@Home | Requesting new tasks for CPU
3/4/2021 22:34:09 PM | Einstein@Home | Scheduler request completed: got 1 new tasks
3/4/2021 22:34:09 PM | Einstein@Home | Project requested delay of 60 seconds
3/4/2021 22:34:09 PM | | [work_fetch] Request work fetch: RPC complete
3/4/2021 22:34:14 PM | | choose_project(): 1614886454.242868
3/4/2021 22:34:14 PM | | [work_fetch] ------- start work fetch state -------
3/4/2021 22:34:14 PM | | [work_fetch] target work buffer: 345600.00 + 345600.00 sec
3/4/2021 22:34:14 PM | | [work_fetch] --- project states ---
3/4/2021 22:34:14 PM | Einstein@Home | [work_fetch] REC 21454.221 prio -41516.762 can't request work: scheduler RPC backoff (54.91 sec)

So, log says 1 task received.
But actually nothing downloaded from project.

---

Enable file transfer debug and see what that says would be my first line of investigation.Then wait until after the back off time before requesting work again. If you request more work before that time, then the timer just starts again. A pain if you have just fixed the problem, especially when it is CPDN and the back off time from the server is an hour.

Edit: I would also see what your project page says about tasks on that computer.

file_xfer_debug enabled:

3/4/2021 22:51:23 PM | Einstein@Home | choose_project: scanning
3/4/2021 22:51:23 PM | Einstein@Home | can fetch CPU
3/4/2021 22:51:23 PM | Einstein@Home | CPU needs work - buffer low
3/4/2021 22:51:23 PM | Einstein@Home | checking CPU
3/4/2021 22:51:23 PM | Einstein@Home | [work_fetch] using MC shortfall 32638.392420 instead of shortfall 2017643.962671
3/4/2021 22:51:23 PM | Einstein@Home | [work_fetch] set_request() for CPU: ninst 4 nused_total 145.00 nidle_now 1.16 fetch share 1.00 req_inst 0.00 req_secs 32638.39
3/4/2021 22:51:23 PM | Einstein@Home | CPU set_request: 32638.392420
3/4/2021 22:51:23 PM | Einstein@Home | checking NVIDIA GPU
3/4/2021 22:51:23 PM | Einstein@Home | NVIDIA GPU not high prio proj
3/4/2021 22:51:23 PM | Einstein@Home | [work_fetch] request: CPU (32638.39 sec, 0.00 inst) NVIDIA GPU (0.00 sec, 0.00 inst)
3/4/2021 22:51:23 PM | Einstein@Home | Sending scheduler request: To fetch work.
3/4/2021 22:51:23 PM | Einstein@Home | Requesting new tasks for CPU
3/4/2021 22:51:27 PM | Einstein@Home | Scheduler request completed: got 1 new tasks
3/4/2021 22:51:27 PM | Einstein@Home | Project requested delay of 60 seconds
3/4/2021 22:51:27 PM | | [work_fetch] Request work fetch: RPC complete
3/4/2021 22:51:32 PM | | choose_project(): 1614887492.138582
3/4/2021 22:51:32 PM | | [work_fetch] ------- start work fetch state -------
3/4/2021 22:51:32 PM | | [work_fetch] target work buffer: 345600.00 + 345600.00 sec
3/4/2021 22:51:32 PM | | [work_fetch] --- project states ---
3/4/2021 22:51:32 PM | Einstein@Home | [work_fetch] REC 21450.815 prio -116558.871 can't request work: scheduler RPC backoff (54.92 sec)
3/4/2021 22:51:32 PM | Milkyway@Home | [work_fetch] REC 6652.195 prio -1.017 can request work
3/4/2021 22:51:32 PM | SETI@home Beta Test | [work_fetch] REC 0.000 prio 0.000 can't request work: suspended via Manager
3/4/2021 22:51:32 PM | | [work_fetch] --- state for CPU ---
3/4/2021 22:51:32 PM | | [work_fetch] shortfall 2017072.46 nidle 1.16 saturated 0.00 busy 0.00


Same. No new entries cause NO file transfers as I said earlier...

---

Edit: I would also see what your project page says about tasks on that computer.

It says 43 tasks
Client lists 44.

---

Not saying it happened on this occasion, but it is entirely possible to receive a new task from Einstein with no visible downloads.

It only happens with the Gravity Wave search, which uses locality scheduling. Even for your first task, you need to download something like 48 data files, up to 200MB. But once you've got them, the server tries, and - after a bug was fixed last week - often succeeds in sending you a new 'task' which is just a set of parameters to specify how to analyse the data which you've already got.

Not saying it happened on this occasion, but it is entirely possible to receive a new task from Einstein with no visible downloads.

It only happens with the Gravity Wave search, which uses locality scheduling. Even for your first task, you need to download something like 48 data files, up to 200MB. But once you've got them, the server tries, and - after a bug was fixed last week - often succeeds in sending you a new 'task' which is just a set of parameters to specify how to analyse the data which you've already got.

Yep. The problem is - currently GWnew disabled in project options. Because of issues we discuss in other thread.
EDIT: though maybe it still slipping in through "work for other apps" in case there is no FGRP work available currently.
I'll check this once again, thanks.

EDIT2: and that was the case indeed. So this case is closed, thanks all.

---