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   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2209 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 
Re: boinc cannot communicate with wcg

It's a libcurl error. I suspect that you have an incompatible version of libcurl installed.

Anyway, we can't help you further while you are using an alpha version. We'll have another bash at this when you either downgrade to 5.8, or upgrade to the new beta: 5.10 (you may have to wait a few days until the x64 version is available).

Please will you also confirm whether you are using the official build, or whether you built BOINC yourself? What version of libcurl do you have?
----------------------------------------
[Edit 1 times, last edit by Former Member at Jun 1, 2007 4:17:59 PM]
[Jun 1, 2007 4:10:14 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: boinc cannot communicate with wcg

I am using the BOINC package from boinc.berkeley.edu

The version of libcurl installed on my Ubuntu 7.04 system is 7.15.5. However, I believe the boinc client has libcurl linked within it statically. Looking for strings within that executable file, I found the following: "libcurl 7.16.2".
.
[Jun 2, 2007 4:56:26 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: boinc cannot communicate with wcg

Okay.

Yes, I believe that package is statically linked. However, some Linux and FreeBSD ports of BOINC link to it dynamically. Anyway, that should help narrow down the problem.

I Googled the error code, and it seems rather common. Something to do with the SSL version not being specified - possibly the proxy is interfering with this information.

Would you like to report the bug, or would you like me to handle it for you? Either way, it will be important for you to continue testing this with 5.10.0 when it is released, and also any future bugfixes.

Further testing you could do will depend on the resources you have available. It would help if you can connect the same machine without a proxy, and also test the proxy using the 32 bit version of BOINC.
[Jun 2, 2007 5:14:04 PM]   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: boinc cannot communicate with wcg

5.10.0 is out since a few days and certainly the benchmark has gone into regression again.... instable particular on at least C2D.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jun 2, 2007 5:49:19 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: boinc cannot communicate with wcg

Further testing you could do will depend on the resources you have available. It would help if you can connect the same machine without a proxy, and also test the proxy using the 32 bit version of BOINC.

I will report the bug (in the 64-bit Linux client) on the boinc trak system.

As an experiment, I tried attaching to WCG from my 32-bit SuSE 10.2 system running the 32-bit Linux client 5.10.0. Going through the same proxy, it attached fine and downloaded both the WCG executable and a WCG workunit. (I'll let the work be crunched -- but this is *not* the system I would be running WCG on.)

I will see how well the 64-bit Linux 5.10.x client, once it is released, will work with the WCG project.

mikus

--------

p.s. It is impractical for me to try to connect my Linux systems without using a proxy - I would need to configure new adapters in the machines, and run different cables (rewire my house?).
.
.
[Jun 2, 2007 6:53:47 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 15   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread