As I wrote, my definition of 'a few' was again about 6 hours, but it is still in progress. But after that, there will be no bigger maintenance for a longer time. Sometimes it has to be done and don't worry, there is the progress. But due to many files in different location I can only guess the estimated time and I was wrong twice this time. There are over 8000000 files so it takes some time.

thought so!

those out here, that are in business for quite some time, don't give predictions like that.

much better to report "progress is at x% now" - no linear predictions possible.

simply because that's the one and only thing that's sure. ;)

Hi,

7.2.42 will report every hour. No need to use the flag, unless you can't hold on for one hour :-)

OK, but then again, if my CPU normally uses 1.5 hour for a job and GPU's 2.5, a 3 hour update would be effective I think. No need for all that traffic, or what??

Maintenance!! As Dagorath put it so very well:
"...maintenance happens, no sense whining about it, deal with it instead.."
This is why there's a function "Do other work if non left for project", or something like that. ;)

7.2.42 will report every hour. No need to use the flag, unless you can't hold on for one hour :-)

This setting is for Boinc in general, right? So it will be the same for SETI@home!? Sorry for the newbie question. Has been reading so much, I'm totally light headed :o

Regarding BoincTasks and updates. What does it mean when the field "CPU%" goes red. Usually blue on green when running full speed. When I came home, all serves where running slow and the fiels "CPU% where red on green I think. It was red, this I'm sure of and they where running slowly.
Is this because they haven't been able to communicate with the update servers? Or what can be the reason. Have looked at help on BoincTasks site! No red markings there!? There where jobs to do, so it can't be that. !?

Have a nice one, all of you ;)

---

Project Headless CLI Linux Multiple GPU Boinc Servers
Ubuntu Server 14.04.1 64bit
Kernel 3.13.0-32-generic
CPU's i5-4690K
GPU's GT640/GTX750TI
Nvidia v.340.29
BOINC v.7.2.42

OK, but then again, if my CPU normally uses 1.5 hour for a job and GPU's 2.5, a 3 hour update would be effective I think. No need for all that traffic, or what??

Maintenance!! As Dagorath put it so very well:
"...maintenance happens, no sense whining about it, deal with it instead.."
This is why there's a function "Do other work if non left for project", or something like that. ;)

7.2.42 will report every hour. No need to use the flag, unless you can't hold on for one hour :-)

This setting is for Boinc in general, right? So it will be the same for SETI@home!? Sorry for the newbie question. Has been reading so much, I'm totally light headed :o

Have a nice one, all of you ;)

7.2.42 will report every hour, whether or not a completed task is available to report. The report every hour setting will work for all Boinc projects, including SETI. The accept work for other applications selection is for other applications within the same project. But it is still a good idea to have a back-up project in mind.

Hi Swiftmallard ;)

Thanks for setting me straight ;)

The accept work for other applications selection is for other applications within the same project. But it is still a good idea to have a back-up project in mind.

OK; I didn't know that. Thank you!!

---

Project Headless CLI Linux Multiple GPU Boinc Servers
Ubuntu Server 14.04.1 64bit
Kernel 3.13.0-32-generic
CPU's i5-4690K
GPU's GT640/GTX750TI
Nvidia v.340.29
BOINC v.7.2.42

I just have to ask. I had several tasks that have been unable to upload due to this maintenance. They are now all past the due date. Will I get credit for them when the server is back up??

---

Probably you will this time but don't count on it everytime. If you have tasks that are already beyond deadline then you're pushing your luck more than I would push. It's up to you of course but you might want to decrease your cache if that's what's causing it.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

Or perhaps it's caused by 4 to 6 hours of unannounced maintenance that has ballooned into 40 to 60 hours, or will it become 4 to 6 DAYS!

---

Or perhaps it's caused by 4 to 6 hours of unannounced maintenance that has ballooned into 40 to 60 hours, or will it become 4 to 6 DAYS!

Crap happens so get used to it because it ain't gonna change. Get used to it and do the smart thing on your end. Or do the dumb thing and miss deadlines and waste electricity if that's what you want.

In case you still didn't get it.... the smart thing is to keep a small cache. Don't believe me? OK, you'll learn eventually. Or maybe you won't, whatever.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

You're correct about the cache. I have only four uploads waiting. Two Mar 25 and two Mar 26. I can crunch something else while I wait. There is always plenty of work without caching.

Ok, the maintenance is done. Server components are on-line again. Thank you for you patient.

Regarding BoincTasks - What does it mean when the field "CPU%" goes red.

This is just to warn you that (average) CPU % for this task may be 'unusual'

For CPU task - is red if CPU % < 50 (usualy they are near 100)
(means something else (e.g. game, GPU task) consumes too much CPU ; or CPU is in Throttle mode)

For GPU task - is red if CPU % > 50 (usualy GPU task is not good to consume much CPU but may be normal for some apps/tasks) (may also mean the app is hang in some loop)

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Or perhaps it's caused by 4 to 6 hours of unannounced maintenance that has ballooned into 40 to 60 hours, or will it become 4 to 6 DAYS!

Don't get bogged down by one projects problems, ALL projects have problems after all they are using computers! The key is to be able to dance around the problems, shuck and jock, dance like a butterfly, moon walk, whatever it takes to keep on crunching. If this projects doesn't have any units just have a backup project and your pc's won't even notice an outage. Instead of having 100% as for how much you crunch for a backup project change that to zero percent and it will ONLY get work when your primary project(s) are out. Boinc can be VERY flexible, it can be a flat out pain in the butt too!, but if you learn to use the options we have it CAN be made to work your way.

---

Hi Dagorath,


Sorry, didn't see your answer before.. And I've been away for a couple of days..

It's not a flag it's an option. And I'm not talking about uploading results, I'm talking about reporting results. The uploading of the actual result file always happens as soon as the task completes. The reporting of the result is a separate event and BOINC client may postpone that for rather long periods of time, too long for my tastes.

If you're looking at this page from the BOINC User Manual then scroll down past the section on logging flags to the section on options.

Thanks for showing this to me. I was looking for info here. I did manage to get it to work though. Mr. Ageless actuaaly did tell me to look at the "wiki" instead! Thanks for the help:
http://boincfaq.mundayweb.com/index.php?language=1&view=91

---

Project Headless CLI Linux Multiple GPU Boinc Servers
Ubuntu Server 14.04.1 64bit
Kernel 3.13.0-32-generic
CPU's i5-4690K
GPU's GT640/GTX750TI
Nvidia v.340.29
BOINC v.7.2.42

Or perhaps it's caused by 4 to 6 hours of unannounced maintenance that has ballooned into 40 to 60 hours, or will it become 4 to 6 DAYS!

Crap happens so get used to it because it ain't gonna change. Get used to it and do the smart thing on your end. Or do the dumb thing and miss deadlines and waste electricity if that's what you want.

In case you still didn't get it.... the smart thing is to keep a small cache. Don't believe me? OK, you'll learn eventually. Or maybe you won't, whatever.

Wrong! Depending what you mean by a small cache (IIRC 0.1 days?). It is not necessarily the smart thing to have a small cache & certainly it is not dumb (check your attitude dude!) to have a bigger cache!, but obviously you don't want such a large cache that your going to bust deadlines.

As I've explained to you before some of us like to focus on (predominantly) one project at a time.
So knowing that projects do go down for maintenance etc from time to time I set a cache of 3 days (+1). I rode out this outage, no problems, & was continuously crunching A@H so no downtime for it :), oh & I was nowhere near the deadlines either. The trick is (for single project crunching) is to set a 3day cache once you have a steady output so BOINC can get a sensible amount of WUs, that works for A@H anyway, maybe for a project with shorter deadlines (are their any?) you'd want to lower that.

Also, once in a while a project is forced to cancel several thousand tasks which unfortunately sometimes trashes results waiting to upload

Yea, but that's rare, very rare AFAIK so I would just chalk that upto 'shit happens' ;)

As far as losing results to crashes on our own machines, baring a HDD death (what are the chances of a hard drive death the same time as project outage? Very unlikely!). I've only ever lost WUs which were currently being crunched, & that's mainly on the GPU which I caused to crash.

(I've O/ced my GPU to 850 MHz which it's fine for crunching weeks at a time for, but play a YouTube video & it BSOD instantly! Lol, (wth?) So I have to hit 'set default clocks' in AMD GPU tool, then o/c to CCCs max of 775 MHz & it plays them fine, of course that means I have to remember to do that! And if I don't then the GPU WU in progress errors out & rarely a CPU task too).

---

Team AnandTech - SETI@H, Muon1 DPAD, Folding@H, MilkyWay@H, Asteroids@H, LHC@H, POGS, Rosetta@H, Einstein@H,DHPE & CPDN

Main rig - Ryzen 3600, 32GB DDR4 3200, RX 580 8GB, Win10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR3 1866, HD 7870 XT 3GB(DS), Win7