There is another maintenance running. The last maintenance wasn't complete so I had to start it today. It will be done within 4 - 6 hours.

Radim Vančo (Kyong)

As far as I can see the server has been shut down for maintenance since at least 11:15 CET (10:15 UTC), and you post the announcement now, 13:30 CET (12:30 UTC) ??

Time to recharge the flux capacitor Marty, or that delorean you need to use for posting timely announcements in advance won't work.

As far as I can see the server has been shut down for maintenance since at least 11:15 CET (10:15 UTC), and you post the announcement now, 13:30 CET (12:30 UTC) ??

Time to recharge the flux capacitor Marty, or that delorean you need to use for posting timely announcements in advance won't work.

At least he is telling us something, MANY other projects don't say a thing and we crunchers must just wonder. Believe me when I say he IS one of the better communicators!!

I thought it won't take so much time today but unfortunately it will. I really don't have much time for everything even the scheduling the maintenance is now problem for me. But it has to be done. If it wouldn't be necessary I would have announce it in advance.

Mikey
Totally agree! At least we got some info :)

Dutch
Blimey give him a break, he posted only a few hours after.

There is another maintenance running. The last maintenance wasn't complete so I had to start it today. It will be done within 4 - 6 hours.

Radim Vančo (Kyong)

Touch wood & cross fingers, I guess you didn't ;)

---

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

Hi Mr. Vanco ;)


Will it be about say an hour to finish updating or will it be a lot more than 2 hours? I've got some work I would like to uploade before "nuking" this mahine back to the stone age ;)

It's not more than about 40 work units, so not much is lost ;)

Keep up the good work!!!
.

---

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

Is this why we cannot upload completed tasks?
Have been waiting all day for them the report back to the servers.
Thanks

Hi bcavnaugh ;)

Yes, this is why.. The server is being updated and this means we can't deliver tasks which is done. We can't get new work either. But these guys are serious guys, if it wasn't necessary, they wouldn't have done it ;)

Just try once in a while, and you'll see the server running again ;)

BTW, your system will try to update automatically. If you are not using any scripts which does this in another way, the boinc-client/boinc-manager will try again and again ;)

Have a nice one ;)

.

---

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

Hi bcavnaugh ;)

Yes, this is why.. The server is being updated and this means we can't deliver tasks which is done. We can't get new work either. But these guys are serious guys, if it wasn't necessary, they wouldn't have done it ;)

Just try once in a while, and you'll see the server running again ;)

BTW, your system will try to update automatically. If you are not using any scripts which does this in another way, the boinc-client/boinc-manager will try again and again ;)

Have a nice one ;)

.

Thanks DanHansen@Denmark I was not sure if it was Ubuntu or not it was the 1st time I ran this project on my Ubuntu Desktop running 7.2.42.

I was not sure if it was Ubuntu or not it was the 1st time I ran this project on my Ubuntu Desktop running 7.2.42.

It was not ;) And welcome to the Linux-party! BTW BoincTasks/BoincView will show you all your computers running Boinc. This is pretty nice, when you are using different platforms. I guess you know about this, just wanted to be sure ;)

Have a nice one...
.

---

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

Maintenance happens, no sense whining about it, deal with it instead. I don't like getting caught with a bunch of results waiting for upload and wondering if they'll make deadline or become wasted effort but instead of whining at the admin over an issue I can deal with myself, I keep an extremely small cache and put "return results immediately" in a cc_config.xml in the BOINC data directory.

Also, once in a while a project is forced to cancel several thousand tasks which unfortunately sometimes trashes results waiting to upload. That's another good reason to keep a miniscule cache and return results immediately. The longer tasks and results sit around on my system the greater the chance something bad is going to happen to them so I get just a few at a time, crunch 'em and send 'em on their way ASAP.

I like a big "switch between applications every" setting, at least 4 hours. It seems that way I get fewer tasks sitting there with only 30 minutes remaining. It's disappointing to see a task that ran for 5 hours and needed only 30 more minutes get canceled, lost to a disk crash, power outage, whatever.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

Maintenance happens, no sense whining about it, deal with it instead.

"...these guys are serious guys, if it wasn't necessary, they wouldn't have done it.."

I keep an extremely small cache and put "return results immediately" in a cc_config.xml in the BOINC data directory

I like a big "switch between applications every" setting, at least 4 hours. It seems that way I get fewer tasks sitting there with only 30 minutes remaining.

1. Which flag do you use for uploading results ASAP? And will this not mean a lot of traffic for the update server/update servers?
2. Does it really change anything to change "switch between applications every" setting to a larger setting? My CPU's does most jobs in 1.5 hours and the GPU's in 2.5 hours.. Maybe changing the setting to 3 hours would be good for me!?

Thanks for the tip!
.

---

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 am sorry to keep you waiting. The maintenance is still running, my estimated time was wrong. There are all files being processed so I can't say the exactly time. But it will still take a few hours.

Maintenance happens, no sense whining about it, deal with it instead.

"...these guys are serious guys, if it wasn't necessary, they wouldn't have done it.."

Agreed.

I keep an extremely small cache and put "return results immediately" in a cc_config.xml in the BOINC data directory

I like a big "switch between applications every" setting, at least 4 hours. It seems that way I get fewer tasks sitting there with only 30 minutes remaining.

1. Which flag do you use for uploading results ASAP? And will this not mean a lot of traffic for the update server/update servers?

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.

So, as an option the statement to turn the option on goes between <option> tags thusly:

<cc_config>
   <log_flags>
   </log_flags>
   <options>
      <report_results_immediately>0|1</report_results_immediately>
   </options>
</cc_config>

The notion that reporting results immediately goes back years to when project servers ran on single core CPUs, disks were slow and disk caches were small. The concern was not so much the increased network traffic as the additional database access overhead. Recording 3 results in the database requires only a wee bit more overhead than recording 1 result so it was preferred that BOINC client should wait until at least 3 results were ready to report.

If BOINC client were programmed to wait until there are 3 results ready and then report them, I would go along with that but instead it can wait until there are over 20 ready. I can't accept that and since it's my system and my electricity I run it the way I like it and report them immediately. Several admins have told me it's not a problem for them and that seems sensible given how much faster disks and CPUs are these days. If it does become a problem then the issue will get reexamined and there will eventually be code changes. That might mean the "report results immediately" option gets replaced by an option similar to "report results when 3 are ready" or it might mean they remove any such option completely, it's hard to say what the BOINC devs might do. Not that what they do is always the final verdict anyway. If they remove the "report tasks immediately" option I'll just run a script that monitors the ready reports and forces an update when I want.

2. Does it really change anything to change "switch between applications every" setting to a larger setting? My CPU's does most jobs in 1.5 hours and the GPU's in 2.5 hours.. Maybe changing the setting to 3 hours would be good for me!?

That setting pertains to all projects. I have some that run 6, 10 or even 24 hours so so 4 works for me. If the longest task you crunch from any project is 2.5 hours then 3 might be better for you. I have no proof, rational or empirical, to support my claim that a large switch time helps anything. It just seems to me I see fewer tasks with a mere 30 minutes remaining, it might not actually be so.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

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

Preliminary Change Log 7.2.35 --> 7.2.36:
<snipped>
• client: report tasks within 1 hour of completion... instead of 24. Better user experience at the expense of slightly increased server load.

---

BOINC blog

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

Preliminary Change Log 7.2.35 --> 7.2.36:
<snipped>
• client: report tasks within 1 hour of completion... instead of 24. Better user experience at the expense of slightly increased server load.

Hey I had totally missed that, that's why my pc's don't have lots of units waiting for me to return them anymore. THANKS!!

Absolutely!

We have info. :)
All is cool.

Big Thank You, Kyong. For all your great work.

---

Melwen - child of the Fangorn Forest

Thanks, MarkJ! A 1 hour wait is not a problem, it's a good compromise. I'll be updating and removing the "report immediately" option from cc_config.xml soon.

---

BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux

I am sorry to keep you waiting. The maintenance is still running, my estimated time was wrong. There are all files being processed so I can't say the exactly time. But it will still take a few hours.

hmmmm - a few hours...

... your definition of "a few" ?

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.