Questions and Answers :
Unix/Linux :
[linux] BOINCmgr hangs while connecting - suggestions?
Message board moderation
Author | Message |
---|---|
ralphw Send message Joined: 7 May 99 Posts: 78 Credit: 18,032,718 RAC: 38 |
I installed new BOINC client/manager apps, in an attempt to get S@H working. (I get persistent HTTP download errors, and no workunits for SETI at home since Jan 2012. I run PrimeGrid and Einstein on my Box - which runs Ubuntu 10.04LTS with zero problems.) I went from 6.10.45 to 6.12.34 (x86_64-pc-linux-gnu) and all seemed well until I stopped the science apps from the boinc_mgr gui, Upon reboot, nothing is working. Normally, my init scripts restart BOINC, but now I have no running science apps, and boincmgr can't connect to the client, as if it's not able to complete its startup and start listening. Here's what "ps" shows: boinc 12996 0.0 0.0 94096 17608 ? SN 06:39 0:00 /usr/bin/boinc --check_all_logins --redirectio --dir /var/lib/boinc-client ralphw 13280 98.4 0.1 333656 24080 ? Rl 06:41 2:15 /usr/bin/boincmgr 1) boinc should be running as the "boinc" user 2) The boincmgr application runs as whoever is logged in So why can't they connect? If there's a permission problem, what else do I need to clean up? (I may have run boinc as root during my earlier testing of the new BOINC binaries. Shouldn't rebooting clean things up, or is there some manual step I must run) (last few lines of stdoutdae.txt - 27-Feb-2012 06:52:08 [PrimeGrid] [work_fetch] NVIDIA GPU: fetch share 0.00 LTD -2279.52 backoff dt 0.00 int 0.00 (susp via GUI) (no new tasks) 27-Feb-2012 06:52:08 [Milkyway@Home] [work_fetch] overall LTD -869793.96 27-Feb-2012 06:52:08 [SETI@home] [work_fetch] overall LTD 0.00 27-Feb-2012 06:52:08 [orbit@home] [work_fetch] overall LTD 0.00 27-Feb-2012 06:52:08 [LHC@home 1.0] [work_fetch] overall LTD 0.00 27-Feb-2012 06:52:08 [climateprediction.net] [work_fetch] overall LTD 0.00 27-Feb-2012 06:52:08 [Einstein@Home] [work_fetch] overall LTD -119.38 27-Feb-2012 06:52:08 [PrimeGrid] [work_fetch] overall LTD -14863.12 27-Feb-2012 06:52:08 [---] [work_fetch] ------- end work fetch state ------- 27-Feb-2012 06:52:08 [---] [work_fetch] No project chosen for work fetch Here's stderrdae.txt Unrecognized XML in CONFIG::parse_options: http_transfer_timeout_bps Skipping: 1 Skipping: /http_transfer_timeout_bps Unrecognized XML in CONFIG::parse_options: http_transfer_timeout_bps Skipping: 1 Skipping: /http_transfer_timeout_bps Unrecognized XML in CONFIG::parse_options: http_transfer_timeout_bps Skipping: 1 Skipping: /http_transfer_timeout_bps Unrecognized XML in CONFIG::parse_options: http_transfer_timeout_bps Skipping: 1 Skipping: /http_transfer_timeout_bps Unrecognized XML in CONFIG::parse_options: http_transfer_timeout_bps Skipping: 1 Skipping: /http_transfer_timeout_bps Unrecognized XML in LOG_FLAGS::parse: guirpc_debug Skipping: 0 Skipping: /guirpc_debug gstate.init() failed Error Code: -180 getaddrinfo: Connection timed out I can run other commands, such as "boinccmd --get_project_status". That returns quite a bit of data, but I suspect it's all from local XML files, and not actually hitting the network. |
ralphw Send message Joined: 7 May 99 Posts: 78 Credit: 18,032,718 RAC: 38 |
Problem was resolved after two more reboots, as well as changing permissions on files in /var/boinc-client. The getaddrinfo failure still seems odd, I've never seen that fail before. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.