| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: boinc cannot communicate with wcg |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
my boinc manager show´s me this message for a couple of days: 17.05.2007 08:42:43||Project communication failed: attempting access to reference site
any idea what it is? |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi diclo,
What happens if you go into the PROJECT tab and select UPDATE or RESET PROJECT? Better tell us what your computer system is. Lawrence |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
on my pc runs win xp and reseting/updating doesn´t work?!
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
diclo, please will you post the lines before and after this failure message? That should give us a clue what is going on.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
hera are all the lines:
18.05.2007 08:52:12|World Community Grid|Sending scheduler request: Requested by user 18.05.2007 08:52:12|World Community Grid|(not requesting new work or reporting completed tasks) 18.05.2007 08:52:13||Project communication failed: attempting access to reference site 18.05.2007 08:52:14||Access to reference site succeeded - project servers may be temporarily down. 18.05.2007 08:52:17|World Community Grid|Scheduler request failed: unsupported protocol 18.05.2007 08:52:17|World Community Grid|Deferring communication for 56 min 21 sec 18.05.2007 08:52:17|World Community Grid|Reason: scheduler request failed thanx for the moment |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi diclo,
Somebody more knowledgeable about BOINC will have to deal with this. I am puzzled by the 'unsupported protocol' error message. Could you describe your system, including the version of BOINC and OS of your computer? If you reboot and try to communicate, the message log should be short enough to post without snipping. Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Running 64-bit Ubuntu 7.04 with the 64-bit boinc client 5.9.11. Have to use a proxy (192.168.1.1; daina.bga) to get to the internet. Tried to attach to WCG (other projects are working on this system). Getting an "unknown protocol" error message.
Don't know if the problem is in the proxy (but I've told the proxy to allow port 443 communication), or in what the boinc client is sending, or in what the WCG server is looking for. [In particular, I don't know which of these is generating that "error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol" message.] mikus ---- Excerpt from boinc's messsage log: Sun May 27 20:45:22 2007||[sched_op_debug] SCHEDULER_OP::init_op_project(): starting op for http://www.worldcommunitygrid.org/ Sun May 27 20:45:22 2007|World Community Grid|Sending scheduler request: Requested by user Sun May 27 20:45:22 2007|World Community Grid|Requesting 65121 seconds of new work Sun May 27 20:45:22 2007||[http_debug] HTTP_OP::init_post(): https://secure.worldcommunitygrid.org/boinc/wcg_cgi/fcgi Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: About to connect() to proxy 192.168.1.1 port 8080 (#0) Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Trying 192.168.1.1... Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Connected to 192.168.1.1 (192.168.1.1) port 8080 (#0) Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Establish HTTP proxy tunnel to secure.worldcommunitygrid.org:443 Sun May 27 20:45:22 2007||[http_debug] [ID#32] Sent header to server: CONNECT secure.worldcommunitygrid.org:443 HTTP/1.0 Host: secure.worldcommunitygrid.org:443 User-Agent: BOINC client (x86_64-pc-linux-gnu 5.9.11) Proxy-Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: successfully set certificate verify locations: Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: CAfile: ca-bundle.crt CApath: none Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: SSLv2, Client hello (1): Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Expire cleared Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Closing connection #0 Sun May 27 20:45:22 2007||[http_debug] HTTP error: SSL connect error Sun May 27 20:45:23 2007||Project communication failed: attempting access to reference site Sun May 27 20:45:23 2007||[http_debug] HTTP_OP::init_get(): http://www.google.com Sun May 27 20:45:23 2007||[http_debug] [ID#33] info: About to connect() to proxy 192.168.1.1 port 8080 (#0) Sun May 27 20:45:23 2007||[http_debug] [ID#33] info: Trying 192.168.1.1... Sun May 27 20:45:23 2007||[http_debug] [ID#33] info: Connected to 192.168.1.1 (192.168.1.1) port 8080 (#0) Sun May 27 20:45:23 2007||[http_debug] [ID#33] Sent header to server: GET http://www.google.com HTTP/1.1 User-Agent: BOINC client (x86_64-pc-linux-gnu 5.9.11) Host: www.google.com Pragma: no-cache Accept: */* Accept-Encoding: deflate, gzip Proxy-Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: HTTP/1.0 200 OK Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: Cache-Control: private Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: Content-Type: text/html; charset=ISO-8859-1 Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: Set-Cookie: PREF=ID=be155963cdb3c9e5:TM=1180316978:LM=1180316978:S=vVtA7hkdVsIu5AUc; expires=Sun, 17-Jan-2038 19:14:07 GMT; path=/; domain=.google.com Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: Server: GWS/2.1 Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: Date: Mon, 28 May 2007 01:49:38 GMT Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: X-Cache: MISS from daina.bga Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: Proxy-Connection: close Sun May 27 20:45:23 2007||[http_debug] [ID#33] Received header from server: Sun May 27 20:45:23 2007||[http_debug] [ID#33] info: Expire cleared Sun May 27 20:45:23 2007||[http_debug] [ID#33] info: Closing connection #0 Sun May 27 20:45:24 2007||Access to reference site succeeded - project servers may be temporarily down. Sun May 27 20:45:27 2007|World Community Grid|Scheduler request failed: SSL connect error Sun May 27 20:45:27 2007|World Community Grid|Deferring communication for 3 hr 32 min 35 sec Sun May 27 20:45:27 2007|World Community Grid|Reason: scheduler request failed ---- |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
hmmmm 5.9.11 is an alpha development version, so could not vouch for the stability or completeness.... if all else fails, return to supported production version 5.8.16
----------------------------------------The line suspicious is: Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: CAfile: ca-bundle.crt CApath: none Check if the bolded file is present in the BOINC program directory or visit other posts on this forum to see where to get it.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
SSL connect error BOINC needs to find ca-bundle.crt to communicate over the Secure Socket Layer. There are many threads where people have had to find the correct ca-bundle.crt for their distro and put it in the BOINC directory. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I believe that Sekerob is mistaken in suggesting that my problem is that the ca-bundle.crt file is not being found. That file *is* in the same directory as the boinc client executable; when I searched the internet for messages concerning ca-bundle.crt, situations in which that file could not be found seemed to produce a different result (i.e., 'error' rather than just 'info'). I think it likely that what the "suspicious" line is saying is that the validation info will be found in file 'ca-bundle.crt", and that to access it 'no' path will have to be prepended to its name. I have asked the boinc developers for clarification of the message I'm getting, but have not yet received an answer.
My current suspicion is that how my 64-bit operating system is supporting the SSL protocol is somehow different from what boinc/wcg expects. As a test I did successfully perform a banking transaction from that system -- so I presume the proxy I'm using provides proper pass-through for port 443. I will continue to seek an explanation for my SSL problem accessing wcg. . |
||
|
|
|