You can use the gui_rpc_auth and remote_hosts files OR the cc_config method. The cc_config method allows any computer to connect and so is considered less secure. You have to restart the BOINC client on Linux (a service restart simply issues a reread config files command). Sometimes you have to restart BOINCtasks to get it to find machines. I even resort to an “ipconfig /flushdns” command on the Win7 machine to get it to see them.
I have an iptables firewall on Linux crunchers because I don’t trust my domestic grade router to stop anything. It probably does but I am not relying on it. My BOINCtasks has passwords for each cruncher as it gives an extra layer of security.
The 31416 port not being read sounds like a firewall problem. The port is being blocked. You can go into Windows Firewall and open that port up.
Yes you need to have a cc_config to use the <allow_remote_gui_rpc>1</allow_remote_gui_rpc> tag. All you need to do to create it is to use the Manager and set a logging flag other than a default ones in the Event Log Diagnostics Flags in the menu and it will create a fully populated cc_config.xml file. I like adding the sched_ops_debug flag because it shows how much work is requested at every connection in the log. Edit the <allow_remote_gui_rpc>1</allow_remote_gui_rpc> option in the front of the file and change the tag from 0 to 1.
Restart BOINC to read the file again or use the Re-Read config files in the Manager menus.
Okay THAT'S my problem, I do not have that in the cc_config files that I do have right now, I will do that today!!
The 31416 port not being read sounds like a firewall problem. The port is being blocked. You can go into Windows Firewall and open that port up.
Yes you need to have a cc_config to use the <allow_remote_gui_rpc>1</allow_remote_gui_rpc> tag. All you need to do to create it is to use the Manager and set a logging flag other than a default ones in the Event Log Diagnostics Flags in the menu and it will create a fully populated cc_config.xml file. I like adding the sched_ops_debug flag because it shows how much work is requested at every connection in the log. Edit the <allow_remote_gui_rpc>1</allow_remote_gui_rpc> option in the front of the file and change the tag from 0 to 1.
Restart BOINC to read the file again or use the Re-Read config files in the Manager menus.
Okay THAT'S my problem, I do not have that in the cc_config files that I do have right now, I will do that today!!
Thanks!!
Nope that only worked on one of the Linux machines, some of the other machines showed up but have a lightening bolt next to their name or ip address. Most say "not connected" but a couple say "password" in the Status column. I also added a 'remote_hosts.cfg' file to each machine so only my main machine can see it and not any outside ones.
The lightning bolt icon on a computer name in the left panel means either the host is not currently running BOINC or there is a connection problem to the host. Again look to Windows firewall application and make sure Port 31416 is opened to applications.
Can you ping any of the Linux devices from the Windows host? That proves basic connectivity.
The password in the Status column indicates the BT program isn't finding the Linux host because of a password problem. Either the password in wrong or unknown. You can click your mouse cursor on the ***** field and it will show you the password. You can then enter the correct password directly in that field and hit Enter. Restart BT to make it poll through the list of computers again.
The lightning bolt icon on a computer name in the left panel means either the host is not currently running BOINC or there is a connection problem to the host. Again look to Windows firewall application and make sure Port 31416 is opened to applications.
Can you ping any of the Linux devices from the Windows host? That proves basic connectivity.
The password in the Status column indicates the BT program isn't finding the Linux host because of a password problem. Either the password in wrong or unknown. You can click your mouse cursor on the ***** field and it will show you the password. You can then enter the correct password directly in that field and hit Enter. Restart BT to make it poll through the list of computers again.
I got 2 more to show up by reentering the password for each one, for some reason most were blank, I will have to make sure the port is open tomorrow. I have not tried to ping them yet but will do that tomorrow too.
You've been a great help and I REALLY do appreciate it!!
Looks like you are making slow progress Mikey. Keep at it. BT is really great to use once it is fully initialized with your computers list.
I think if you had started from scratch with all the passwords set on each host with the remote_hosts file set for your Windows BT host and then used the Find Computers dialog with the password set in the Search field it would have found all your Linux hosts on first try.
Looks like you are making slow progress Mikey. Keep at it. BT is really great to use once it is fully initialized with your computers list.
I think if you had started from scratch with all the passwords set on each host with the remote_hosts file set for your Windows BT host and then used the Find Computers dialog with the password set in the Search field it would have found all your Linux hosts on first try.
I hope so, I was able to ping the Linux pc's with no problem so it's down to opening the port which I will do today at some point, my wife has appts for me so it will have to be after those. I've also been going thru my router and assigning the current ip address of each pc as that pc's permanent ip address everytime it asks for a new one. I could have done it on each pc but this way seems easier. It takes affect after the next reboot of the router.
UPDATE: Short-lived success! Yesterday I got LUbuntu Linux 18.04 loaded and, after going down a few rabbit holes and climbing a steep-ish learning curve, got E@H running tasks on my RX 570. This morning I installed my RX 460 and got that running E@H (after a meandering through a couple more rabbit holes), but the system seemed to be rather hot running the two cards at their default settings. The ol' host was pulling 400W at the wall, which is the limit of my power supply (what's that smell?). As I was looking up how to undervolt or power limit AMD GPUs in Linux, my PSU gave up the ghost (mit spritzen und sparken!).
So, my new questions (and perhaps better put in a new thread?) are:
What's the likelihood that something other than the PSU is fried? In other words, would it be prudent to buy a new PSU to try and revive the host?
How does one adjust AMD GPU card parameters under Linux? Is there a Linux/Ubuntu equivalent to AMD's Global Wattman or MSI Afterburner? Are there command line settings for tweaking GPUs?
Ideas are not fixed, nor should they be; we live in model-dependent reality.
Did you ever try the
)
Did you ever try the BOINCToolbox64 application? Here is the forum webpage on how to use it.
https://efmer.com/boinctasks-add-computers/
Keith Myers wrote:You can use
)
You can use the gui_rpc_auth and remote_hosts files OR the cc_config method. The cc_config method allows any computer to connect and so is considered less secure. You have to restart the BOINC client on Linux (a service restart simply issues a reread config files command). Sometimes you have to restart BOINCtasks to get it to find machines. I even resort to an “ipconfig /flushdns” command on the Win7 machine to get it to see them.
I have an iptables firewall on Linux crunchers because I don’t trust my domestic grade router to stop anything. It probably does but I am not relying on it. My BOINCtasks has passwords for each cruncher as it gives an extra layer of security.
BOINC blog
Keith Myers wrote:The 31416
)
Okay THAT'S my problem, I do not have that in the cc_config files that I do have right now, I will do that today!!
Thanks!!
mikey wrote:Keith Myers
)
Nope that only worked on one of the Linux machines, some of the other machines showed up but have a lightening bolt next to their name or ip address. Most say "not connected" but a couple say "password" in the Status column. I also added a 'remote_hosts.cfg' file to each machine so only my main machine can see it and not any outside ones.
The lightning bolt icon on a
)
The lightning bolt icon on a computer name in the left panel means either the host is not currently running BOINC or there is a connection problem to the host. Again look to Windows firewall application and make sure Port 31416 is opened to applications.
Can you ping any of the Linux devices from the Windows host? That proves basic connectivity.
The password in the Status column indicates the BT program isn't finding the Linux host because of a password problem. Either the password in wrong or unknown. You can click your mouse cursor on the ***** field and it will show you the password. You can then enter the correct password directly in that field and hit Enter. Restart BT to make it poll through the list of computers again.
Keith Myers wrote:The
)
I got 2 more to show up by reentering the password for each one, for some reason most were blank, I will have to make sure the port is open tomorrow. I have not tried to ping them yet but will do that tomorrow too.
You've been a great help and I REALLY do appreciate it!!
mikey
Looks like you are making
)
Looks like you are making slow progress Mikey. Keep at it. BT is really great to use once it is fully initialized with your computers list.
I think if you had started from scratch with all the passwords set on each host with the remote_hosts file set for your Windows BT host and then used the Find Computers dialog with the password set in the Search field it would have found all your Linux hosts on first try.
Keith Myers wrote:Looks like
)
I hope so, I was able to ping the Linux pc's with no problem so it's down to opening the port which I will do today at some point, my wife has appts for me so it will have to be after those. I've also been going thru my router and assigning the current ip address of each pc as that pc's permanent ip address everytime it asks for a new one. I could have done it on each pc but this way seems easier. It takes affect after the next reboot of the router.
UPDATE: Short-lived success!
)
UPDATE: Short-lived success! Yesterday I got LUbuntu Linux 18.04 loaded and, after going down a few rabbit holes and climbing a steep-ish learning curve, got E@H running tasks on my RX 570. This morning I installed my RX 460 and got that running E@H (after a meandering through a couple more rabbit holes), but the system seemed to be rather hot running the two cards at their default settings. The ol' host was pulling 400W at the wall, which is the limit of my power supply (what's that smell?). As I was looking up how to undervolt or power limit AMD GPUs in Linux, my PSU gave up the ghost (mit spritzen und sparken!).
So, my new questions (and perhaps better put in a new thread?) are:
What's the likelihood that something other than the PSU is fried? In other words, would it be prudent to buy a new PSU to try and revive the host?
How does one adjust AMD GPU card parameters under Linux? Is there a Linux/Ubuntu equivalent to AMD's Global Wattman or MSI Afterburner? Are there command line settings for tweaking GPUs?
Ideas are not fixed, nor should they be; we live in model-dependent reality.
Prudence be damned - I just
)
Prudence be damned - I just bought a new PSU from a local shop. Will know in a day or two whether anything else was fried.
Ideas are not fixed, nor should they be; we live in model-dependent reality.