Me thinks you are screwed (unless there is another way to it) you need to interrupt tasks when being reported to get the resends to come in.

Me thinks you are screwed (unless there is another way to it) you need to interrupt tasks when being reported to get the resends to come in.

Ok. Will give E@H a little help while waiting to fix the problem here. Thanks

---

In the mean time, all work done but still appearing Em progresso (51) in my host task list.
Sure they are ghosts, did anyone remember the post where the ghost DL sequence is explained?

Did save the explanation, sorry don´t remember from who

As an alternative to the "ghost" recovery process that I had previously posted quite a while back (involving client_state backup and restore, etc.), I have another one to offer that I think is simpler and can be entirely controlled within BOINC Manager. It just requires a fast finger on your mouse button, since the key here is to interrupt a scheduler request before it completes. I just used this quite successfully over the weekend to recover 127 "ghosts" that I had created on Friday when I started trying to run the "Special" app on Linux. I just went back to that machine occasionally when I had a few minutes and ran it when I knew I had room in the queue for at least 20 tasks to be recovered, so 7 times in all. I figured that, since it was my fault for creating the "ghosts", the least I could do was try to recover them as a courtesy to my wingmen.

1) Set "No New Tasks"

2) Make sure you have enough room in your work buffer to accommodate your "ghosts" (up to a maximum of 20 per request). If you're not one of those who typically have a queue which reaches the task limits, simply increasing the size of your work buffer should be sufficient. Otherwise, you'll have to wait until you've reported enough completed tasks to free up the necessary space in your queue.

3) Wait for, or initiate (using Update), a scheduler request that reports at least one completed task.

4) As soon as you see the scheduler request commence, interrupt it by IMMEDIATELY clicking "Suspend network activity". I find it easiest to first open the "Activity" menu drop-down and, while keeping my mouse pointer poised over "Suspend network activity", keep a close eye on the Event Log awaiting the start of the scheduler request. Then, as soon as the scheduler request commences, just CLICK.

If successful, the Event Log will show lines like this, and stop:
-------------------------------------------------
Sending scheduler request: To fetch work.
Reporting 1 completed tasks
Requesting new tasks for CPU and NVIDIA GPU
Not requesting tasks: "no new tasks" requested via Manager
Suspending network activity - user request
-------------------------------------------------

If you get a "Scheduler request completed" line before the "Suspending network activity" line, you weren't quick enough. For me, at least, that hasn't been a problem.

5) To be on the safe side, at this point, I usually Exit BOINC completely, shutting down all running tasks, wait a minute or so, then restart BOINC. Note that network activity should still be suspended when BOINC resumes. You should also still see your task(s) "Ready to report".

6) "Allow New Tasks"

7) Resume network activity (always, or based on preferences, whichever is normal for you). If a scheduler request isn't triggered automatically, click "Update". The Event Log should now show something such as:
-------------------------------------------------
Sending scheduler request: To fetch work.
Reporting 1 completed tasks
Requesting new tasks for CPU and NVIDIA GPU
Scheduler request completed: got 4 new tasks
Resent lost task blc4_2bit_guppi_57432_24865_PSR_J1136+1551_0002.22874.831.18.27.49.vlar_1
Resent lost task blc4_2bit_guppi_57432_24865_PSR_J1136+1551_0002.22874.831.18.27.189.vlar_0
Resent lost task blc4_2bit_guppi_57432_25217_HIP57328_0003.22901.831.18.27.241.vlar_0
Resent lost task 01au09aa.11976.21340.7.34.21_1
-------------------------------------------------

followed by the usual task download messages.

NOTE: Since 20 "ghosts" seem to be the maximum that can be retrieved in one request, those with more than 20 "ghosts" will need to repeat the process multiple times, at least 5 minutes apart.

NOTE 2: If any of the "ghost" tasks are Arecibo VLARs, the scheduler may try to send them to an NVIDIA GPU (if you have one), which will fail, marking the task as "Abandoned". At least it's no longer a ghost.

3) Wait for, or initiate (using Update), a scheduler request that reports at least one completed task.

Thanks for your step by step explanation, but i believe i'm screwed, i have no more WU on my cache. All was crunched and sended .

---

We are all heading into "Sit back and wait" mode until someone who can gets into the lab and gives the servers a prod to get them moving again.

---

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

. . Probably just this machine then ...

Your Windows system has 1 GPU, and is doing CPU crunching, so that would mean a total of 200WUs.
According to your task list you've got 206.
So since you've got 6 more than the limit, and you're getting CPU work, I guess it won't let you have any more GPU work till those GPU Ghosts time out, more than 6 GPU WUs have been reported, or you re-claim them.

EDIT-
WTF? That system now shows 313 tasks in progress. 113 more than it should have.
Are you playing with the app_info.xml again?

. . Nope I have 113 ghosts left from the 1st attempt but after I wrote those messages I got a load of work. I should have posted that but I went out. so that was a full cache plus the 113 ghosts.

. . Now I am getting no work at all on the Linux boxes. They have been getting "no tasks available" since 2:30 pm AEST. Though occassionally they have received a small batch of 2 or 3 tasks at long irregualr intervals. Bertie has been out of work completely on CPU and GPU for over 4 hours. Not a good sign since there are 600K tasks in the RTS hopper ...

Stephen

PS, I have since seen the messages about the SSP being frozen ...

:(

Hope Eric or Jeff get up early today.

+ 1
In the mean time, all work done but still appearing Em progresso (51) in my host task list.
Sure they are ghosts, did anyone remember the post where the ghost DL sequence is explained?

. . Set 'No new tasks'

. . make suren there are enough uploads to have time to go through the sequence and that it has been 5 mins since last update.

. . (I have open the event window to monitor the progress, the transfer window to know when the last task is uploading and the options window open to be ready to shut down the internet access)

. . Start the uploads, when the last transfer is running watch the event window for the 1st sign of a response then shut down the network.

. . Close Boinc down (client) give it a little while then open BOINC again. Set fetch new work and re-enable the network, you should get 20 resends.

Stephen

. . I have to do it from time to time.

. . And as Brent said, if you have no work to complete and upload then you are done like a duck dinner. It won't work.

> >

There is probably nothing in RTS.
The SSP page is 32 hours stale.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

In the mean time, all work done but still appearing Em progresso (51) in my host task list.
Sure they are ghosts, did anyone remember the post where the ghost DL sequence is explained?

Did save the explanation, sorry don´t remember from who

NOTE 2: If any of the "ghost" tasks are Arecibo VLARs, the scheduler may try to send them to an NVIDIA GPU (if you have one), which will fail, marking the task as "Abandoned". At least it's no longer a ghost.

. . This part no longer applies unless you use very old hardware and apps. Nvidia GPUs are now getting Arecibo VLAR tasks as normal.

Stephen

:)

The kitties are still patiently waiting for that big kick to the servers...........................

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

SSP is dry, but current.

SSP is dry, but current.

Ahhh...well, that should mean that somebody is working on it.
Good news.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

anyone getting any WUs? over a million in "Workunits waiting for assimilation". Looks like they added some AP splitting to the mix too.

None here in a long time.

---

Hello? Has the "prod" happened? Still not getting any CPU work, here...

---

.

Hello, from Albany, CA!...

Got 1 new AP on 2 diff hosts but thats all.

5/7/2018 11:22:49 AM | SETI@home | Project has no tasks available

---

Results ready to send 0 0 231 0m

hopefully this is good news... hope this means that the huge amount (1.1 million+) waiting to be assimilated are finally being assimilated.

Ah, we have some result creation, and I'm starting to fill up. Just in time to go to bed ;-)

I'll sort out the mess in the morning.

Ah, we have some result creation, and I'm starting to fill up. Just in time to go to bed ;-)

I'll sort out the mess in the morning.

. . Half your luck, getting nothing here ...

. . [edit] OK, I changed the host 'location' to home and got a FULL cache ...

Stephen

:(