It looks like you lost the S5R2 task that was still in the pipeline. Honestly I didn't expect people to still have one of these, and the app_info.xml isn't prepared for this.
BM
*blush* the lost task was a S5R2 task indeed, and it was processed with the SR52 client and S5R2 app_info.xml
Oh yes, don't we all love this error... In your BOINC directory, there should be a file called "gui_auth_cfg" (or similar, can't check right now). This contains a random hexadecimal key. Open the file with a text editor of your choice (I think you need root for that) and copy the key. Then go into BOINC manager, advanced, select computer. As computer you type in "localhost". Then you paste the key into the "password" window. Now you should be able to connect to the manager.
Hi Annika! Me, again.
I first want to thank you for your help. Unfortunately, it seems that the file you mentioned is missing from my setup. I un-installed and then re-installed BOINC, but the file still didn't show up. (I verified this by doing a "find" search on the whole hard drive.)
If I download an older version from one of the BOINC port sites and install it manually, the file does get created. But, that's an old text-based app, and its file won't work with the newer BOINC from the FreeBSD ports.
For now, though, I'll need to let it go. I had to rob the keyboard and mouse from this machine to use on one of my other boxes. (I'm in serious need of some KVM switches.)
the file i have in my boinc directory is gui_rpc_auth.cfg if this helps any.
If I remember correctly, I think that I performed a search for 'gui*', so that I would find everything that started with "gui". It's been about a week or so since I messed with it, so I could be mistaken. Anyway, I'll take a look at it later, when I can access that machine, again.
the file i have in my boinc directory is gui_rpc_auth.cfg if this helps any.
If I remember correctly, I think that I performed a search for 'gui*', so that I would find everything that started with "gui". It's been about a week or so since I messed with it, so I could be mistaken. Anyway, I'll take a look at it later, when I can access that machine, again.
The gui_rpc_auth.cfg file will only be present if you chose to allow this machine's boinc client to be controlled "remotely" through remote procedure calls. I think this is something you normally specify at install time - I don't remember since I don't do "normal" installs :). It's very easy to create this file with a normal text editor and all it should contain is the "password" you wish to use when connecting to the local client from a remote manager. Seeing as the person using the remote manager has to type in the password each time, choose someting nice and simple rather than using the default 32 character string, provided you don't have security issues like being on an insecure network.
If you want to get rid of a 32 char default, just edit the file to your liking and stop and restart the local boinc. You will then be using the new password.
Well Gary, I don't think you can specify if you want remote control if you do a "normal" install. I remember nothing of that sort from either the Windows installer, the Linux shell script, Debian/Ubuntu package or FreeBSD port ;-) I guess it's part of the concept that BOINC can be controlled remotely.
Just something I wanted to add ;-) apart from that, very good explanation!
Well Gary, I don't think you can specify if you want remote control if you do a "normal" install....
Yes, you are quite right. Having reminded myself, it's not something you do at installation but rather at runtime.
By default, BOINC will allow only the local manager to communicate with the local client. If you want remote control you need to use the flag -allow_remote_gui_rpc when you start BOINC and this will create gui_rpc_auth.cfg containing a default 32 char password if one doesn't already exist. You can avoid this by creating your own file containing your own password and putting it in place before BOINC is started. One of these files is part of my home-grown installation template so I never have to worry about some obscure default password which would be different for each different machine.
Well Gary, I don't think you can specify if you want remote control if you do a "normal" install....
Yes, you are quite right. Having reminded myself, it's not something you do at installation but rather at runtime.
By default, BOINC will allow only the local manager to communicate with the local client. If you want remote control you need to use the flag -allow_remote_gui_rpc when you start BOINC and this will create gui_rpc_auth.cfg containing a default 32 char password if one doesn't already exist. You can avoid this by creating your own file containing your own password and putting it in place before BOINC is started. One of these files is part of my home-grown installation template so I never have to worry about some obscure default password which would be different for each different machine.
Well, this gives me something to try, at least. Hopefully, I'll be able to get to it in a few days, and let you know the results.
RE: RE: I lost one
)
*blush* the lost task was a S5R2 task indeed, and it was processed with the SR52 client and S5R2 app_info.xml
RE: Oh yes, don't we all
)
Hi Annika! Me, again.
I first want to thank you for your help. Unfortunately, it seems that the file you mentioned is missing from my setup. I un-installed and then re-installed BOINC, but the file still didn't show up. (I verified this by doing a "find" search on the whole hard drive.)
If I download an older version from one of the BOINC port sites and install it manually, the file does get created. But, that's an old text-based app, and its file won't work with the newer BOINC from the FreeBSD ports.
For now, though, I'll need to let it go. I had to rob the keyboard and mouse from this machine to use on one of my other boxes. (I'm in serious need of some KVM switches.)
the file i have in my boinc
)
the file i have in my boinc directory is gui_rpc_auth.cfg if this helps any.
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
RE: the file i have in my
)
If I remember correctly, I think that I performed a search for 'gui*', so that I would find everything that started with "gui". It's been about a week or so since I messed with it, so I could be mistaken. Anyway, I'll take a look at it later, when I can access that machine, again.
RE: RE: the file i have
)
The gui_rpc_auth.cfg file will only be present if you chose to allow this machine's boinc client to be controlled "remotely" through remote procedure calls. I think this is something you normally specify at install time - I don't remember since I don't do "normal" installs :). It's very easy to create this file with a normal text editor and all it should contain is the "password" you wish to use when connecting to the local client from a remote manager. Seeing as the person using the remote manager has to type in the password each time, choose someting nice and simple rather than using the default 32 character string, provided you don't have security issues like being on an insecure network.
If you want to get rid of a 32 char default, just edit the file to your liking and stop and restart the local boinc. You will then be using the new password.
Cheers,
Gary.
Well Gary, I don't think you
)
Well Gary, I don't think you can specify if you want remote control if you do a "normal" install. I remember nothing of that sort from either the Windows installer, the Linux shell script, Debian/Ubuntu package or FreeBSD port ;-) I guess it's part of the concept that BOINC can be controlled remotely.
Just something I wanted to add ;-) apart from that, very good explanation!
RE: Well Gary, I don't
)
Yes, you are quite right. Having reminded myself, it's not something you do at installation but rather at runtime.
By default, BOINC will allow only the local manager to communicate with the local client. If you want remote control you need to use the flag -allow_remote_gui_rpc when you start BOINC and this will create gui_rpc_auth.cfg containing a default 32 char password if one doesn't already exist. You can avoid this by creating your own file containing your own password and putting it in place before BOINC is started. One of these files is part of my home-grown installation template so I never have to worry about some obscure default password which would be different for each different machine.
Cheers,
Gary.
RE: RE: Well Gary, I
)
Well, this gives me something to try, at least. Hopefully, I'll be able to get to it in a few days, and let you know the results.
Many thanks!
@Bernd-- It took longer
)
@Bernd--
It took longer than I had hoped, but I finally got your FreeBSD app to run on my DesktopBSD machine. We'll see how it works out.
The first pair of results is
)
The first pair of results is in, and another pair is in progress. It's looking good, so far.