For remote client connections you will want this in cc_config.
<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
Along with:
gui_rpc_auth.cfg
remote_hosts.cfg

The arrow on the file means the file 'lives' in a different location. A Shortcut in Windows, a symbolic link in Unix.
So /etc/boinc-client is where the file is.

Try ... sudo gedit /etc/boinc-client/remote_hosts.cfg
I'm not sure if gedit is the Pi text editor though ...

There is always the Repository work around to edit files ... for a short time until BOINC locks it's privileges again.
sudo chmod -R 0777 /var/lib/boinc-client ... might need /* on that.
That makes all the files 'world' writable/editable to everyone :)

Hi Brent,

Will this: <allow_remote_gui_rpc>1</allow_remote_gui_rpc> allow me to Remote Desktop Connection into my Pi and control BOINC from there? That is what I am looking to do. Right now I have no control, except command line commands, over the apps and the boinc-client. I can only shut them down with the commands. I want to do this through BOINC Manager in RDC. I can do it with my other 2 Pis which were attached to SETI differently then with my first Pi.

On the Pi I can use "sudo nano..." for editing. It's in my other post previous to this one.

Have a great day! :)

Siran

[edit]
I forgot to mention that I checked cc_config.xml on one of my other Pis and it is the same as the one on my first Pi I'm working on. <allow_remote_gui_rpc>1</allow_remote_gui_rpc> is not in it.
[/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

One of the problems with the repository versions of BOINC is the restrictions in editing as you have found because of BOINC group ownership. If BOINC is installed in a directory of your choosing in /home, then you are the owner and you have all the editing authorization to do whatever you want. The other issue is that the repository versions of BOINC install a boinc.service that automatically loads the client. It doesn't have to be that way if you don't want it. Any version of BOINC can be started just by starting the manager which starts the client. I don't want BOINC to run automatically since I do some overclocking prep work before I start the Manager. Or when I need to do other maintenance on the host and not wanting BOINC to be using resources.

A pi is not a desktop host per se so not applicable to my examples. I just have the Manager icon docked on my Desktop and any time I want to run BOINC, a simple click starts the client and manager. When I want to stop BOINC, the Exit BOINC command under the File menu stops both the client and manager.

You could always just move the repository BOINC files in their two separate directories into a new directory of your own choosing in your /home directory.

You might like to read about the procedure here.
http://alpheratz.net/how-to-move-boinc-data-directory-linux/
Those instructions continue with starting the client service. But again, you don't have to automatically restart the service if you don't want to.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

One of the problems with the repository versions of BOINC is the restrictions in editing as you have found because of BOINC group ownership. If BOINC is installed in a directory of your choosing in /home, then you are the owner and you have all the editing authorization to do whatever you want. The other issue is that the repository versions of BOINC install a boinc.service that automatically loads the client. It doesn't have to be that way if you don't want it. Any version of BOINC can be started just by starting the manager which starts the client. I don't want BOINC to run automatically since I do some overclocking prep work before I start the Manager. Or when I need to do other maintenance on the host and not wanting BOINC to be using resources.

A pi is not a desktop host per se so not applicable to my examples. I just have the Manager icon docked on my Desktop and any time I want to run BOINC, a simple click starts the client and manager. When I want to stop BOINC, the Exit BOINC command under the File menu stops both the client and manager.

You could always just move the repository BOINC files in their two separate directories into a new directory of your own choosing in your /home directory.

You might like to read about the procedure here.
http://alpheratz.net/how-to-move-boinc-data-directory-linux/
Those instructions continue with starting the client service. But again, you don't have to automatically restart the service if you don't want to.

Hi Keith,

I don't think I used a repository version of BOINC. I used terminal and typed "sudo apt-get install boinc". Now that I think about it, I guess that would be a repository version. On PCs with Linux, in the past, I did install using the repository in a GUI window, I didn't use the terminal. I used a KVM between it and my Windows PC for access.

I'll check out that link later, I'm getting a headache from trying to get this figured out. My head feels like it has cotton in it. Probably does. lol ;)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
is for BOINC Manager Remote RDC, not remote desktop ... not the same. Also used for programs like BoincTasks.

I want to do this through BOINC Manager in RDC. I can do it with my other 2 Pis which were attached to SETI differently then with my first Pi.

How are they different? Different networking? IF they are on a different sub net (192.168.x.x) that would be an issue.

It's a bit confusing on this end when you are talking about 3 different computers at once, each with different issues.

---

<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
is for BOINC Manager Remote RDC, not remote desktop ... not the same. Also used for programs like BoincTasks.

I want to do this through BOINC Manager in RDC. I can do it with my other 2 Pis which were attached to SETI differently then with my first Pi.

How are they different? Different networking? IF they are on a different sub net (192.168.x.x) that would be an issue.

It's a bit confusing on this end when you are talking about 3 different computers at once, each with different issues.

Hi Brent,

Let me try to clear up the confusion:

Raspberry Pi #1: I had a tiny 5 inch LED display for a display. I got Linux installed and then BOINC. BOINC Manager would not bring up a list of projects to attach to, the list was something... different. After many tries I got the notion to access the Pi with a remote BOINC Manager on my main PC. I opened a second BM window and logged into BOINC on the Pi and I got the list to attach to projects. I attached to SETI. I did this on the 10th of December. I closed the Pi BM window on my main and tried to enter BM on the Pi. It would not connect to the client. So I monitored BOINC on the Pi with a BM window on my main.

I strung an HDMI cable between my monitor and the Pi and using the input switch on the monitor I could go between my Pi and my main. I had to have a second mouse and keyboard for the Pi. They are wireless. I could do anything BUT deal with BOINC in that fashion. On to the next...

Raspberry Pi #2: Having been able to access the first Pi though HDMI on my monitor I decided to do everything: install Linux, install BOINC and attach to SETI. That worked out great, fantastic. I then tried RDC and found that I could do everything including deal with BOINC through the RDC connection. GREAT!!! No second keyboard and mouse required. On to the next...

Raspberry Pi #3: Since I could have an RDC connection to my second Pi, I decided to do everything from there: install Linux, install BOINC, and attach to SETI.

I discovered that I could not access my second 2 Pis with a second BM window on my main. It would not make the connection to either Pi, not like it does for my first Pi. So, I decided that I wanted my first Pi to be accessed and dealt with the way my second 2 Pis are, through RDC. This is my dilemma since yesterday.

I hope this may have cleared up the cobwebs so you can see things as I do. ;) I have my Ethernet cable plugged into a 4 port switch and my main PC and the 3 Pis are on the switch. My router assigns IP addresses to each device. Will <allow_remote_gui_rpc>1</allow_remote_gui_rpc> allow me to shut down BOINC and the client on the Pi? If so, I could live with that. I just want some kind of control of BOINC on Pi #1 besides monitoring it. Pis #2 and #3 are good to go! :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I hope this may have cleared up the cobwebs so you can see things as I do. ;) I have my Ethernet cable plugged into a 4 port switch and my main PC and the 3 Pis are on the switch. My router assigns IP addresses to each device. Will <allow_remote_gui_rpc>1</allow_remote_gui_rpc> allow me to shut down BOINC and the client on the Pi? If so, I could live with that. I just want some kind of control of BOINC on Pi #1 besides monitoring it. Pis #2 and #3 are good to go! :)

Each of the pi's should have the <allow_remote_gui_rpc>1</allow_remote_gui_rpc> set in each pi's cc_config file. This allows remote procedure calls to the host from another computer. A remote procedure call could be a shutdown command via the gui or the boinccmd command line tool. I use BoincTasks to control my farm from my desktop daily driver computer. It runs on WINE very well in Linux.

Don't know whether your desktop is light enough and you have enough memory to run WINE or not. Not the only solution but one of the easiest to install and use.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Regarding Pi 1 ... sudo apt-get install boinc ... that caught my eye before.
I seem to recall using that install method it is something like:
sudo apt-get install boinc boincmgr
I don't think you have a Manager on that computer.
I will see if I can find more on that ...

Pi 3, no Desktop sharing? As I read you ...
Did you enable it?
From the Pi Menu, search for Desktop Sharing
And make sure it is turned on :)

Pi 2 and 3, as Keith said, <allow_remote_gui_rpc>1</allow_remote_gui_rpc> ... for all.
EDIT: And Restart BOINC.

---

Yea, Boinc Individual Installs are explained here
sudo apt-get install boinc-manager
should fix it - I think.

I hope this may have cleared up the cobwebs so you can see things as I do. ;) I have my Ethernet cable plugged into a 4 port switch and my main PC and the 3 Pis are on the switch. My router assigns IP addresses to each device. Will <allow_remote_gui_rpc>1</allow_remote_gui_rpc> allow me to shut down BOINC and the client on the Pi? If so, I could live with that. I just want some kind of control of BOINC on Pi #1 besides monitoring it. Pis #2 and #3 are good to go! :)

Each of the pi's should have the <allow_remote_gui_rpc>1</allow_remote_gui_rpc> set in each pi's cc_config file. This allows remote procedure calls to the host from another computer. A remote procedure call could be a shutdown command via the gui or the boinccmd command line tool. I use BoincTasks to control my farm from my desktop daily driver computer. It runs on WINE very well in Linux.

Don't know whether your desktop is light enough and you have enough memory to run WINE or not. Not the only solution but one of the easiest to install and use.

Hi Keith,

My desktop (main) is running Windows 10, not Linux... yet. ;)

I compared the cc_config.xml file on Pi #1, the one not quite to my liking, to the one on one of the other Pis that is working the way I want. The files were identical. The <allow_remote_gui_rpc>1</allow_remote_gui_rpc> was not in the cc_config.xml file on the Pi that works as I want.

I can use RDC (Remote Desktop Connection, Micro$ofts version of VNC) on my main and log into all 3 Pis and do things like edit files or use the browser, but I can only control BOINC, shut it and the apps down using BOINC Manager on the second and third Pis which I got running in a different manner than my first Pi. Using this "/etc/init.d/boinc-client stop" in terminal, in RDC connected to the first Pi, is the only way to shut BOINC down on the first Pi. I want to be able to use BOINC manager to shut BOINC down on Pi 1 like I can with Pis 2 and 3 in an RDC connection from my main.

I added <options> <allow_remote_gui_rpc>1</allow_remote_gui_rpc> </options> to the cc_config.xml file on the Pi giving me headaches and it made no difference. I still cannot get BOINC Manager to connect to the client when in RDC.

I'm getting closer to the notion that I will need to finish out WUs on the troubled Pi, detach from SETI, uninstall BOINC and then reinstall BOINC the way I did it with the other 2 Pis and then reattach to SETI. I have one more idea I'm gonna try before I decide to take drastic measures to get the Pi to do as I want.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Regarding Pi 1 ... sudo apt-get install boinc ... that caught my eye before.
I seem to recall using that install method it is something like:
sudo apt-get install boinc boincmgr
I don't think you have a Manager on that computer.
I will see if I can find more on that ...

Pi 3, no Desktop sharing? As I read you ...
Did you enable it?
From the Pi Menu, search for Desktop Sharing
And make sure it is turned on :)

Pi 2 and 3, as Keith said, <allow_remote_gui_rpc>1</allow_remote_gui_rpc> ... for all.
EDIT: And Restart BOINC.

Hi Brent,

Perhaps it's slightly different for the Raspberry Pi. The Linux is Raspbian which is a derivative of Debian.

Using "sudo apt-get install boinc" installed the BOINC Manager on all 3 Pis per the instructions on this website. It works, believe me, I have the manager on all 3 Pis.

I added <options> <allow_remote_gui_rpc>1</allow_remote_gui_rpc> </options> to the cc_config.xml file, rebooted the Pi, which starts BOINC. I did this through RDC on my main. Nothing. It did not change a thing.

Please see my response to Keith earlier.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Something must not have got installed right for the Manager on Pi 1, just missing something. Try
sudo ldd /usr/bin/boinc
sudo ldd /usr/bin/boinccmd
sudo ldd /usr/bin/boincmgr
I suspect the first 2 outputs are fine, the third will say something is missing.
Compare to Pi 2 and 3 to confirm.

---

Something must not have got installed right for the Manager on Pi 1, just missing something. Try
sudo ldd /usr/bin/boinc
sudo ldd /usr/bin/boinccmd
sudo ldd /usr/bin/boincmgr
I suspect the first 2 outputs are fine, the third will say something is missing.
Compare to Pi 2 and 3 to confirm.

Hi Brent,

I ran on all 3 Pis and they are all identical. Nothing was saying something was missing on the first or any Pi.

I decided that I'm just going to finish out the WUs I have on Pi 1, detach from SETI and uninstall BOINC and reinstall and attach to SETI doing it the way I did with my third Pi, doing it from in RDC. I'll need to merge the 2 Pi 1s after reattaching. Then everything will be hunky dory.

Thank you to you and Keith for the help you've given. My first Pi was a new thing for me and I got stuff wrong with it BOINC wise. It was a learning experience. That's why my Pis 2 and 3 do as I want, everything from in RDC including controlling BOINC. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I wonder if you have 2 copies of BOINC on that PI. In your computer list you have a Pi that connected 2 days ago with v7.4.53
Do you know where that came from?

You shouldn't have to detach from the project, just reinstall. If you keep the client_state intact it should connect normally again.

---

I wonder if you have 2 copies of BOINC on that PI. In your computer list you have a Pi that connected 2 days ago with v7.4.53
Do you know where that came from?

You shouldn't have to detach from the project, just reinstall. If you keep the client_state intact it should connect normally again.

Hi Brent,

v7.4.53 is my Lenovo tablet. Yeah, it runs the same Arm architecture as my Pis do, just an earlier version. The OS, Android, should have given it away. ;)

If I can reinstall without detaching, I still have to run my supply of WUs down, right? Seems to me like a better way to go just to avoid problems for wing-persons. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I wonder if you have 2 copies of BOINC on that PI. In your computer list you have a Pi that connected 2 days ago with v7.4.53
Do you know where that came from?

You shouldn't have to detach from the project, just reinstall. If you keep the client_state intact it should connect normally again.

Hi Brent,

v7.4.53 is my Lenovo tablet. Yeah, it runs the same Arm architecture as my Pis do, just an earlier version. The OS, Android, should have given it away. ;)

If I can reinstall without detaching, I still have to run my supply of WUs down, right? Seems to me like a better way to go just to avoid problems for wing-persons. :)

Have a great day! :)

Siran

FYI If they haven't started crunching yet, just abort them and report. The server will then send them PDQ to another person.

Well yea, running out the tasks first is always a kind way of doing things.

The ldd test mostly proves that everything is there for the Manager to run, so it's likely just a silly config issue.
I was thinking, maybe make sure the rpc_cfg has localhost, and try the actual host IP address added to it.
The use the local Manager to open Computer 'localhost' with p/w from GUI_auth.
A thought.

I use BOINCtasks running on a Windows PC to control my farm. The Pi’s are all headless. No gui needed which frees up memory. You can use BOINCtasks to attach to projects and manage the BOINC side of things. I use putty on the PC to remote into each one when installing and doing OS updates, etc. You don’t need BOINC Manager to control them.

If you’ve got a Windows machine or an x64 Linux that can run wine then I would suggest you simplify and standardise the setup. When you have a number of them the last thing you want is them having different setups. I can drop you a PM about my setup process which starts with imaging the SD card (you’ll need a PC for that too).

---

BOINC blog

I use BOINCtasks running on a Windows PC to control my farm. The Pi’s are all headless. No gui needed which frees up memory. You can use BOINCtasks to attach to projects and manage the BOINC side of things. I use putty on the PC to remote into each one when installing and doing OS updates, etc. You don’t need BOINC Manager to control them.

If you’ve got a Windows machine or an x64 Linux that can run wine then I would suggest you simplify and standardise the setup. When you have a number of them the last thing you want is them having different setups. I can drop you a PM about my setup process which starts with imaging the SD card (you’ll need a PC for that too).

Greetings Mark,

2 of my Pis are working just fine with BOINC Manager through RDC (Micro$oft's equivalent to VNC). I'm not worried about memory usage; BOINC is the only thing running on them and usage is about 50%. Even if I do something on them like edit a file or whatever usage only slightly goes up. I don't use them to browse the Internet. ;) lol

My main PC is Windows 10... for now anyway.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Well yea, running out the tasks first is always a kind way of doing things.

The ldd test mostly proves that everything is there for the Manager to run, so it's likely just a silly config issue.
I was thinking, maybe make sure the rpc_cfg has localhost, and try the actual host IP address added to it.
The use the local Manager to open Computer 'localhost' with p/w from GUI_auth.
A thought.

Hi Brent,

Well, I tried to do the install again and this is what I got:

pi@Rasbpi-1:~ $ sudo apt-get install boinc
Reading package lists... Done
Building dependency tree       
Reading state information... Done
boinc is already the newest version (7.6.33+dfsg-12).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@Rasbpi-1:~ $ 

I already have BOINC shut down on the Pi. Can I copy the state file somewhere such as my home directory, uninstall BOINC, reinstall BOINC and copy the state file back to the directory it should be? I assume the data directory is /var/lib/boinc-client, correct? Since that is where the state file is.

After some Googling I found this: sudo apt-get purge boinc-manager boinc-client which gets rid of executable, config and data files. This: sudo apt-get remove boinc-manager boinc-client will only get rid of the executable files. If I go with the first I should have no problem, but going with the second I will be in the same boat as I'm in right now. Correct? :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I already have BOINC shut down on the Pi. Can I copy the state file somewhere such as my home directory, uninstall BOINC, reinstall BOINC and copy the state file back to the directory it should be? I assume the data directory is /var/lib/boinc-client, correct? Since that is where the state file is.

After some Googling I found this: sudo apt-get purge boinc-manager boinc-client which gets rid of executable, config and data files. This: sudo apt-get remove boinc-manager boinc-client will only get rid of the executable files. If I go with the first I should have no problem, but going with the second I will be in the same boat as I'm in right now. Correct? :)

Sure you can copy the client state file from /var/lib/boinc-client to another folder and then do the "apt purge boinc -y" to get rid of it before reinstalling. Seeing as you keep mentioning the remote desktop I presume you're using it to access a gui on the Pi, but if you wanted to copy it using the command line simply do the following:
cd /var/lib/boinc-client
cp client_state.xml /tmp/client_state.xml

That will make a copy into the /tmp folder.

---

BOINC blog