Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 15
Posts: 15   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1859 times and has 14 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Problem with 64 bit linux

I recently updated one of my computers to Mandriva x64 2009.1. I had been using the 32 bit version before. This was a clean install meaning I reformated the hard drive when installing. After the install I get an SSL connect error only on this project all the othe projects work fine. I read the posts about curl but haven't found anything that helps. I have reset the project and I still get the same error. I put in a cc_config.xml file and added the http_debug flag. Here is what I get when I update WCG.


localhost http://www.worldcommunitygrid.org/ 6/3/2009 9:39:58 PM Sending scheduler request: Requested by user.
localhost http://www.worldcommunitygrid.org/ 6/3/2009 9:39:58 PM Requesting new tasks
localhost --- 6/3/2009 9:39:58 PM [http_debug] HTTP_OP::init_post(): https://grid.worldcommunitygrid.org/boinc/wcg_cgi/fcgi
localhost --- 6/3/2009 9:40:00 PM [http_debug] [ID#3] info: About to connect() to grid.worldcommunitygrid.org port 443 (#2)
localhost --- 6/3/2009 9:40:00 PM [http_debug] [ID#3] info: Trying 198.20.8.241...
localhost --- 6/3/2009 9:40:00 PM [http_debug] [ID#3] info: Connected to grid.worldcommunitygrid.org (198.20.8.241) port 443 (#2)
localhost --- 6/3/2009 9:40:00 PM [http_debug] [ID#3] info: found 59 certificates in ca-bundle.crt
localhost --- 6/3/2009 9:40:01 PM [http_debug] [ID#3] info: gnutls_handshake() failed: A TLS packet with unexpected length was received.
localhost --- 6/3/2009 9:40:01 PM [http_debug] [ID#3] info: Expire cleared
localhost --- 6/3/2009 9:40:01 PM [http_debug] [ID#3] info: Closing connection #2
localhost --- 6/3/2009 9:40:01 PM [http_debug] HTTP error: SSL connect error
localhost --- 6/3/2009 9:40:01 PM Project communication failed: attempting access to reference site
localhost --- 6/3/2009 9:40:01 PM [http_debug] HTTP_OP::init_get(): http://www.google.com/
localhost http://www.worldcommunitygrid.org/ 6/3/2009 9:40:03 PM Scheduler request failed: SSL connect error



Does anyone know what the "info: gnutls_handshake() failed: A TLS packet with unexpected length was received" means. Any help woul be appreciated
[Jun 4, 2009 2:06:45 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Nick-MMX
Advanced Cruncher
Joined: Dec 24, 2006
Post Count: 108
Status: Offline
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

Ive had a similar problem to this one in the past. The router that I was using was forwarding the port to a different computer for some reason. I had to replace the router to fix it. Hope that helps.
[Jun 4, 2009 2:22:15 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

Hi,

here a link to the only other thread where the gnutls_handshake got a mention... hope that gives the pointer.

http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=25666
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jun 4, 2009 6:57:32 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Lightningrunner
Cruncher
Joined: Sep 11, 2007
Post Count: 4
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

Try this:
1. cd /var/lib/boinc-client
2. sudo mv ca-bundle.crt{,.bak}
3. sudo wget http://boinc.berkeley.edu/trac/export/16195/trunk/boinc/curl/ca-bundle.crt -O ca-bundle.crt.upstream
4. sudo cp -a ca-bundle.crt{.upstream,}

use ALL .s and { etc
[Jun 4, 2009 11:06:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

Lightningrunner, although that is a common fix for CA-bundle issues, it is not the problem here.

Curl will report SSL errors and certificate errors differently.

Paul Sands, Sekerob's advice is the most likely to be correct. We can confirm this if you post the startup messages, particularly the libraries line. The solution is to rebuild libcurl with OpenSSL support enabled.
[Jun 4, 2009 11:20:29 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

Here are my start up messages


localhost --- 6/3/2009 9:36:33 PM Starting BOINC client version 6.7.4 for x86_64-pc-linux-gnu
localhost --- 6/3/2009 9:36:33 PM This a development version of BOINC and may not function properly
localhost --- 6/3/2009 9:36:33 PM log flags: task, file_xfer, sched_ops, http_debug
localhost --- 6/3/2009 9:36:33 PM Libraries: libcurl/7.19.4 GnuTLS/2.6.4 zlib/1.2.3 c-ares/1.6.0 libidn/1.13 libssh2/1.0
localhost --- 6/3/2009 9:36:33 PM Data directory: /home/psands/BOINC
localhost SETI@home 6/3/2009 9:36:33 PM Found app_info.xml; using anonymous platform
localhost --- 6/3/2009 9:36:33 PM Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz [Family 6 Model 15 Stepping 11]
localhost --- 6/3/2009 9:36:33 PM Processor: 4.00 MB cache
localhost --- 6/3/2009 9:36:33 PM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm t
localhost --- 6/3/2009 9:36:33 PM OS: Linux: 2.6.29.3-desktop-1mnb
localhost --- 6/3/2009 9:36:33 PM Memory: 2.95 GB physical, 3.90 GB virtual
localhost --- 6/3/2009 9:36:33 PM Disk: 277.75 GB total, 274.59 GB free
localhost --- 6/3/2009 9:36:33 PM Local time is UTC -4 hours
localhost --- 6/3/2009 9:36:33 PM CUDA device: GeForce GTX 260 (driver version 0, compute capability 1.3, 896MB, est. 96GFLOPS)
localhost --- 6/3/2009 9:36:33 PM Not using a proxy
localhost SETI@home 6/3/2009 9:36:33 PM URL: http://setiathome.berkeley.edu/; Computer ID: 4358929; location: home; project prefs: default
localhost Hydrogen@Home 6/3/2009 9:36:33 PM URL: http://hydrogenathome.org/; Computer ID: 3849; location: (none); project prefs: default
localhost wanless2 6/3/2009 9:36:33 PM URL: http://bearnol.is-a-geek.com/wanless2/; Computer ID: 6304; location: (none); project prefs: default
localhost lhcathome 6/3/2009 9:36:33 PM URL: http://lhcathome.cern.ch/lhcathome/; Computer ID: 9686926; location: home; project prefs: default
localhost http://www.worldcommunitygrid.org/ 6/3/2009 9:36:33 PM URL: http://www.worldcommunitygrid.org/; Computer ID: not assigned yet; location: (none); project prefs: default
localhost Einstein@Home 6/3/2009 9:36:33 PM URL: http://einstein.phys.uwm.edu/; Computer ID: 1269812; location: home; project prefs: default
localhost rosetta@home 6/3/2009 9:36:33 PM URL: http://boinc.bakerlab.org/rosetta/; Computer ID: 60957; location: home; project prefs: default
localhost Cosmology@Home 6/3/2009 9:36:33 PM URL: http://www.cosmologyathome.org/; Computer ID: 22959; location: (none); project prefs: default
localhost Magnetism at home 6/3/2009 9:36:33 PM URL: http://kinetic.dnsalias.org/magnetism/; Computer ID: 7725; location: (none); project prefs: default
localhost GPUGRID 6/3/2009 9:36:33 PM URL: http://www.gpugrid.net/; Computer ID: 26413; location: (none); project prefs: default
localhost climateprediction.net 6/3/2009 9:36:33 PM URL: http://climateprediction.net/; Computer ID: 867852; location: home; project prefs: default
localhost Milkyway@home 6/3/2009 9:36:33 PM URL: http://milkyway.cs.rpi.edu/milkyway/; Computer ID: 16753; location: (none); project prefs: default
localhost Poem@Home 6/3/2009 9:36:33 PM URL: http://boinc.fzk.de/poem/; Computer ID: 11188; location: (none); project prefs: default
localhost PrimeGrid 6/3/2009 9:36:33 PM URL: http://www.primegrid.com/; Computer ID: 64181; location: (none); project prefs: default
localhost SETI@home Beta Test 6/3/2009 9:36:33 PM URL: http://setiweb.ssl.berkeley.edu/beta/; Computer ID: 1256; location: home; project prefs: default
localhost SETI@home 6/3/2009 9:36:33 PM General prefs: from SETI@home (last modified 11-Nov-2008 16:11:30)
localhost SETI@home 6/3/2009 9:36:33 PM Computer location: home
localhost SETI@home 6/3/2009 9:36:33 PM General prefs: no separate prefs for home; using your defaults
localhost --- 6/3/2009 9:36:33 PM Reading preferences override file
localhost --- 6/3/2009 9:36:33 PM Preferences limit memory usage when active to 2719.98MB
localhost --- 6/3/2009 9:36:33 PM Preferences limit memory usage when idle to 3022.20MB
localhost --- 6/3/2009 9:36:33 PM Preferences limit disk usage to 100.00GB
localhost wanless2 6/3/2009 9:36:33 PM Restarting task wep_1244014180_439_1 using wep version 113


I used Mandriva's package manager to install curl and libcurl. According to it OpenSSl is enabled.
[Jun 4, 2009 8:25:08 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

This is the output of ldd libcurl

localhost psands # ldd /usr/lib64/libcurl.so.4
linux-vdso.so.1 => (0x00007fff247fe000)
libcares.so.2 => /usr/lib64/libcares.so.2 (0x00007ff31c2f0000)
libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007ff31c0bd000)
libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007ff31be97000)
libldap-2.4.so.2 => /usr/lib64/libldap-2.4.so.2 (0x00007ff31bc4e000)
librt.so.1 => /lib64/librt.so.1 (0x00007ff31ba45000)
liblber-2.4.so.2 => /usr/lib64/liblber-2.4.so.2 (0x00007ff31b833000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007ff31b604000)
libgnutls.so.26 => /usr/lib64/libgnutls.so.26 (0x00007ff31b352000)
libz.so.1 => /lib64/libz.so.1 (0x00007ff31b13c000)
libgcrypt.so.11 => /usr/lib64/libgcrypt.so.11 (0x00007ff31aec6000)
libc.so.6 => /lib64/libc.so.6 (0x00007ff31ab64000)
libcrypto.so.0.9.8 => /usr/lib64/libcrypto.so.0.9.8 (0x00007ff31a7a9000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007ff31a592000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007ff31a376000)
libssl.so.0.9.8 => /usr/lib64/libssl.so.0.9.8 (0x00007ff31a122000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ff319f06000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff31c767000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007ff319c61000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007ff319a39000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007ff319835000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007ff31962d000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007ff319428000)
libtasn1.so.3 => /usr/lib64/libtasn1.so.3 (0x00007ff319217000)
libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00007ff319013000)
[Jun 4, 2009 10:33:48 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
confused Re: Problem with 64 bit linux

localhost --- 6/3/2009 9:36:33 PM Starting BOINC client version 6.7.4 for x86_64-pc-linux-gnu

...They start developing v.6.7.X now confused
[Jun 5, 2009 5:29:48 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

It lasted about 1 nanosecond, in Berkeley terms. It was a step to a special GridRepublic version (an central BOINC account manager) to add Facebook functionality.

THEN, they briefly did 6.8 to signify a production release and then they renumbered to 6.9, very first alpha towards 6.10 which is the next developers production target and it's loaded (with what, you'll have to go to Berkeley forum and follow the check-in list).

If you see an uneven minor ( .1 .3 .5 .7 or .9) it's very alpha. If you see an even minor (.2 .4 .6 .8), it's permanent beta, for a recommended release lasts about, 2 nanoseconds. This rule confirmed again going from 6.6.20 to 6.6.28 to 6.6.31 all being stickered 'recommended' and notification messages appearing in the client log if you don't use the WCG custom version which only tells when WCG thinks it's ready for production, here.

So, when you see 6.7.4 the question should read "have they started developing 6.8?" and on we went to 6.10 ;?
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jun 5, 2009 6:39:30 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Problem with 64 bit linux

Only want to be told when there is a WCG endorsed release... follow this short FAQ: https://secure.worldcommunitygrid.org/forums/wcg/viewthread?thread=25784
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jun 5, 2009 6:40:43 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 15   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread