| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Scheduler request failed: SSL connect error |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 110
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Updated SSL.
Grabbed the new boinc for Linux from the WCG link. "/usr/local/bin/boinc: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory" This machine does not have X11 installed at all. Where can I find a boinc version without extraneous X11 dependencies? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Your Distro's repository package maintainer maybe? There are so many Linuses that a single package proofed impossible. This one only tested on Ubuntu by Berkeley FAIK.
----------------------------------------[Edit 1 times, last edit by Former Member at Jul 30, 2015 7:12:03 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Your Distro's repository package maintainer maybe? There are so many Linuses that a single package proofed impossible. This one only tested on Ubuntu by Berkeley FAIK. My Debian package is too old and I've never used them in the past either. I just want a working client binary with no unnecessary dependencies. If the download here is only tested on Ubuntu and requires X11, then it should say so, with a note to say where a version that doesn't require X11 may be found. That limitation was certainly not there in the past in any of the v5 or v6 clients I've tried. To anyone who wondered why some of us stay with old versions for so long, this is why: Because you never know when WCG will make undocumented changes that screw things up. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Did you tell us what version of OS you have [too lazy to go search what you might have told us]? Then I can do the Google for you and anyone else. Hopes are low but you never know.
The download -here- is the identical as the download of Berkeley, about zero customization on the part of WCG, so you sort of know where to complain  . Anyone who runs Anglia age Linux is on self-support, same as those still running XT, lest they fork over lots of dosh.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have run into this before even on Ubuntu. Fortunately, there are only a few libraries that need to be loaded (at least in my case). You need to load the software package for libXss for your distro. After that I usually hit a problem with the window widgets toolkit and had to load libwxgtk2.8 (if there is a later version like 3.0 you might want to load that as I think they started using the later version in the later releases of the BOINC client). It usually would start after those libraries were installed.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hey - I'm having this same problem. I have BOINCPortable at work and an updated version at home. Win7 at work, Win 8.1 at home.
I brought in the new DLLs to work, but BOINCPortable is not able to connect to the localhost when I copy them over. I've tried copying libcurl, zlib1, libeay32, and ssleay32 in a variety of combinations. With the new DLLs, boinc.exe gets a failure error: "The application was unable to start correctly (0x0150002). Click OK to close the application." which is why, I assume, boincmgr.exe isn't working. I'm not the most technical person, clearly - I'm capable of following instructions, but I don't have a lot of knowledge. What am I missing? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Here's a search of all posts that mention BOINC AND Portable in same message
https://secure.worldcommunitygrid.org/forums/...=0&sort=1&rows=20 The top 13-14 of that list all touch on the present problem [This thread], which you may want to revisit. If one manages to get 6.10.18 running with just the 2 OpenSSL referring .dlls, why does the other with the same not work? We don't know. FYI: You say you have this plugged into a work-computer. Just to warn you that you may be violating your employers IT policies. The next linked thread refers to the BOINC Usage policy for your reference. http://boinc.berkeley.edu/dev/forum_thread.php?id=9632&filter=false#56247 . |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
SekeRob - I'm sorry, I should have specified that I've read those posts, which is how I knew what the main issue was and how to potentially resolve it. I seem to be running into an issue that Bjoerner also ran into, and was hoping more specifically for them to chime in and say if they'd had success, and if so, how. Or, if someone else has insight into the localhost issue, that would be welcome too.
Alas, there's no "message forum member directly" option, or I would have done so. |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges: 
|
Hey - I'm having this same problem. I have BOINCPortable at work and an updated version at home. Win7 at work, Win 8.1 at home. I brought in the new DLLs to work, but BOINCPortable is not able to connect to the localhost when I copy them over. I've tried copying libcurl, zlib1, libeay32, and ssleay32 in a variety of combinations. With the new DLLs, boinc.exe gets a failure error: "The application was unable to start correctly (0x0150002). Click OK to close the application." which is why, I assume, boincmgr.exe isn't working. I'm not the most technical person, clearly - I'm capable of following instructions, but I don't have a lot of knowledge. What am I missing? That was the same error I got testing on XP with a standard user install. Depending on how new the version you got those 4 dll files from is, it may require the other 3 dll files as older versions used msvcp80 & msvcr80 and newer versions use msvcp100 & msvcr100. I am not sure if sqlite3 is necessary to update but I just did it anyway since I was updating all of the others. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
In case anyone else cares, there is an easy way out of the problem of not wanting a bloated v7 boinc with all manner of extraneous requirements, such as X11.
First, compile SSL. (Easy, it's a tarball, unlike the boinc mess.) Second, ditch using the WCG boinc versions as SekeRob suggested, but for a different reason: They are all compiled with static SSL libs! If we want to link to a new SSL lib, the WCG versions are all useless. The Debian versions of boinc use shared SSL libs. Third, put one of those in an "export LD_LIBRARY_PATH=/usr/local/lib" wrapper and symlink your new SSL to whatever it expects and you have a working boinc again. |
||
|
|
|