It looks like we don't have any WUs available to download? Server status says zero for Astropulse and both Seti versions.

It looks like we don't have any WUs available to download? Server status says zero for Astropulse and both Seti versions.

Yes it looks like splitters stopped doing their job 13h ago so we ran out of WUs a couple hours ago

---

3 of my systems have run out of work it seems. 0 in progress

:(

---

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

I just started to receive tasks.

I sent the word out.
Hopefully Eric or Jeff are available and get the message soon to put their big boots on and kick something.

Meow.

EDIT.....
And Jeff replied. He thinks it is fixed for now. Silly arse log file issue.

---

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

no task available,

0 ready to send,

some logic here O:-)

---

result creation now 90/a second, must have been kicked.

result creation now 90/a second, must have been kicked.

You betcha it has.
Meowmeowmeow.

---

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

2 out of 3 of my systems that ran dry have picked back up, but my ex-Mining maching has yet to pick back up.

looks like it's submitted it's last tasks around 10:30 UTC, and has had communication with the project as recent as 16:00 UTC. but still shows 0 tasks in progress.

i've had this problem in the past (with another system, but similar hardware and software configuration), during wow, when it ran dry, and just wouldn't reconnect for more jobs until i rebooted the system. i'll have to see what's up with it when i get home.

---

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

If a system doesn't report a task every 10 minutes the 5 minute timer goes to (I think) 2 hours, or 1 hour.
A manual "Project Update" will connect to the server again. If it misses getting tasks on that try an the next, It goes back into a back off again.

And clicking 'update' is far faster than a reboot, even if you're booting from an SSD.

If a system doesn't report a task every 10 minutes the 5 minute timer goes to (I think) 2 hours, or 1 hour.
A manual "Project Update" will connect to the server again. If it misses getting tasks on that try an the next, It goes back into a back off again.

And clicking 'update' is far faster than a reboot, even if you're booting from an SSD.

i don't have system access at the moment, so i cannot click "Update". I can simply see the stats for last contact here in my computers list. but when i had a similar issue to this in the past, even clicking update would not work. it just didnt get anything. no errors, just no tasks given. reboot and it was back.

but it has been 6+ hours , coming up on the 2hr mark since last contact in a few mins. so if it doesn't pick anything up, it'll have to wait until i get home to see what it's doing.

---

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

download 40 task at 16h33 UTC

---

That's why BOINC 7.4.44 was developed. Required software for your Linux mini-super computer. Not only does 7.4.44 allow your Investment to store enough work to make it through a Tuesday Outrage, it doesn't have a Back-Off 'Feature'. 7.4.44 will bang on the Server relentlessly every 5 minutes requesting work. Considering a mini-super computer returns around 10 tasks every 5 minutes, it makes sense to request work every 5 minutes. 7.4.44 is available in the Docs folder of the Linux BOINC All-In-One package.

That's why BOINC 7.4.44 was developed.

Just curisity it still has the 1000 WU limit or that was changed to 3000?

---

That's why BOINC 7.4.44 was developed. Required software for your Linux mini-super computer. Not only does 7.4.44 allow your Investment to store enough work to make it through a Tuesday Outrage, it doesn't have a Back-Off 'Feature'. 7.4.44 will bang on the Server relentlessly every 5 minutes requesting work. Considering a mini-super computer returns around 10 tasks every 5 minutes, it makes sense to request work every 5 minutes. 7.4.44 is available in the Docs folder of the Linux BOINC All-In-One package.

Do you have to use Jeff's Rescheduler [CPU->GPU] to bank enough to cover outages? or does it bank some natively?

there is a per-component 100 task limit still, right?

---

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

i don't have system access at the moment, so i cannot click "Update". I can simply see the stats for last contact here in my computers list. but when i had a similar issue to this in the past, even clicking update would not work. it just didnt get anything. no errors, just no tasks given. reboot and it was back.

Yes, that is what happens to me to with the 7.8.3 host. After running out and not reporting anything for a while, Updating just keep returning the no tasks are available message even when the RTS buffer has 600K available. Solution is to make sure you let the 5 minute timer run down almost all the way, then exit BOINC and wait out the remaining time on the timeout and then restart BOINC. BOINC will then get a large slug of tasks out of what is available in the buffer and continue on normally.

Don't see that issue with TBar's 7.4.44 which is my preferred BOINC. I only run 7.8.3 on one host because MilkyWay won't run on any BOINC less than 7.6.33.

---

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

A proud member of the OFA (Old Farts Association)

That's why BOINC 7.4.44 was developed. Required software for your Linux mini-super computer. Not only does 7.4.44 allow your Investment to store enough work to make it through a Tuesday Outrage, it doesn't have a Back-Off 'Feature'. 7.4.44 will bang on the Server relentlessly every 5 minutes requesting work. Considering a mini-super computer returns around 10 tasks every 5 minutes, it makes sense to request work every 5 minutes. 7.4.44 is available in the Docs folder of the Linux BOINC All-In-One package.

Do you have to use Jeff's Rescheduler [CPU->GPU] to bank enough to cover outages? or does it bank some natively?

there is a per-component 100 task limit still, right?

No BOINC is still limited by the servers to 100cpu/100gpu. You have to use a Rescheduler to bank or bunker for an outage. Jeff's is nice to work with.

---

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

A proud member of the OFA (Old Farts Association)

That's why BOINC 7.4.44 was developed.

Just curisity it still has the 1000 WU limit or that was changed to 3000?

Are you asking about 7.4.44 or 7.8.3? 7.4.44 has the 3000 limit and 7.8.3 still has the 1000 limit.

---

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

A proud member of the OFA (Old Farts Association)

That's why BOINC 7.4.44 was developed.

Just curisity it still has the 1000 WU limit or that was changed to 3000?

Are you asking about 7.4.44 or 7.8.3? 7.4.44 has the 3000 limit and 7.8.3 still has the 1000 limit.

As you could allready know 1000 WU is not enought with the 4 X GPU hosts and the regular outages.
I was asking if the 7.8.3 was changed to support 3K WU like the 7.4.44 but apparently the 1k limit is still on place.
Rescheduling is good, but you need to be aware, sometimes its fails in the shooting down process of the WU and leaves the slot opened. At least that still happening on my host but with the help of some friends i was abble to create a way to bypass of the problem.

---