BOINC 7.x breaks BOINC Project Updater

[zombie67]

After upgrading BOINC, BOINC Project Updater (PBU) is spitting out the same error message you get if your password doesn't match what is in the gui_rpc_auth.cfg file. What changed with 7.x that breaks BBPU? Does BOINC 7.x use a different file for the password or something?

[Mr. Hankey]

Why upgrade?

[zombie67]

Why upgrade?

It's required for the new GPU apps (openCL) at some projects.

[Slicker]

I'll install BOINC 7.0.3 and step through the code in debug and see if I can find the problem.

[Slicker]

I found the first error. Once again, the guys at Berkeley really need to take an XML 101 course. They have invalid characters embedded in their XML. That's what happens when developers think XML is just text with < and > around it. It would be nice if they would at least read the specs: http://www.w3.org/TR/REC-xml/

Anyway, it looks like they removed or changed the project_update api call. I'm not sure which yet or if there is a workaround.

[Fire$torm]

Thank you Slicker. Too bad they don't have sense enough to hire you. But then, I guess, they would have to pay you an awful lot of money to put up with them.......

[Slicker]

It turns out that they used to use
<project_update>\a<project_url>\ahttp://a.b.c/d/</project_url>\a</project_update>\a

and now they want
<project_update>\n<project_url>\nhttp://a.b.c/d/</project_url>\n</project_update>

If they were using actual XML, they would be expecting
<project_update><project_url>http://a.b.c/d/</project_url></project_update>

and if they wanted better performance and to use less bandwidth, they would use
<project action="update" url="http://a.b.c/d/"/>

Anyway, here's a new version that works with 7.0.3:
http://boinc.thesonntags.com/collatz/download/BoincProjectUpdater_v1030.zip

[Fire$torm]

It turns out that they used to use
<project_update>\a<project_url>\ahttp://a.b.c/d/</project_url>\a</project_update>\a

and now they want
<project_update>\n<project_url>\nhttp://a.b.c/d/</project_url>\n</project_update>

If they were using actual XML, they would be expecting
<project_update><project_url>http://a.b.c/d/</project_url></project_update>

and if they wanted better performance and to use less bandwidth, they would use
<project action="update" url="http://a.b.c/d/"/>

Anyway, here's a new version that works with 7.0.3:
http://boinc.thesonntags.com/collatz/download/BoincProjectUpdater_v1030.zip

OK, call me a noob.... Is this a patch for BM 7.0.3 or its replacement?

[Slicker]

Just replace the old boincprojectupdater.exe with the new one in the zip file and it should then work with boinc 7.0.3

[zombie67]

Thanks! Is the new project updater compatible with older BOINC? Or do I need to use old with old and new with new?

[Slicker]

Thanks! Is the new project updater compatible with older BOINC? Or do I need to use old with old and new with new?

It works with the 6.10.43 client. That's the oldest one I'm currently running at home.

[zombie67]

It works with the 6.10.43 client. That's the oldest one I'm currently running at home.

Thanks! I will give it a shot this weekend!

[zombie67]

I am trying it out now. Does this mean I don't need to run two instances of it, for two projects now? That's what it looks like. If so, great!

[Slicker]

It should handle multiple project and multiple computers. If you can access them via BOINC Manager remotely, then you should be able to use BPU as well. If it doesn't let me know.

[STE\/E]

Just replace the old boincprojectupdater.exe with the new one in the zip file and it should then work with boinc 7.0.3

Works with 7.0.3 but not with 7.0.7 ... lol

[zombie67]

Works with 7.0.3 but not with 7.0.7 ... lol

It is working with 7.0.7 for me (win7 64).

[STE\/E]

It is working with 7.0.7 for me (win7 64).

Hmmmm, won't work for me on my only Win 7 64-bit Box ... :confused: ... Works on all my XP 64-bit Box's though

[Fire$torm]

Hmmmm, won't work for me on my only Win 7 64-bit Box ... :confused: ... Works on all my XP 64-bit Box's though

Though not likely, maybe your missing a Win update or more likely you have all the updates and one of them is causing the glitch?

[STE\/E]

Though not likely, maybe your missing a Win update or more likely you have all the updates and one of them is causing the glitch?

Updates :confused: I never Update any OS once it's installed ... :D

[Bryan]

Updates :confused: I never Update any OS once it's installed ... :D

Win update on a working system .... blasphemy! Never happen :))

[STE\/E]

Win update on a working system .... blasphemy! Never happen :))

lol ... Seriously I never Update the OS once it's installed, I just install SP2 then Shut off Auto Updates & any access to the Registry. I don't want Microsoft touching anything in my OS, they run just fine the way they are without any interference from Microsoft for what I use them for ...

[Bryan]

lol ... Seriously I never Update the OS once it's installed, I just install SP2 then Shut off Auto Updates & any access to the Registry. I don't want Microsoft touching anything in my OS, they run just fine the way they are without any interference from Microsoft for what I use them for ...

+1

[kaptainkarl1]

Could someone please explain the updater and how to use it for those of us who missed the class.

I have downloaded it and input what I thought was the right information but it doesn't seem to be working.

Thanks!

[STE\/E]

JUst click on Edit at the top of the Updater Window it will say add or remove host/project.

Then fill in the Host name & password & URL of the Project you want to call to, you get the password from the BOINC File Directory, it's the gpu_rpc_auth.cfg file, open it up and copy the password to the BOINC Updater.

Each computer has it's own Password so you can't use the same one for each computer.

NOTE: Seems to work for me except my Win 7 Box but it doesn't seem to keep updating any of the Box's, it will show it's Hr's behind on the Updates so I don't think it's working like it should for me anyway ...

[zombie67]

Are you talking about access to a remote machine? If so, that remote machine has to have the FW set to allow access. Also, that remote machine BOINC has to be set up to allow the incoming IP address. There is a BOINC file it has to be added to. <---I think.

[STE\/E]

The File would be the remote_hosts.cfg which all my Box's have to allow me to access them from 3 different Box's. 1 of the Box's is where I have the BOINC Updater installed on, funny thing is it's the Win 7 Box that won't Update itself with BOINCUpdater but BOINCView & BOINC Tasks both work from the Box ...

[Fire$torm]

JUst click on Edit at the top of the Updater Window it will say add or remove host/project.

Then fill in the Host name & password & URL of the Project you want to call to, you get the password from the BOINC File Directory, it's the gpu_rpc_auth.cfg file, open it up and copy the password to the BOINC Updater.

Each computer has it's own Password so you can't use the same one for each computer.

NOTE: Seems to work for me except my Win 7 Box but it doesn't seem to keep updating any of the Box's, it will show it's Hr's behind on the Updates so I don't think it's working like it should for me anyway ...

Just tried it on my desktop Win7 Home Premium x64, seems to be working.

Some things to note:
*Check your firewall, especially if your are using Windows Firewall (yuck), and add BoincProjectUpdater.exe to your allow/include list with TCP Outbound on port 31416.
*You can edit the gpu_rpc_auth.cfg in your BOINC Data directory to change the password to anything you want. I made the password for all my boxes the same which makes them easier to manage for me. Changes won't take effect until BOINC is restarted.
*If you want to manage remote hosts you may need to edit the remote_hosts.cfg file in the BOINC Data directory, for each remote system. to include the IP address of the computer used to manage remote systems.

Example:
My_Desktop <---- Name of computer used as controller
192.168.1.110 <---- Controller IP Address
127.0.0.1 <---- Loopback Address (aka Localhost) See Wikipedia for more info (Link (http://en.wikipedia.org/wiki/Localhost))

[STE\/E]

I added the Updater to the Firewall but still no go ...

[coronicus]

if its on the same host make sure to us 127.0.0.1

[Fire$torm]

I added the Updater to the Firewall but still no go ...

Hmmm, the only other thing I can think of is that it is an issue with the Remote Procedure Call (RPC) protocol, which is what BOINC uses for communication with remote hosts. Firewalls typically deny it because it is a very insecure method of data communication.

[STE\/E]

Don't have a clue here as to why it won't work on the Win 7 Box, I'm a Network Dummy so Networking for Dummy'z wouldn't even help me ... :o)

[zombie67]

if its on the same host make sure to us 127.0.0.1

This is what I use too.

[STE\/E]

if its on the same host make sure to us 127.0.0.1

Where would I enter or put that ???

[Fire$torm]

Where would I enter or put that ???

In the gpu_rpc_auth.cfg in your BOINC Data directory and add it to your firewall rules for the BOINC.exe and the updater.

[zombie67]

Where would I enter or put that ???

In Updater? In "Host". You can also use "localhost".

[STE\/E]

Okay Z that seemed to work for my Win 7 "local host" Box ... Thanks

Creating a new Firewall rule for 127.0.0.1 didn't work ... The Updater loses Contact with some of the Hosts I think, mainly because their all Wireless, so it won't Update them until I restart the Updater even if it re-makes contact before I restart it ...

[Fire$torm]

Okay Z that seemed to work for my Win 7 "local host" Box ... Thanks

Creating a new Firewall rule for 127.0.0.1 didn't work ... The Updater loses Contact with some of the Hosts I think, mainly because their all Wireless, so it won't Update them until I restart the Updater even if it re-makes contact before I restart it ...

Glad to hear its working on that box. That is why I always include it. Just so you know 127.0.0.1 = loopback = localhost. They all refer to the same thing.
The reconnect might be something trigggl can work on in the updater.

[Slicker]

you get the password from the BOINC File Directory...

Each computer has it's own Password so you can't use the same one for each computer.

You can edit it as well. [rant on]Why BOINC doesn't ask what you want it to be when installing pisses me off. DA says it is because most people only have one computer. So what. I find it a pain to have to go back after installing and rebooting to edit the password and then have to restart boinc. [/rant off]

Anyway.... Edit the gui_rpc_auth.cfg (note: gui, not gpu) with you favorite text editor (Notepad, TextPad, Notepad2, Notepad++, nano, vi, pico, etc.). The file contains only one line. That line is the boinc password on the machine. Change it to whatever you want, as short or long as you want. Stop and restart boinc. I make the password the same on all machines in my farm so I don't have to remember different passwords. If you have a secure network (e.g. are behind a firewall) you can delete the password completely so that it is an empty file. Don't delete the entire file, just blank the password.

If you want to control BOINC on the machine from some other machine, edit the remote_hosts.cfg file (or create one if it doesn't exist) and put the list of host names or IP addresses in it one per line. Don't forget 127.0.0.1 so it can always control itself. If you want to allow it to be controlled by any other computer, you can add the --remote_gui_rpc_auth startup parameter as described in the BOINC Wiki: http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely

[kaptainkarl1]

In the gpu_rpc_auth.cfg in your BOINC Data directory and add it to your firewall rules for the BOINC.exe and the updater.

All I see is gui_rpc_auth file. Is this file containing the number that I put in the host field in the updater? Or is it the password for the host in the updater?

[STE\/E]

Yes, copy the # inside gpu_rpc_auth.cfg file & paste it into the password line ... The Host Field is the Name of your Computer

[Fire$torm]

Ooops. Sorry I was tired... gpu_, gui_ it all looks the same after 18 hours up on four hours sleep :P

[zombie67]

I just discovered an issue/feature with the new version of BPU.

I have been pulling out my hair off and on, for several weeks now. It was just not possible to get it to work with mindmodeling. Just that one project, and no other. I tried everything. Finally, it occurred to me to look at the URL that was in the client_state.xml.

This is the URL I was using: http://mindmodeling.org/beta/
This is the URL in the client state (and the one that works): http://MindModeling.org/beta/

It turns out that BOINC project updater is case sensitive. Any way to make it not case sensitive?

[zombie67]

For the first time now, I am using BPU update remote machines, and am getting the following error pop up:

http://dl.dropbox.com/u/55884901/bpu.png

[Fire$torm]

Hmmm, I have used BPU remotely on two machines and never saw that. Hope its an easy fix.

[Bryan]

I saw the same error message as Z when I tied in remotely to my controlling machine.

[Fire$torm]

Maybe it is due to BM 7.x as I still run 6.10.58 on everything.

[zombie67]

Maybe it is due to BM 7.x as I still run 6.10.58 on everything.

I have no 7.x running currently. So I don't think that's the issue.

[Bryan]

I do ... 7.0.11 I like to live dangerously :))

[Duke of Buckingham]

:p I do that 7.0.11. I am much better now because I am living dangerously before I thought that I was crazy. Thanks Bryan for putting my madness in a more kind words. =))

:cool: Living dangerously seems much better than being crazy. I like it. :rolleyes:

http://globalnerdy.com/wordpress/wp-content/uploads/2007/02/living-dangerously.jpg

Cat you are living dangerously. Nice Doggys.

[Slicker]

BOINC Project Updater v1.0.4 has been released. The only change in this from v1.0.3 is that it now allows blank passwords which means it works with blank gui_rpc_auth.cfg files. You can download the latest version at: http://boinc.thesonntags.com/collatz/download/BOINCProjectUpdater_v1040.zip

[STE\/E]

I saw the same error message as Z when I tied in remotely to my controlling machine.

Same here, I just close & open the Updater a few times until the error doesn't show up anymore ...

[coronicus]

:p I do that 7.0.11. I am much better now because I am living dangerously before I thought that I was crazy. Thanks Bryan for putting my madness in a more kind words. =))

:cool: Living dangerously seems much better than being crazy. I like it. :rolleyes:

http://globalnerdy.com/wordpress/wp-content/uploads/2007/02/living-dangerously.jpg

Cat you are living dangerously. Nice Doggys.

All i see is an appetizer :))

[Duke of Buckingham]

Yeha I have to stop living that way ...

http://www.saintseton.com/images/450_BC_Hurt_Cat_080318.gif

The Dogs weren`t so nice afterall.

Maybe you should have a thread called living dangerously. We could offer that one to my friend Bryan.

http://www.hahnfamilies.com/Fun%20Stuff/Picture%20This/Images/living%20dangerously.jpg

You can come you are living dangerously also.

[coronicus]

OMG what a way to learn about gravity.

[Slicker]

For the first time now, I am using BPU update remote machines, and am getting the following error pop up:

http://dl.dropbox.com/u/55884901/bpu.png

Now that's a new one. I'm running 7.0.3 and don't get the error. Is the remote host also a 7.x.x client? Is is a blank password?

[zombie67]

Now that's a new one. I'm running 7.0.3 and don't get the error. Is the remote host also a 7.x.x client? Is is a blank password?

Nope, to both.

[Slicker]

Nope, to both.

Do you get the error when first starting up BPU or after it is running for a while?

[zombie67]

Do you get the error when first starting up BPU or after it is running for a while?

Just when starting up. And I get one or two of those pop-ups. After that, it runs normally.

[Slicker]

I have not been able to duplicate the issue, but I'm really hoping this (potential) fix solves the problem:

http://boinc.thesonntags.com/collatz/download/BOINCProjectUpdater_v1050.zip

I think that, for wireless hosts, where it may take a little longer to connect, that the grid was still updating while it was trying to automatically resize the columns. The new version starts all the threads, one per remote host, prior to trying to automaticaly adjust the columns sizes so that all the data is visiable on the grid.

[kaptainkarl1]

Not sure if this is the place for this but here goes.

I can't seem to get the updater to remember it's settings. After a reboot it comes up blank. Am I doing something wrong?

[Duke of Buckingham]

Not sure if this is the place for this but here goes.

I can't seem to get the updater to remember it's settings. After a reboot it comes up blank. Am I doing something wrong?

Yes, you are.

You are using windows aren't you?

http://punditkitchen.files.wordpress.com/2009/01/political-pictures-soldier-army-windows.jpg

[Bryan]

I have not been able to duplicate the issue, but I'm really hoping this (potential) fix solves the problem:

http://boinc.thesonntags.com/collatz/download/BOINCProjectUpdater_v1050.zip

I think that, for wireless hosts, where it may take a little longer to connect, that the grid was still updating while it was trying to automatically resize the columns. The new version starts all the threads, one per remote host, prior to trying to automaticaly adjust the columns sizes so that all the data is visiable on the grid.

Slicker I see this quite frequently on my systems. I'm remotely controlling from 1 machine with 6 satellites ... 4 are wireless. I'm running V1060 and BOINC 7.0.28. On an overnight run I might have 8 to 10 of those error messages. Is there something I can do on my end?