| 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: 10
|
|
| Author |
|
|
madd1n
Cruncher Joined: Feb 1, 2006 Post Count: 7 Status: Offline Project Badges:
|
I am using Gentoo Linux 3.3.8 with KDE. I recently re-installed BOINC because winter is coming and I can use the extra warmth from some extra CPU cycles. :P
Anyway, on first run BOINC and its manager successfully started, I managed to attach to projects and received WUs which were then worked on. After I rebooted my machine, however, I couldn't find a way to connect the manager and the BOINC client anymore. It was still running, I could see the work unit processes in the process list and my CPU was running hot as expected, but the manager and client didn't communicate and I was unable to change this by pressing "Select computer" or doing any of the things I found online. After the workunits were obviously done, no new ones have started running. Just now I tried again in order to properly describe its behaviour. When I start the Manager, the status bar says "Connecting to localhost" for a while, then changes to "Disconnected". After pressing "Select computer", not entering anything and pressing Enter, I am presented with a message saying the client unexpectedly exited three times. Choosing to try again doesn't yield any result ("Disconnected", again). Could someone please point me in any helpful direction? |
||
|
|
a_mobile_humanist
Cruncher Joined: May 20, 2011 Post Count: 34 Status: Offline Project Badges:
|
Does the Event Log show any relevant entries?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi madd1n,
My own experience with a fast exiting core client is that an uninstall and new install is needed. Had this on Ubuntu, suspecting the permissions were not properly created. How to test: Set 2 terminal windows. In one do a top -u boinc In the second, navigate to where BOINC application is installed, and type sudo service boinc start Watch what happens in the first terminal top view. In theory you first should see the daemon start and when it has work, the work unit applications. If it fails to stick, the boinc daemon disappears again within seconds. |
||
|
|
madd1n
Cruncher Joined: Feb 1, 2006 Post Count: 7 Status: Offline Project Badges:
|
Watch what happens in the first terminal top view. In theory you first should see the daemon start and when it has work, the work unit applications. If it fails to stick, the boinc daemon disappears again within seconds. Boinc starts and stays there. No work units, as expected. If I now start the manager, it just sits there saying "Disconnected". Manually selecting localhost does nothing. It doesn't even try to connect. About the event log: It's empty. Edit: I am currently reinstallling the BOINC package to see if that helps. [Edit 1 times, last edit by madd1n at Oct 4, 2012 7:02:03 PM] |
||
|
|
madd1n
Cruncher Joined: Feb 1, 2006 Post Count: 7 Status: Offline Project Badges:
|
No such luck. Reinstalled it. Same as above.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is the stdoutdae.txt file empty(?), for that's where the event log messages are stored? If the BOINC Manager is not connected the event log view stays empty.
You can always try using boinccmd to attach WCG, but running boinccmd --state would tell you what else is going on. Most everything you can do with BOINC Manager can be done with the boinccmd tool: http://boinc.berkeley.edu/wiki/Boinccmd |
||
|
|
madd1n
Cruncher Joined: Feb 1, 2006 Post Count: 7 Status: Offline Project Badges:
|
Is the stdoutdae.txt file empty(?), for that's where the event log messages are stored? If the BOINC Manager is not connected the event log view stays empty. You can always try using boinccmd to attach WCG, but running boinccmd --state would tell you what else is going on. Most everything you can do with BOINC Manager can be done with the boinccmd tool: http://boinc.berkeley.edu/wiki/Boinccmd Interesting. The event log file does not report any errors. 04-Oct-2012 21:26:20 [---] No config file found - using defaults Well okay, there's always the CLI, but that wouldn't really qualify as a solution to the problem "My boinc manager doesn't work".. Edit: boinccmd --status says: Can't connect to local host. [Edit 1 times, last edit by madd1n at Oct 4, 2012 8:10:04 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Did ask you if BOINC was shown in the top view. Can't be [but just very briefly] as between startup and unload there were 26 seconds closing with:
04-Oct-2012 21:26:47 [---] Exit requested by user This is why neither the boinccmd tool can give a status report. |
||
|
|
madd1n
Cruncher Joined: Feb 1, 2006 Post Count: 7 Status: Offline Project Badges:
|
Did ask you if BOINC was shown in the top view. Can't be [but just very briefly] as between startup and unload there were 26 seconds closing with: 04-Oct-2012 21:26:47 [---] Exit requested by user This is why neither the boinccmd tool can give a status report. As I said, BOINC was shown in top for as long as I kept it running. Still, no connection was possible. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Beyond me. If you delete the gui_rpc_auth.xml and set the remote all rpc then anyone with sudo boinccmd should be able to get some output back from the core client daemon. Check again in the stdoutdae.txt. If the exit requested by user still shows as last entry than the core client is *not* running.
This is a link to the Gentoo install manual (Written by a guy who does know his Linux stuff): http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Gentoo . Been toying with stuff on Ubuntu, and never ran into this kind of issue. |
||
|
|
|