| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
vcobz
Cruncher Joined: Sep 24, 2010 Post Count: 12 Status: Offline |
Thank you to all who answered and tried helping me.
I gaveup on Fedora mainly due to other reasons. Primarilly SuSE studio being the real head turner and things just work. But in redhats defense and all boffins who guessed it was my fault and not the OS's ten points. I have returned to confirm what i bellieve the chief cause of my issues and maybe anyone new or daft to linux like me. Make sure you copy the contents of the gui_rpc_auth.cfg and do as the fedora install says enter that string of data in as your password when connecting to localhost and things comes to life. You may find that you have to start from command line initially but after it's fired up connection manager and found the net and started it's magic your away. OpenSuSE is my happy medium currently but that technique should work on redhat and some others. Those bashing they're heads on tables trying to get it to work remember firewall plays a major part also but if thats all sussed and you still have problems make sure client is running in the background then try fireup manager otherwise you'll get the disconnected everytime. Hope that helps someone persistance pays of don't let it beat you the people here are mega helpfull but theres only so much they can do the rest is up to you oh and the OS and hardware in question ;-) Happy crunching really looking forward to helping the clean energy project. Wish they would do win etc client wise these users would love to help crunch packets to. It's a conspiracy :P the only ones able to crunch for clean energy is the nuclear power stations themselves ;-) kidding kidding easy easy lol |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The real daft thing is that you don't need to enter the password (On Windows or Ubuntu for sure). Entering "localhost" in the hostname field would have completed the password field automatically. Even dafter, leaving both fields blank and just hitting OK would have connected the BOINC Manager to the "localhost" core client, provided of course that the core client is already running. Of course, that is if there are rights and the Firewall is not blocking localhost traffic over IP 127.0.0.1 with RPC calls made over port 31416.
----------------------------------------Happy Crunching.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|