| 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 |
|
|
mito7
Advanced Cruncher Slovakia Joined: Oct 12, 2008 Post Count: 58 Status: Offline Project Badges: 
|
Sek,
----------------------------------------I will definitely try it but I have this on my work comp and I am off work for this week. And it would be no point trying because all SSL version are enabled now. On 20.7. older version will be disabled after certifcate upgrade and then I try if that trick worked. Of course I will let you know the outcome ;)  |
||
|
|
The Aspens
Advanced Cruncher New Mexico, USA Joined: Apr 15, 2005 Post Count: 54 Status: Offline Project Badges: 
|
My guess is that if it works at all (like Sekerob said, check the scheduler request followed by upload/download) then it is likely to work with the new certificate.
----------------------------------------Based on my reading of https://www.openssl.org/news/openssl-0.9.8-notes.html, support for sha256 was added in version 0.9.8o of OpenSSL. However that required the calling application to set flags to enable support for it. I believe that with OpenSSL 1.0 those flags are enabled by default. My only concern is that something about the OpenSSL API changed between version 0.9.8 and 1.0 and thus the statement about "if it works at all". This will be really helpful though if it works.  |
||
|
|
rclow@v-m-f.org
Cruncher Joined: Apr 17, 2012 Post Count: 18 Status: Offline Project Badges: 
|
@Arjai - if you check the log and see a version of SSL that is 1.0.1 or higher you are sure to be ok. There are some situations where lower versions have been ok. Thanks! Since this P4 is headless, and my connection now is a 3G hotspot, even Teamviewer has a tough time with it. So, rather than preemptively effing it all up. I waited. This Morning, 21st, it dumped 12 and up-ed 14!! So, to clarify, 6.12.33, WORKS after SSL updates.  |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges:
|
Did some more testing on Windows, and ver. 5.10.45 will work if the dll files are replaced with ones from newer versions of the client. I used 7.6.3 dll files and copied all 7 over to the 5.10.45 directory and contact with WCG works fine.
|
||
|
|
mito7
Advanced Cruncher Slovakia Joined: Oct 12, 2008 Post Count: 58 Status: Offline Project Badges:
|
I have only copied 2 dll files (see my earlier post) from 7.2.47 to 6.10.18 a it is working. I have got some errors y´day (but only when reported work, upload and download worked fine). And now it works smoothly.
---------------------------------------- |
||
|
|
Bjoerner
Cruncher Joined: May 4, 2007 Post Count: 10 Status: Offline Project Badges:
|
I have only copied 2 dll files (see my earlier post) from 7.2.47 to 6.10.18 a it is working. I have got some errors y´day (but only when reported work, upload and download worked fine). And now it works smoothly. I tried it with the dll files from 7.4.42 and the connection to local host is not working. Does it have to be 7.2.47? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not necessarily, but 7.2.47 happens to be the special build for WCG [the only project using elevated security in BOINC world, FAIK].
----------------------------------------Edit: Connection to localhost failing is a different issue... the BOINC Manager unable to connect to the core client. Check if boinc.exe is running. [Edit 1 times, last edit by Former Member at Jul 22, 2015 10:21:21 AM] |
||
|
|
Bjoerner
Cruncher Joined: May 4, 2007 Post Count: 10 Status: Offline Project Badges:
|
Hmm, more tricky than I thought.
I have the BOINCPortable.exe and boincmgr.exe running with the 7.4.42 dlls in place. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
'connection to localhost' in BOINC parlance means BOINCmgr talking to boinc.exe via the local ip 127.0.0.1, default over port 31416. If it fails, the BOINCmgr shows this right bottom in the mgrs status bar. If you meant something different, you need to qualify.
Since BOINCPortable.exe is used as executable name, that's kind of already a deviation. As mito7 has it working with 6.10.18, can't see what different tricks apply.  |
||
|
|
Bjoerner
Cruncher Joined: May 4, 2007 Post Count: 10 Status: Offline Project Badges:
|
That is what I get: http://i.imgur.com/YkBKygP.png
----------------------------------------Essentially it can't connect to localhost. Looks like there is no workaround yet, except trying to get my hands on the 7.2.47 dlls. Edit: I swapped out to the original dlls of the Portable version for the second time and oddly enough I got all remaining uploads (11 WUs) through. I cannot report them however. 22.07.2015 14:08:18 World Community Grid Reporting 11 completed tasks, requesting new tasks [Edit 1 times, last edit by Bjoerner at Jul 22, 2015 12:09:16 PM] |
||
|
|
|