home page

Posts by Ingleside

1) Message boards : Number crunching : Africa v7.22 Errors (Message 51317)
Posted 633 days ago by Ingleside
Hmm, does the Africa-application have the same fatal bug as the PNW-application, with landing in the "crashes 100 times before giving-up", or is it something else going-on with just some bad wu's?
2) Message boards : Number crunching : Main web page down (Message 51131)
Posted 655 days ago by Ingleside
"Attaching isn't a problem"
for users already attached, who have an account_* file somewhere, yes "Attaching isn't a problem"

But, for new clients, who don't have such, yes it is a problem.

Makes it hard to recruit new (and old) users when they need an "account_*" file on their system already to sign up -

Maybe some kind of magic redirection from the public sites -- I have no clue.

New users can't sign up right now -- is that correct?

Well, I can't at the moment test if it's possible to make a new account, since I'm stuck at a Linux-computer with no possibility to run BOINC...

For everyone that already has an acccount, manages to find these pages and also manages to login their own account on these web-pages, it's fairly easy to make an account-file if for some reason it's not possible to just attach to by manually typing this into BOINC Manager...

Goto and use notepad (or similar) to make, as marked in bold, a file called in your BOINC data-directory.

For the contents, at the moment you'll need to use for PROJECT_URL and for WEAK_ACCOUNT_KEY you can use either the weak account-key listed on the web-page or the "normal" account-key listed on the "Your account"-page.

After successfully editing and saving, just re-start BOINC.
3) Message boards : Number crunching : Main web page down (Message 51118)
Posted 656 days ago by Ingleside
Has anyone else been able to attach since the the front page went offline? If so how?

Attaching isn't a problem, you can use to attach since they've also including the link to scheduler on this page. While the BOINC-client will complain about using this address it will still work without any problems. I've for many years been attached to the "wrong" url for a project without having any problems appart for getting the "wrong address" on scheduler-requests.

For anyone already attached but is stuck with needing to re-download master-page, a work-around is to edit the in the BOINC data-directory to use as the master-url (the 2nd. line in the file) and afterwards re-start the BOINC client.

Then the homepage is finally back, it is just to re-edit the account-file to use as master_url. This can be done even if you attached to the "wrong" url originally.

BTW, while attaching isn't difficult to do, I immediately hit the Linux-bug of "missing", a library so ancient it's not part of the repositories any longer meaning I've not got the foggiest idea how to install it.
4) Message boards : Number crunching : Compute Errors on Pacific North West v7.22 Tasks (Message 49593)
Posted 825 days ago by Ingleside
Last PNW to come to my machine was on 12th Feb this year. It completed.

Ok, I forgot to specify it's all the Windows-PNW-tasks crapping-out, under different OS like Linux this batch is possibly worse since this time it's an input-file-error while not sure on the source of error for the "no heartbeat"-tasks.
5) Message boards : Number crunching : Compute Errors on Pacific North West v7.22 Tasks (Message 49590)
Posted 826 days ago by Ingleside

That's because of the INITTIME error, as mentioned a few posts down.

All PNW-models now crapping-out after 30 seconds or something with a INITTIME-error is a huge improvement since the previous batches...

... since these ran-through 100 re-starts due to "no heartbeat" before crapping-out and as a "bonus" left-behind around 300 MB of garbage on the hd.

Frankly, AFAIK PNW haven't worked since the upgrade to 7.22, a version AFAIK not even beta-tested before release so I've no idea why CPDN continues releasing new PNW-garbage before they've even tried to get it working as beta.

6) Message boards : Number crunching : Project keeps resetting - any explanations? (Message 49371)
Posted 858 days ago by Ingleside
Anyway, the disk value has been typical for this machine for quite sometime, which is why I thought it was "normal." So -- I have one last question: Is it easiest to simply try a project "reset" to clean out the directory? I would dislike damaging the directory structure the way I go about wiping folders and disks... Thanks!

Reset should work.
7) Questions and Answers : Macintosh : GB added to my Time Machine backup (Message 48959)
Posted 906 days ago by Ingleside
2) Normally exclude the boinc directory tree from time capsule backups. Once a week, remove this exclusion, select "backup now" and after the backup is done, re-exclude the boinc directory tree for another week.

3) Same as 2) except suspend/shutdown boinc while the backup is taking place. (To satisfy my paranoia about doing a backup while boinc is running. )

4) Once a week suspend/shutdown boinc, copy the directory tree to a backup disk, restart boinc. The only problem of this option, is remembering to do it, and waiting around while 14 GB is being copied to the (relatively slow) backup disk so boinc activity can be resumed.

I tend to lean toward 4).

Well for hadam3p_eu-models it's a waste of time to do weekly backups, since chances are any restored backup will be of models you've already finished & reported. For hadam3p_anz the usefulness of a weekly backup is also limited so except for hadcm3n a weekly backup is mostly useless. (No idea with Moses).

A daily backup on the other hand would be much more useful. If the "Time Machine" is up to the task, I would choose option #5:

5: Exclude boinc from hourly backup. Make a separate backup-profile for BOINC, doing a daily backup of only the BOINC data-directory (including sub-directories).

If time machine can't handle #5, option #2 but done once-a-day is probably the best.
8) Questions and Answers : Wish list : Enhance scheduling/throttling strategies (Message 48958)
Posted 906 days ago by Ingleside
If you edits the BOINC-preferences locally on a computer, it's saved in a file called global_prefs_override.xml located in the BOINC data-directory.
In addition BOINC includes boinccmd located in the BOINC application-directory, this is a command-line tool to give various commands to a running BOINC-client, including reading global_prefs_override.xml

So while BOINC doesn't directly support changing %cpu-usage due to time-of-day, one method that should work is to make two small batch-files, and these batch-files you can schedule to run at a particular time in Windows.

To make the batch-files, you'll first need to make the BOINC-preferences. This can example be to make the "full"-preferences, copy global_prefs_override.xml and calling it full.xml, re-edit BOINC-preferences choosing the "low"-preference and copy global_prefs_override.xml calling it low.xml

The full-batch-file can be something like:
copy "your-boinc-data-dir\full.xml" "your-boinc-data-dir\global_prefs_override.xml"
"your-boinc-app-dir\boinccmd" --read_global_prefs_override

And the half-batch-file can be something like:
copy "your-boinc-data-dir\low.xml" "your-boinc-data-dir\global_prefs_override.xml"
"your-boinc-app-dir\boinccmd" --read_global_prefs_override

You'll need access-rights for the copying to work.
9) Message boards : Number crunching : CONVERTING TO LINUX (Message 48944)
Posted 907 days ago by Ingleside
That's a thought, but with dual boot, Jim can just switch to Windows when cpdn is out of work and run other projects with that.

Well, atleast in my experience, a project going down always happens at the wrong time, example 15 minutes before you're increasing the cache-size from 0.1 days to 5 days, or 5 minutes after leaving in the morning so computer can sit idle for many hours during the day if don't have a backup-project.

Even with "lots of work" cached for CPDN, how many bad batches has CPDN released over the years, crashing after a few seconds in a run? Not to forget, while all Hadam3p-variants for years was probably the most stable models, after PNW released a new version (AFAIK not even bothered beta-tested) all PNW-models has in my experience had a 100% error-rate. (and as a bonus these crashes has filled-up the hd leading to also the other models crapping-out due to no free disk space).

10) Message boards : Number crunching : CONVERTING TO LINUX (Message 48931)
Posted 907 days ago by Ingleside
I agree with Les: Mint is best if your Linux install is going to be used for various things. But if your box is dedicated to CPDN work (or BOINC work in general), I'd recommend 32 bit Lubuntu. Lubuntu is Ubuntu with the 'LXDE' desktop, which is very light on system resources, so it leaves more CPU for CPDN to use.

If you're only going to run CPDN under Linux using a 32-bit version is possibly the best option. But if you're also expecting other projects will be run, either due to your choise or as a backup for next time CPDN is out of work or has server-problems and can't get any new work, a 32-bit Linux doesn't look like a good choise, since for some BOINC-projects the 64-bit-applications has a significant speed-advantage.

Next 10 posts

Copyright © 2002-2016