Thread 'BOINC manager on Gentoo can't connect to the host.'

Message boards : Questions and problems : BOINC manager on Gentoo can't connect to the host.
Message board moderation

To post messages, you must log in.

AuthorMessage
Peter Humphrey

Send message
Joined: 25 Nov 13
Posts: 30
United Kingdom
Message 67608 - Posted: 9 Feb 2016, 12:20:11 UTC

After a clean installation of sci-misc/boinc-7.4.42-r1 on my Gentoo box, but keeping all the existing project data, I find that boincmgr cannot connect to localhost. I find these entries in the error log:

$ grep lib64 /var/lib/boinc/stderrdae.txt
boinc: /usr/lib64/libssl.so.1.0.0: no version information available (required by boinc)
boinc: /usr/lib64/libcurl.so.4: no version information available (required by boinc)
boinc: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by boinc)
boinc: /usr/lib64/libssl.so.1.0.0: no version information available (required by boinc)
boinc: /usr/lib64/libcurl.so.4: no version information available (required by boinc)
boinc: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by boinc)

I think this means that boinc is expecting a different version of openssl and of curl, but it was compiled on this machine so it should be looking for the openssl and curl that are here. (It would be helpful if these error-log messages were time-stamped; I can't tell whether these two sets of errors came from the same or different invocations.)

# ldd /usr/bin/boinc
linux-vdso.so.1 (0x00007ffe74fb2000)
libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f2e8166c000)
libssl.so.1.0.0 => /usr/lib64/libssl.so.1.0.0 (0x00007f2e813f6000)
libcrypto.so.1.0.0 => /usr/lib64/libcrypto.so.1.0.0 (0x00007f2e80fb7000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f2e80db3000)
libz.so.1 => /lib64/libz.so.1 (0x00007f2e80b9d000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f2e80981000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/libstdc++.so.6 (0x00007f2e80672000)
libm.so.6 => /lib64/libm.so.6 (0x00007f2e8036e000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/libgcc_s.so.1 (0x00007f2e80157000)
libc.so.6 => /lib64/libc.so.6 (0x00007f2e7fdbc000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2e818ce000)


Boinc, openssl and curl are all at the latest versions in the Gentoo tree. These are the USE flags they use:

# emerge -pv boinc openssl curl
--->8
[ebuild R ] dev-libs/openssl-1.0.2f::gentoo USE="asm tls-heartbeat zlib -bindist -gmp -kerberos -rfc3779 -sctp -static-libs {-test} -vanilla" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="(sse2)" 0 KiB
[ebuild R ] net-misc/curl-7.45.0::gentoo USE="ipv6 ssl -adns -http2 -idn -kerberos -ldap -metalink -rtmp -samba -ssh -static-libs {-test} -threads" ABI_X86="(64) -32 (-x32)" CURL_SSL="openssl -axtls -gnutls (-libressl) -nss -polarssl (-winssl)" 0 KiB
[ebuild R ~] sci-misc/boinc-7.4.42-r1::gentoo USE="X -cuda -static-libs" 0 KiB

I tried remerging openssl with +rfc3779 but it didn't help.

How can I fix this?
ID: 67608 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 67627 - Posted: 9 Feb 2016, 21:22:33 UTC - in response to Message 67608.  

It would be helpful if these error-log messages were time-stamped


I think those are coming from loader, nothing we can do about timestamps.

Could you move stderrdae.txt and stdoutdae.txt to some backup location and then restart the client and post here anything that appears in those files. Also check syslog to see if the client crashes or anything like that.

BTW. You could tell the package maintainer to update BOINC to 7.6.23 (but not later, there was some untested and unfinished code checked into the 7.6 branch yesterday).
ID: 67627 · Report as offensive
Peter Humphrey

Send message
Joined: 25 Nov 13
Posts: 30
United Kingdom
Message 67844 - Posted: 17 Feb 2016, 10:54:15 UTC - in response to Message 67627.  

Sorry about the delay, but I've had a hardware problem: I think the RAM was fading with age, had been for over a year, and had introduced errors in all sorts of places. So I've rebuilt the whole system on new RAM, which has taken a few days, this being a Gentoo box.

I also cleaned out the whole boinc partition and started afresh, calling "boinc attach_project <URL> <key>" on each project.

Whatever got fixed along the way seems to have fixed my problem with boinc too. Except for one thing: ATLAS@home can't connect to the local host; it says "Communication with VM Hypervisor failed." And when I log in via kdm I get a pop-up notice saying the VirtualBox kernel service is not running. I'm looking into that now.

My newly built system has been running for a few days now with nothing in stderrdae.txt and nothing untoward in stdoutdae.txt, so it looks like this thread can be closed. Thanks for your help anyway.
ID: 67844 · Report as offensive

Message boards : Questions and problems : BOINC manager on Gentoo can't connect to the host.

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.