Message boards : Questions and problems : boinccmd --get_tasks gives read failure
Message board moderation
Author | Message |
---|---|
Send message Joined: 5 Mar 17 Posts: 3 |
Hi All, I have just recently started with boinc and decided to help a bit to various projects as I think the idea is really cool. Unfortunately I am fighting to set it up on a headless old hardware. I am using a Zotac ZBOX HD-ID11 as hardware and running an Ubuntu 16.04 on it. Originally I simply wanted the server version, but later I needed to add the desktop due to the fights. And here are my findings: * CASE1 - If I install the boinc client and manager and start the manager and let it run constantly on the server (so no headless mode) then everything works perfectly fine and stable! On top of that I can do what I really want and check the status of the processing via SSH. I log in and execute the "boinccmd --get_tasks" command as many times as I want. * CASE2 - If I just run my ubuntu in a headless mode and no gui login is happening (the startup starts the boinc client) then after a while my task checks via SSH starts to hung and will answer with read failure. someone@zotac:/var/lib/boinc-client$ boinccmd --get_tasks Operation failed: read() failed someone@zotac:/var/lib/boinc-client$ telnet 192.168.0.3 31416 Trying 192.168.0.3... Connected to 192.168.0.3. Escape character is '^]'. ^CTerminated someone@zotac:/var/lib/boinc-client$ After switching on some extra logging I see that in the first case the boinc manager is basically constantly firing the requests to the client. Is it possible that the lack of these rpc calls will switch off or cause the boinc client to misfunction...? 05-Mar-2017 23:43:27 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply> <msgs> <msg> <project></project> <pri>1</pri> <seqno>12806</seqno> <body> [gui_rpc] GUI RPC reply: '<b' 05-Mar-2017 23:43:27 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request> <get_results> <active_only>0</active_only> </get_results> </boinc_gui_rpc_request> ' What is also strange that in the headless mode the actual tasks which are executed become defunct: someone@zotac:/var/lib/boinc-client$ sudo ps -ef | grep 17809 boinc 17809 17808 0 21:38 ? 00:00:02 /usr/bin/boinc --dir /var/lib/boinc-client boinc 17885 17809 43 21:38 ? 00:25:32 [wcgrid_fahv_vin] <defunct> boinc 17886 17809 28 21:38 ? 00:16:57 [wcgrid_fahv_vin] <defunct> boinc 17887 17809 43 21:38 ? 00:25:24 [wcgrid_fahv_vin] <defunct> boinc 17888 17809 96 21:38 ? 00:56:49 ../../projects/www.worldcommunitygrid.org/wcgrid_fahv_vina_7.34_x86_64-pc-linux-gnu -jobfile FAHV_1002343_3j3y-_b-P4_Rigid_12585.job -inputfile FAHV_1002343_3j3y-_b-P4_Rigid_12585.zip -seed 1132837364 someone 18122 1566 0 22:37 pts/0 00:00:00 grep --color=auto 17809 I am still fighting and trying to understand the problem via various combinations. If any of you experienced this issue please let me know. It would also be great if you could give me a hint what could cause this Many thanks! |
Send message Joined: 13 Jun 14 Posts: 81 |
Does sudo boinccmd --get_tasks work? |
Send message Joined: 5 Mar 17 Posts: 3 |
Hi, No unfortunately that also did not work. It remains also stucked like without sudo.... Peter |
Send message Joined: 8 May 10 Posts: 90 |
Consider enabling debugging switches to cc_config.xml of yours. <task_debug/> and <slot_debug/> might be a good start. Also showing logs might be worth it. I'm counting for science, points just make me sick. |
Send message Joined: 5 Oct 06 Posts: 5137 |
Consider enabling debugging switches to cc_config.xml of yours. <task_debug/> and <slot_debug/> might be a good start. Also showing logs might be worth it.I'd suggest gui_rpc_debug too. Although he's not asking about the actual GUI (BOINC Manager), boinccmd uses the same rpc calls to query the client. |
Send message Joined: 5 Mar 17 Posts: 3 |
Hi All, After some fighting I think I have figured out what could be wrong. Initially when I have installed my ubuntu version then I have allowed home folder encryption. After removing this the same ubuntu version seems to be working completely fine and stable with boinc. I do not need to log in and it operates in headless server mode. I am not 100% sure whether really this was the issue, but for me it looks this solved the problem on the same hardware and software like before. Thanks, Peter |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.