Only one gbt splitter is running. Time for Panic?

definitely :-)

the sah assimilators are not running so we have a little less than 5 hours of WUs left.

The Assimilators clean up after WUs have been processed & the results returned, but they have nothing to do with the production or distribution of work to be processed.

Thank you. I misunderstood. It sounds like it is the Results of the processed WU that is assimilated into the science db, so the bit labeled "Workunits waiting for assimilation" is just the WU waiting for the result to be put into the science db then the WU moves to the "Workunit files waiting for deletion" stage.

So the data file is split into WUs. The WU is validated, and then put into the RTS. then it comes back with a result that waits for validation once validated. the result is assimilated. once the result is assimilated the original WU can be deleted. ???

So the data file is split into WUs.

Yep.

The WU is validated

Nope.
Once it's split, it goes straight to the Ready-to-send buffer. From there it gets sent out to 2 systems to be processed.

Validation happens after the WU has been processed, and the result is returned to the server. That result is compared with the result returned from the other system for that WU- if they match then they are Validated (if they don't match, another copy is sent out to be processed, then that result is compared with the other(s)), the result is then Assimilated in to the science database, then the WU & results are eventually deleted, then purged from the working database.

---

Grant
Darwin NT

Only one gbt splitter is running. Time for Panic?

Oh yeah- there is a whole sea of red on the Server status page now.
At least the web site & forums are staying up (for now).

---

Grant
Darwin NT

Passes a "Xanax" to everyone :)

If you have your checkpoints sufficiently long enough to be greater than the crunching time of the task, then the task just starts over from zero when you restart BOINC. No harm, no foul.

What checkpoint time you use? And where i put that?

. . It is in the BOINC preferences page where you find the No of CPUs to use etc, it is 'Minimum time to checkpoint'.

. . Use whatever your average run time is plus 10% to 15%. On my machine where the average run time is 5 mins I use 6 minutes. (I know that is plus 20% but I like round numbers)

Stephen

:)

Didn't we all have this trouble this time last year also in April this year? Wonder if it's due to Day Light Savings starting and Ending around the world?

. . I guess it could be but since SETI runs on UTC I would think the only conflict would be local 'Day Light Saving' changes at Berkeley.

Stephen

:)

And we're just a few minutes away from running dry...
Quite convenient that i was fiddling with rescheduler script last night and managed to fill up my cache before this unexpected down time!

---

I just remembered having this discussion 6 months back then further 6 months bout the time I rejoined..

What checkpoint time you use? And where i put that?

. . It is in the BOINC preferences page where you find the No of CPUs to use etc, it is 'Minimum time to checkpoint'.

Usual caveat: there are two different places to set preferences.

If you have ever viewed your settings in BOINC Manager, and exited by clicking 'OK' (old versions) or 'Save' (very recent versions only) you will have created a 'global preferences override' file, and BOINC will exclusively use the settings contained in that file. Changing the web setting after that event will have no effect at all.

If you want to change the checkpoint interval, look first at the Options --> Computing preferences dialog in BOINC Manager. Read the top panel. If it says 'Using web preferences', back away very carefully by clicking the 'Cancel' button (or pressing 'Esc'), and go change it on the web as described. If it says 'Using local preferences', then change it there: Computing tab, last box.

Ahhh...just lovely.
I see the splitters are on the lam again and RTS has disappeared.
I sent the word out, but of course it's 4AM in Berkeley and Sunday.
So I don't expect to see any kicking done real soon.
Meowsigh.

---

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

If nothing changes in the next hour the big crunchers will start to suffer with WU starvation very soon.

Why this things normaly happening in the dawn of a weekend day?

I know is the Murphys law in action.

---

How about that "gbt splitter 3" . Hanging tough and splitting long after all the others have given up.

someone needs to give all the splitters a kick (I.E. a re-boot, or boot in the bum...)

---

.

Hello, from Albany, CA!...

Splitters are still borked.

---

Splitters are still borked.

it`s sunday very early in CA.

---

Weeellll, it's 10am, I suppose it could be considered early, depending on the activities of the previous evening..? ;-)

---

Woke up this morning to no tasks but I expected that outcome given the hiccups and yo-yo'ing project yesterday. Servers are borked and will probably need a complete reboot of the project in sequence.

---

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

A proud member of the OFA (Old Farts Association)

still no tasks here

---

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

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.

Since the project has run out of work, this seemed like an opportune time to try to switch to this version.

i installed the dependencies listed in your post on CA
i copied all files from my /var/lib/boinc-client/projects/seti directory to the BOINC/projects/seti directory in my Home folder
i moved the client_state file over also

but i think maybe something is not right. it's saying my boinc version is 7.8.3, not 7.4.44

EDIT: nevermind, i got it. i missed that this package was not 7.4.44 natively and you had to extract the 7.4.44 components separately. got it now.

also, do i have to do anything special to remove my old service install of BOINC 7.9.3? when installing the dependencies and copying boinc folder to my home folder, i noticed my service install blanked out and removed my project.

running sudo apt-get remove boinc-client boinc-manager returned that neither were installed, which seemed odd to me. is it gone from something i did? can i just delete the boinc-client and boinc folders from my var/lib/ directory?

will this new version auto-start at system boot like the service install does?

---

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