 |
|
Message boards : Number crunching : Unable to connect to server to get tasks
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 4 Jun 17 Posts: 15 Credit: 2,654,269 RAC: 1,635 |
5404 climateprediction.net 8/18/2024 7:38:27 PM update requested by user 5405 climateprediction.net 8/18/2024 7:38:32 PM Fetching scheduler list 5406 8/18/2024 7:38:34 PM Project communication failed: attempting access to reference site 5407 8/18/2024 7:38:35 PM Internet access OK - project servers may be temporarily down. I've disabled my firewall, opened up every web site query on my DNS server. Web site works fine from the browser, but when I try to connect to this project to get work I get this message every time. |
 Dave JacksonSend message Joined: 15 May 09 Posts: 4538 Credit: 19,008,987 RAC: 21,524 |
Just checked my event log, no record of failed communication with server on my box at least over past fifteen hours at least. As your computers are hidden, I can't see if you have since had a successful attempt. If not, try enabling http debug in the event log options, try again and post the output. Don't leave it enabled as it very quickly fills up the log. |
|
Send message Joined: 4 Jun 17 Posts: 15 Credit: 2,654,269 RAC: 1,635 |
8/18/2024 8:16:40 PM | climateprediction.net | update requested by user 8/18/2024 8:16:44 PM | climateprediction.net | [http] HTTP_OP::init_get(): https://climateprediction.net/ 8/18/2024 8:16:44 PM | climateprediction.net | Fetching scheduler list 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Too old connection (474 seconds idle), disconnect it 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Connection 2004 seems to be dead 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Closing connection 2004 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Trying 129.67.241.50:443... 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Connected to climateprediction.net (129.67.241.50) port 443 (#2006) 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: schannel: disabled automatic use of client certificate 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: ALPN: offers http/1.1 8/18/2024 8:16:45 PM | climateprediction.net | [http] [ID#1] Info: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline. 8/18/2024 8:16:45 PM | climateprediction.net | [http] [ID#1] Info: Closing connection 2006 8/18/2024 8:16:45 PM | climateprediction.net | [http] HTTP error: SSL connect error 8/18/2024 8:16:46 PM | | Project communication failed: attempting access to reference site 8/18/2024 8:16:46 PM | | [http] HTTP_OP::init_get(): https://www.google.com/ 8/18/2024 8:16:46 PM | | [http] [ID#0] Info: Trying 74.125.21.106:443... 8/18/2024 8:16:46 PM | | [http] [ID#0] Info: Connected to www.google.com (74.125.21.106) port 443 (#2007) 8/18/2024 8:16:46 PM | | [http] [ID#0] Info: schannel: disabled automatic use of client certificate 8/18/2024 8:16:46 PM | | [http] [ID#0] Info: ALPN: offers http/1.1 8/18/2024 8:16:46 PM | | [http] [ID#0] Info: ALPN: server accepted http/1.1 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: GET / HTTP/1.1 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: Host: www.google.com 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.20.2) 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: Accept: */* 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: Accept-Encoding: deflate, gzip 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: Accept-Language: en_US 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: reference site 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: <time>1724026606</time> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: </msg> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: <msg> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: <project></project> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: <pri>1</pri> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: <seqno>5441</seqno> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: <body><![CDATA[ 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: [http] HTTP_OP::init_get(): https://www.google.com/ 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: <time>1724026606</time> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: </msg> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: </msgs> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: </boinc_gui_rpc_reply> 8/18/2024 8:16:46 PM | | [http] [ID#0] Sent header to server: 8/18/2024 8:16:47 PM | | [http] [ID#0] Info: Mark bundle as not supporting multiuse 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: HTTP/1.1 200 OK 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Date: Mon, 19 Aug 2024 00:16:47 GMT 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Expires: -1 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Cache-Control: private, max-age=0 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Content-Type: text/html; charset=ISO-8859-1 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Content-Security-Policy-Report-Only: object-src 'none';base-uri 'self';script-src 'nonce-LfZoarMCU4rykRtf6nclLw' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info." 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Content-Encoding: gzip 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Server: gws 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: X-XSS-Protection: 0 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: X-Frame-Options: SAMEORIGIN 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Set-Cookie: AEC=AVYB7cq-eqsz6P28ego-jWaeA60rcwqBPu10xNuvN7CJTlGkhAGe12qt67s; expires=Sat, 15-Feb-2025 00:16:47 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax 12/31/1969 7:00:00 PM | | 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: Transfer-Encoding: chunked 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: 00000001 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: 00000001 8/18/2024 8:16:47 PM | | 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: 00000001 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: 8/18/2024 8:16:47 PM | | [http] [ID#0] Received header from server: 00000001 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 2364 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 10354 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 3 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 25 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 5 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 8 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 5 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 1 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 3021 bytes 8/18/2024 8:16:47 PM | | [http_xfer] [ID#0] HTTP: wrote 4614 bytes 8/18/2024 8:16:47 PM | | [http] [ID#0] Info: Connection #2007 to host www.google.com left intact 8/18/2024 8:16:47 PM | | Internet access OK - project servers may be temporarily down. |
|
Send message Joined: 1 Jan 07 Posts: 1061 Credit: 36,703,308 RAC: 9,860 |
Have you recently started trying to attach that computer to the CPDN project? Your opening post mentioned 'Fetching scheduler list' - that normally has to be done just once, when you attach a new computer. Your logs mention a connection to 'climateprediction.net', and that's also only needed once, at initial sign-on. The problem seems to be schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.That's beyond me - I have no idea what a 'revocation server' is, or what role it plays in this situation. I've also had problems connecting new devices to CPDN, and I'll have to do it again next week - I found a work-round last time, but can't immediately remember what it was. Once we can get you connected, the rest is usually straightforward - all subsequent connections are with cpdn.org, whuch doesn't have these problems. Edit - perhaps stackoverflow? |
|
Send message Joined: 4 Jun 17 Posts: 15 Credit: 2,654,269 RAC: 1,635 |
Yes I'm not able to attach the host. I've tried two different windows hosts, possibly even a third a while back. |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4538 Credit: 19,008,987 RAC: 21,524 |
The revocation function was unable to check revocation because the revocation server was offline.As this is outside of Richard's experience it will be no surprise to learn it is also outside of mine. I found a couple of threads on other fora about this with git. One of them found this solution. I fixed the issue manually deleting all expired certificates from my PC (certmgr.msc). I read this in some forum and it worked however at this point I'm not sure why expired certificates cause this problem in some situations. |
|
Send message Joined: 1 Jan 07 Posts: 1061 Credit: 36,703,308 RAC: 9,860 |
I suspect that the ultimate fix may require the attention of Oxford IT support, either to the server or to the perimeter firewall. That's beyond our skills here. @Skillz - Do you have access to any other machine, already attached to and successfully running CPDN? I suspect that my workround may have involved copying a segment from client_state.xml from another machine, to bypass the troubled 'scheduler fetch' blockage. But's that's not trivial, and requires knowledge and attention to detail. I won't be able to confirm it until next week. |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4538 Credit: 19,008,987 RAC: 21,524 |
Interesting Richard. I have signed two new machines up to CPDN since this latest batch of work came on stream. (Actually the same machine, one client using WINE, the other Tiny10 a cut down version of Windows in a VM. I am struggling to work out why Skillz should have an issue when it worked out of the box for me. What is different about his machines. I presume they have been able to get work for other projects? Are they on a network? |
|
Send message Joined: 4 Jun 17 Posts: 15 Credit: 2,654,269 RAC: 1,635 |
I suspect that the ultimate fix may require the attention of Oxford IT support, either to the server or to the perimeter firewall. That's beyond our skills here. No, I haven't been able to attach to CPDN for years. My points I have are from years ago when I crunched this project. I can't even connect to the project with my host unless I use the command line and all that does is just locally generate the account_project.xml file for you. It doesn't actually communicate with the project. When I try to use the GUI (BOINC Manager or BOINCTasks) I am just told it failed to add project and to please try again. Interesting Richard. I have signed two new machines up to CPDN since this latest batch of work came on stream. (Actually the same machine, one client using WINE, the other Tiny10 a cut down version of Windows in a VM. I am struggling to work out why Skillz should have an issue when it worked out of the box for me. What is different about his machines. I presume they have been able to get work for other projects? Are they on a network? Things I have tried. Downloaded the newest client 8.x.x. Disabled my Pi-hole blocking features. Changed my host DNS to that of Google's public DNS servers 8.8.8.8 and 8.8.4.4. Tethered my phone to my computer using the Cell service network to attempt to connect. Used different hosts all running Windows bare metal. (3 total, all Windows 10) |
|
Send message Joined: 4 Jun 17 Posts: 15 Credit: 2,654,269 RAC: 1,635 |
One other thing I'd like to mention. Even though the BOINC Manager shows climateprediction.net as a project on the project list. When I go to my account and view my hosts. It's not there. Nothing is there except for hosts I had connected years ago if I show more than the last 30 days. |
|
Send message Joined: 1 Jan 07 Posts: 1061 Credit: 36,703,308 RAC: 9,860 |
That's part of the same problem. It's a two-part process: you have to connect and get the address of the scheduler first, and then contact the scheduler and get assigned a host number and a whole lot of other stuff besides. You're failing on the first part. Out of curiosity, have you attached to any other BOINC project? |
|
Send message Joined: 4 Jun 17 Posts: 15 Credit: 2,654,269 RAC: 1,635 |
Yeah, I run a lot of BOINC projects on all my hosts including the one's I've tried attaching. Even trying multiple instances on the same host results in the same. |
|
Send message Joined: 1 Jan 07 Posts: 1061 Credit: 36,703,308 RAC: 9,860 |
That reinforces my suspicion that there is something wrong with the configuration of the climateprediction dot net server. I'll be watching out for that when my new hardware arrives, currently scheduled a week on Thursday. |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4538 Credit: 19,008,987 RAC: 21,524 |
That reinforces my suspicion that there is something wrong with the configuration of the climateprediction dot net server. I'll be watching out for that when my new hardware arrives, currently scheduled a week on Thursday.Which still leaves the question as to what is different about the clients that can still attach to the project? I remember some years ago, users from a specific ISP got blacklisted though I don't remember the details and probably a red herring. I guess we are going to have to wait till you get your new hardware Richard and see what happens. I doubt there is much point in my setting up another windows VM to try attaching as I am fairly certain it would work as normal. given that it was only attached after the current batches of work came out? |
|
Send message Joined: 1 Jan 07 Posts: 1061 Credit: 36,703,308 RAC: 9,860 |
I had a quick look yesterday, and new hosts have been attaching steadily recently - the last I saw was 1552499. So it isn't a universal problem. I've hopefully got a quiet day today, so I was thinking of making a list of the main visible attributes of each of them - things like OS variant, BOINC version number, and so on. Hopefully that might reveal a gap somewhere - some that you'd expect would be able to attach, but are missing from the list. Won't cover things like ISP, though. |
|
Send message Joined: 12 Apr 21 Posts: 317 Credit: 14,826,047 RAC: 19,877 |
If you haven't yet, try the following: Log into your account on the website. In the Account information section, click on View next to Account Keys. Read thru it. There are instructions on how to attach a computer to your account without using the BOINC Manager. If other hosts are connecting, like Richard said, and you've tried tethering via your cellphone, I kind of suspect it's a local issue. Assuming your cellphone and ISP providers aren't the same, I'd think it's likely not an ISP issue. It kind of seems like the problem is here, the timestamps don't reflect the almost 8 min. idle connection. 8/18/2024 8:16:40 PM | climateprediction.net | update requested by user 8/18/2024 8:16:44 PM | climateprediction.net | [http] HTTP_OP::init_get(): https://climateprediction.net/ 8/18/2024 8:16:44 PM | climateprediction.net | Fetching scheduler list 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Too old connection (474 seconds idle), disconnect it 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Connection 2004 seems to be dead 8/18/2024 8:16:44 PM | climateprediction.net | [http] [ID#1] Info: Closing connection 2004 Afterwards a connection is attempted to the http version of the site, where you'd expect to have problems as it's not secure (http vs https). Not sure why there are 2 versions of the site up. |
|
Send message Joined: 1 Jan 07 Posts: 1061 Credit: 36,703,308 RAC: 9,860 |
It kind of seems like the problem is here, the timestamps don't reflect the almost 8 min. idle connection.No, that's perfectly normal - it's an old connection, possibly to somewhere else. And the next line is 'Trying 129.67.241.50:443...' - using port 443 implies that this is another https connection - again normal. 'climateprediction.net' is the full public name of the research project, and is used for security against spoofing, and to reassure users that they've ended up in the right place. 'cpdn.org' is a simpler reference to the BOINC sub-section: climateprediction has other irons in the fire too. |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
Skillz, as you tried 3 different hosts, presumably on the same local network, do you have any anti-virus software running that affects the hosts? I'm wondering if you have, try adding cpdn.org to the whitelist. Also, check the time on your machines. If that's not following a network timeserver that can interfere with SSL. As pointed out in an earlier message, the timestamps in the log could be off. The only other thing I can think of is have a look in Windows Credentials Manager and see if CPDN is mentioned there. If it is, delete the entry. Do you get anything useful in the pi-hole logs before you disabled it? (and double check it really is disabled) This is the key part of the log as Richard says. It points to a problem validating the CPDN site. 8/18/2024 8:16:45 PM | climateprediction.net | [http] [ID#1] Info: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline. --- CPDN Visiting Scientist |
|
Send message Joined: 1 Jan 07 Posts: 1061 Credit: 36,703,308 RAC: 9,860 |
This is the key part of the log as Richard says. It points to a problem validating the CPDN site.Actually, it points to a problem validating the climateprediction.net site - in networking terms, the two are different, and I believe they're hosted on different servers with different configurations. I've completed my list of 50 hosts which have been attached in the last three days. And it told me - nothing. All computer life is there: apart from the usual suspects, there are CPUs from Apple to ARM, operating systems from Android to Darwin, and BOINC from v7.14.2 to v8.0.2 No gaps that I can see. List (in XLS speadsheet format) available on request. |
|
Send message Joined: 29 Oct 17 Posts: 1049 Credit: 16,432,494 RAC: 17,331 |
Indeed, that's what I mean. 'climateprediction.net' is not going to be in use for much longer. They are rebranding to 'CPDN'. But that's a degression.... It's a local issue, nothing at the server side I can see. --- CPDN Visiting Scientist |
©2024 cpdn.org
