| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Community
Forum: Chat Room
Thread: Running Boinc and BOINCTasks on Ubuntu [Resolved] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18667 Status: Offline Project Badges: 
|
For the moment, I have console access (no GUI) to an Ubuntu 14.04 server. I am able to install, attach and get BOINC running fine. Tried getting BOINCTasks working with mixed results. BOINCTasks could connect to the server but then BOINCCMD on the server would give a -1 error whatever the command. I expect it has to have something to do with how I edited the cc_config.xml and allow_gui_remote_rpc.cfg files. BOINC was shut down on the server and I used vi to edit the two files. I was in the /var/lib/boinc-client directory to edit them. I'm obviously missing something as a linux neophyte! Anyone want to point out the obvious?
---------------------------------------- Edit: DOH! I'm running BOINCTasks on a Windows machine, not the server. ---------------------------------------- [Edit 2 times, last edit by keithhenry at Nov 23, 2015 10:21:50 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
An allow_gui_remote_rpc.cfg does not and has never existed... the line
<allow_remote_gui_rpc>1</allow_remote_gui_rpc> goes into the cc_config.xml's <options> section. How much Doh will this unleash ;p |
||
|
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18667 Status: Offline Project Badges:
|
I should really watch my late night posts!
---------------------------------------- Yes, adding that option to the cc_config.xml file allows rpc's from any machine that uses the right password. The OTHER file is the one you put the password in. VI wouldn't save the changes saying both files were read-only. Had to sudo vi to be able to save the changes. That's probably part of my problem. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Late or early, maybe put the other ear on the pillow for an extra snooze, for other readers, the password file is actually called gui_rpc_auth.cfg and -often- other than putting a blank in the file on Ubuntu ** leads to continued inability to connect... ;P)
** Wild guess, on my installation the password file is symlinked to the /var/lib/boinc-client folder from /etc/boinc-client, which possibly breaks things. Whilst on Windows the pw file is pre-filled with a random 32 character hex hash, the Ubuntu does come as blank, but then I've never ever used the .sh installation, always the ready to run from repo. |
||
|
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18667 Status: Offline Project Badges:
|
Oh dear! The wierdness is growing! Actually, after editing the two files in /var/lib/BOINC-client (including putting a password in gui_rpc_auth.cfg). BOINCTasks connected. However, you symlink statement seems to be stimulating some rather ancient memory cells. That's true for both files (being symlinked). I expect that's why VI was saying they were read-only. I'm betting I need to edit them over in /etc/boinc-client!
---------------------------------------- |
||
|
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: 
|
I always find that editing remote_hosts.cfg and adding the url of the windows rig with bonctasks on it is enough. I am using Linux Mint so the gui_rpc_auth.cfg file is already empty.
----------------------------------------(double check my naming here ...there may be some capitals in filenames)  |
||
|
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18667 Status: Offline Project Badges:
|
Thanks Rob! I have it working now. Left the password file blank like it came. Updated the cc_config.xml file over in /ect/boinc-client via a sudo vi to add the allow_remote_gui_rpc option.
----------------------------------------OldChap, I'll consider switching to that as it does seem more secure. Taking things a step at a time for now. EDIT: BTW, what do you guys use for the refresh rate in BOINCTasks? I wouldn't think processing the RPCs would take much but that could add up if it's often enough with enough machines. ---------------------------------------- [Edit 1 times, last edit by keithhenry at Nov 23, 2015 10:24:10 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
View: Manual 6 sec
Tasks: 120 sec History: Min 60 sec, Max 240 sec These work for lowest possible load without missing results being logged properly to history (sometimes tasks will sit whitelisted as waiting on an ack from the server till the next connect). If you feel the password has any added value, or hardlisting the device IPs/Urls (how you do that?), in remote_hosts, fine. I'm trusting the hardened router firewall [SE-Linux based] to the outside world for that to not ever happen, and then BOINC is sandboxed itself on top. |
||
|
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18667 Status: Offline Project Badges:
|
View: Manual 6 sec Tasks: 120 sec History: Min 60 sec, Max 240 sec These work for lowest possible load without missing results being logged properly to history (sometimes tasks will sit whitelisted as waiting on an ack from the server till the next connect). If you feel the password has any added value, or hardlisting the device IPs/Urls (how you do that?), in remote_hosts, fine. I'm trusting the hardened router firewall [SE-Linux based] to the outside world for that to not ever happen, and then BOINC is sandboxed itself on top. Thanks again Rob. I had set view at 10 seconds but dropped it to 5 not long after. Haven't messed with the other two as I haven't seen a need yet. As for security, yea, it's very unlikely. Still, these days, a fairly simple one-off that adds more security can't hurt. We've had a few pretenders (running with multiple usernames, their own team, conversations with themselves in a team thread - hey it was that much more crunching that got done despite the wierdness) and wackos (stealing usernames - that's what you get for using obvious passwords though) and such over the years here at WCG. Besides, no telling what direction the hackers, virus writers and other nut cases will take in the future. Folks do lock their doors these days. Why make it easy? |
||
|
|
|