| 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 |
|
|
costas218
Cruncher Joined: Apr 27, 2007 Post Count: 6 Status: Offline Project Badges: 
|
What about a working portable boinc client?
|
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
See earlier in this thread for a [suspect] zip of supposedly 6.10.60... fetch at own risk [My browser and AV would not want to touch it even with a long pole]. Protable BOINC has not been 'maintained' by whoever constructed it since a very long time [find very very little on Google].
----------------------------------------BOINC is open source, anyone can port. Lest builds are Berkeley origin or other trusted place, compile yourself as one other member reported doing few posts up in this thread. BOINC is only officially maintained for Windows, Android, Mac and Linux (only tests on Ubuntu I think). For Windows I've identified 2 specific OpenSSL related files for BOINC [see also earlier in thread]. No idea if you can drop these into the BOINC program folder of older installs and then then starting working with WCG. Trial and error. No you have, yes you could get. To sum it up, I've added zero information to this thread with this post.  [Edit 1 times, last edit by Former Member at Jul 14, 2015 2:28:37 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
In theory one should be able to take an older client and a newer version of OpenSSL and compile it to have a working client. That is unless the client is doing something weird.
What this also means, other projects that are using SSL will have an issue in the future. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Unfortunately, we can't precisely pinpoint the impacted devices and match that to devices and block them. One reason is the failure and resumption may not be handled well. One of my machines, after attempting to connect for several days (once per minute or so - 30,000 extraneous lines in the log, thanks a lot), gave up altogether. I had to kill boinc and restart it manually. Other machines returned to normal operation after the SSL problem went away. I'm using v5.10.45, as I've had no reason to upgrade. I'd suggest that if you are going to make changes that will cause massive failures, you should inform users first, preferably with lots of notice. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
How about having an option to just not use SSL at all? It's just a waste of CPU cycles anyhow. It's not like my ISP is going to intercept my WCG results and report them to a competing research group or something.
|
||
|
|
rclow@v-m-f.org
Cruncher Joined: Apr 17, 2012 Post Count: 18 Status: Offline Project Badges: 
|
Building dependency tree
Reading state information... Done boinc-client is already the newest version. boinc-manager is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? y This is on Mint Lisa. Boinc ver. 6.12.33 I wonder if this version is gonna be affected by this? So, far, so good. |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 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.
|
||
|
|
mito7
Advanced Cruncher Slovakia Joined: Oct 12, 2008 Post Count: 58 Status: Offline Project Badges: 
|
knreed
----------------------------------------I have coppied files that Sekerob mentioned earlier (libeay32.dll and ssleay32.dll) from BOINC 7.2.47 to portable BOINC 6.10.18 and SSL is now 1.0.1 according to log. You think it should work? 15/07/2015 20:55:33 Starting BOINC client version 6.10.18 for windows_x86_64 15/07/2015 20:55:33 Config: don't use coprocessors 15/07/2015 20:55:33 log flags: file_xfer, sched_ops, task, checkpoint_debug 15/07/2015 20:55:33 Libraries: libcurl/7.19.4 OpenSSL/1.0.1 zlib/1.2.3 15/07/2015 20:55:33 Data directory: C:\TEMP\BOINCPortable\App\BOINC 15/07/2015 20:55:33 Running under account 15/07/2015 20:55:33 Processor: 12 GenuineIntel Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz [Intel64 Family 6 Model 62 Stepping 4] 15/07/2015 20:55:33 Processor: 256.00 KB cache 15/07/2015 20:55:33 Processor features: fpu tsc pae nx sse sse2 pni mmx 15/07/2015 20:55:33 OS: Microsoft Windows 7: x64 Edition, Service Pack 1, (06.01.7601.00) 15/07/2015 20:55:33 Memory: 31.95 GB physical, 63.89 GB virtual 15/07/2015 20:55:33 Disk: 919.22 GB total, 765.01 GB free 15/07/2015 20:55:33 Local time is UTC +2 hours 15/07/2015 20:55:33 Using HTTP proxy 15/07/2015 20:55:33 World Community Grid URL http://www.worldcommunitygrid.org/; Computer ID 3357121; resource share 100 15/07/2015 20:55:33 World Community Grid General prefs: from World Community Grid (last modified 26-Apr-2013 08:13:51) 15/07/2015 20:55:33 World Community Grid Computer location: home 15/07/2015 20:55:33 General prefs: using separate prefs for home 15/07/2015 20:55:33 Reading preferences override file 15/07/2015 20:55:33 Preferences limit memory usage when active to 24534.13MB 15/07/2015 20:55:33 Preferences limit memory usage when idle to 29440.95MB 15/07/2015 20:55:33 Preferences limit disk usage to 20.00GB 15/07/2015 20:55:33 Running CPU benchmarks 15/07/2015 20:55:33 Suspending computation - running CPU benchmarks 15/07/2015 20:56:04 Benchmark results: 15/07/2015 20:56:04 Number of CPUs: 12 15/07/2015 20:56:04 3473 floating point MIPS (Whetstone) per CPU 15/07/2015 20:56:04 8824 integer MIPS (Dhrystone) per CPU  |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges:
|
As a follow up to what mito7 tried, I did this on a normal install on WinXP.
Installed ver. 6.10.1 which from previous tests know did not work with the new certificate. Here are the first 3 lines: 7/15/2015 6:38:21 PM Starting BOINC client version 6.10.1 for windows_intelx86 7/15/2015 6:38:21 PM log flags: task, file_xfer, sched_ops, cpu_sched, checkpoint_debug 7/15/2015 6:38:21 PM Libraries: libcurl/7.19.4 OpenSSL/0.9.8k zlib/1.2.3 Then, I copied over the two files Sekerob mentioned from ver. 7.6.3, but the client would not start up correctly. So I copied all of the dll files from 7.6.3 (libcurl, libeay32, msvcp100, msvcr100, sqlite3, ssleay32, & zlib1) and the client started correctly with updated libraries in the messages: 7/15/2015 6:41:23 PM Starting BOINC client version 6.10.1 for windows_intelx86 7/15/2015 6:41:23 PM log flags: task, file_xfer, sched_ops, cpu_sched, checkpoint_debug 7/15/2015 6:41:23 PM Libraries: libcurl/7.39.0 OpenSSL/1.0.2a zlib/1.2.8 Will have to wait until the 20th to see if dropping in new dll files works. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The number of BOINC iterations is near countless, so there are many surprises as what will and will not work borrowing pieces from 1 client and dropping them into install folders of long passed versions. [Imagine, the BOINC Manager is maintained so it can still remote connect to all these old releases]
To mito7's question, what you're waiting for to try fetching/reporting work. Tell us the outcome [Are the minimal Linux usb installs of, forgot the name, Dotch or so, still working?] If someone goes like putting foot down, text often reads like that unintended tone, 'I have 5.10.48, I had no need to upgrade', then now is the time.  As for an option to disable SSL in communications... very very much doubt WCG would ever agree to such a proposition, but this will have come out in geste  |
||
|
|
|