Latest boinc version thread

[rcofell]

How about posting the log files (stdoutdae.txt and stderrdae.txt in the base BOINC directory) as I mentioned?

I suppose the other thing is you could also just try running the client back-end (boinc.exe) from a console prompt instead to debug it, for which you can attach the '-allow_remote_gui_rpc' argument to let any host/IP attempt to authenticate and control via the GUI RPC functionality.

I just checked, and attempts by non-defined hosts (not in 'remote_hosts.cfg' that is) show up when running the client back-end from a console prompt, so that should show up in those log files as well, when running as a service that is. It doesn't look like clients using the wrong GUI RPC password show up though, so that makes things a little harder to diagnose.

I've been running versions 6.1.0 and 6.3.0 for quite some time with BoincView, that is with Windows XP and Linux respectively, so BoincView definitely works with the 6.x releases.

[D_A]

I don't bother with the passwords, and so wipe the contents of that file. I just block the ports at my network firewall.

[Jaco]

Has anyone got boincview running with the 6.x clients?

Regards,
Bob

Nope , I have the same problem and I can't figure it out (apart from re-installing an older version like 5.10.45)

[123bob]

How about posting the log files (stdoutdae.txt and stderrdae.txt in the base BOINC directory) as I mentioned?

I suppose the other thing is you could also just try running the client back-end (boinc.exe) from a console prompt instead to debug it, for which you can attach the '-allow_remote_gui_rpc' argument to let any host/IP attempt to authenticate and control via the GUI RPC functionality.

I just checked, and attempts by non-defined hosts (not in 'remote_hosts.cfg' that is) show up when running the client back-end from a console prompt, so that should show up in those log files as well, when running as a service that is. It doesn't look like clients using the wrong GUI RPC password show up though, so that makes things a little harder to diagnose.

I've been running versions 6.1.0 and 6.3.0 for quite some time with BoincView, that is with Windows XP and Linux respectively, so BoincView definitely works with the 6.x releases.

Sorry rcofell, I read your other post too fast. I'll do as you say and report back here in a bit. Thx.

Good to hear you have it running on your rigs. I can at least go from there.

Regards,
Bob

EDIT #1: Well, the plot thickens....I looked for the files stdoutdae.txt and stderrdae.txt in the Boinc program directory, and they are not there. Neither are the sub-folders "projects" or "slots"..... I seem to remember at install time that it gave some options for putting stuff in different places. I just let it use the defaults. I looked over my whole machine trying to find them, but did not see them. Boinc is running and crunching WUs, so they must be somewhere... I'll investigate further and may re-install and see what happens....

[Jaco]

That's it !

Look under c:\documents and settings\All Users\Application data\Boinc

Thanks Bob and rcofell

[123bob]

That's it !

Look under c:\documents and settings\All Users\Application data\Boinc

Thanks Bob and rcofell

Was going to edit my previous one to report that I found it under c:\programdata\boinc. I'll edit this one to report on the progress. I bet if I stuck the remote_hosts file in here, it would work....... Stupid me.....


EDIT: IT WORKED!! Thanks rcofell! If you hadn't asked about the files, I may never have caught that the specific data files were somewhere other than the boinc program directory. I feel somewhat stupid now, but I'm really happy boincview still works. I rely on it to manage the farm....

Thanks much,
Bob

[D_A]

That's why I install BOINC from a direct download instead of the repositories. The folder is where I put it, not spread out all over the file system.

[123bob]

That's why I install BOINC from a direct download instead of the repositories. The folder is where I put it, not spread out all over the file system.

I install from download too. It just appears that this new version allows you to put the boinc data in a different place than the program. I just blew through the default choices when I installed and didn't catch that the locations were different. I'll likely re-install just to get it configured the same as all my other machines.

Thanks everyone for your help. This was driving me nuts.

Bob

[RAMMIE]

.... I'll likely re-install just to get it configured the same as all my other machines.

Thanks everyone for your help. This was driving me nuts.

Bob

The BOINC folder in ApplicationData has to stay there to work.You cannot move or combine this with the Boinc folder in Program Files.

[D_A]

That's not what he's suggesting. In an earlier post Bob mentioned that he was given the choice of where to put the data folder during the installation process. He is now considering re-installing from scratch and selecting to have everything in the same overall directory.

[RAMMIE]

That's not what he's suggesting. In an earlier post Bob mentioned that he was given the choice of where to put the data folder during the installation process. He is now considering re-installing from scratch and selecting to have everything in the same overall directory.

Won't work.They have to be seperate.

[D_A]

I would have thought if the installer gave the option then it would work.

In linux they live quite happily in the same directory ie BOINC (linux is a completely different animal I know)

[123bob]

You are both right. I always had the boinc data files in the boinc program directory on my client version 5.10.45 installs. They must have changed this at some point though because this new version won't allow me to choose the same directory. The easy work around was to create a sub-directory called "data" in the program files boinc directory. So, it's all back in one folder now, with the new "data" subfolder. Screenies to show what I'm saying....


This shows the 6.2.19 screen I blew past when I originally installed. Note the it sets the directory differently. Note the "advanced" button.


Pushing the button gives this screen....I set both path's equal using the "change" button.



Doing this now gives...


I went back in and added a "data" subdirectory and it took it. Now my path to the gui_rpc_auth and such is c:\program files\boinc\data. It's happy, I'm happy.

Now all is happy with this final screenie....

Note that this is 6.4.5. While I was messing with this, 6.4.5 went to the "recommended" Status at the boinc page..... I figured I'd put it in since I was re-installing anyway...


Regards,
Bob

[emuexport]

Can WCG use CUDA in the latest version as on the BOINC page it says:

For BOINC 6.4.5 and later

"Use your NVIDIA GPU for scientific computing"

"Projects with CUDA applications include:

GPUgrid.net
Of course, you can attach to other projects too; BOINC will keep both your CPU and GPU busy."

Anyone tried it? I only have one CUDA card atm but this sure would generate more points if it worked.

[123bob]

Can WCG use CUDA in the latest version as on the BOINC page it says:

For BOINC 6.4.5 and later

"Use your NVIDIA GPU for scientific computing"

"Projects with CUDA applications include:

GPUgrid.net
Of course, you can attach to other projects too; BOINC will keep both your CPU and GPU busy."

Anyone tried it? I only have one CUDA card atm but this sure would generate more points if it worked.

+1 here. Same question.

I don't much care what app I run on it, just so it's a worthwhile cause.

I only have a few rigs that have decent enough cards in them to run on, but I'll crunch those if I can. Heck, I'd crunch with the washing machine if I could figure out how to get a client running on it....

[D_A]

w00t! 6.4.5 is the recommended version for x86_64

[emuexport]

Guess I'll have to try it out later then! and report back.

[Lu523]

I await your results.

[D_A]

Ok, tried it on two opterons (185 and 170) and an Athlon XP. Benchmarks have dropped a few % across all machines so far.have to wait and see what happens to completion times or if this is just all about CUDA.

[123bob]

With 5.10.45 and 6.4.5 on a dual Harper rig @3.6gig, I get the following for benches

5.10.45 - 3661/10744

6.4.5 - 3658/10781

Nearly equal and the completion times look very close to the same.

I've had 6.4.5 running for about 15 hours now and it has been running smoothly. One thing of note is that I don't seem to have as big a WU queue as I should. I'll have to look into the preferences on that. I have it set to the same profile as my other machines. I may have to reset preferences on the client.

I'm not doing anything with the CUDA stuff yet. I have to find out if it works and can contribute yet.

Regards,
Bob

[D_A]

I don't have any CUDA enabled cards, so that part is wasted on me.

[bowman]

http://www.nvidia.com/object/io_1229516081227.html

According to NVIDIA, SETI and Einstein have now added CUDA support, but still no mention of WCG.

Can't say the gains are shockingly huge though.. GTX 280 2 times faster than a stock i7 965? Perhaps they only use FP64.

The good news is that unlike certain CUDA DC projects it's both Win and Lin.

[D_A]

Actually ...

Hi!
We are indeed thinking of GPGPU at least for desktop supercomputer-type (not grid-enabled) computing for the moment.

As a matter of fact, our reserach group is working on accelerating Q-Chem using GPGPUs (We have ~10-20X speedup right now). The Karplus group is also working on accelerating CHARMM with GPGPU.

In principle, in the near future these GPGPU codes could be grid-enabled as they become available. At the moment, our Q-Chem port is still in beta, and it would take a while to stabilize.

You can see the abstract of our GPGPU publication here:
http://pubs.acs.org/doi/abs/10.1021/jp0776762

- The Clean Energy Project team

CUDA support in the science apps at WCG is coming.

[Sunfire]

6.5.0 beta is available for:

OS X

OS X command line version

Edit: Windows version 6.5.0 beta arrived:

Windows 32 bit

Windows 64 bit

[illidan]

is 6.4.5 good replacement for 5.10.45 at 32bit system? should i change the 5.10.45?