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: 24
Posts: 24   Pages: 3   [ 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 5015 times and has 23 replies Next Thread
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1673
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
2021-02-20 Scheduler request failed: HTTP internal server error [SOLVED]

Edit: The number of machines experiencing troubles is growing!
---
Since about 8 hours, 2 3 Linux machines of 7 (+1 Windows) are not able to report.
The results are correctly uploaded.
However the results cannot be reported and it is also not possible to download new work:
Scheduler request failed: HTTP internal server error 

Even a reboot did not help.
It is very strange.
Cheers,
Yves
----------------------------------------
----------------------------------------
[Edit 2 times, last edit by KerSamson at Feb 22, 2021 10:57:24 PM]
[Feb 20, 2021 6:20:58 PM]   Link   Report threatening or abusive post: please login first  Go to top 
PMH_UK
Veteran Cruncher
UK
Joined: Apr 26, 2007
Post Count: 772
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

----------------------------------------
Paul.
[Feb 20, 2021 8:17:27 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1673
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

Hi Paul,
I thank you for the observation. However it seems to be different.
In my case, I have only the "Scheduler request failed: HTTP internal server error" message; nothing more.
It started with one machine, a little bit later, a second one, and 6 hours later a third one.
Since I am currently keeping the buffers relatively small (<1 day), the machines are close to run dry.
As usual, it's occurring during a week-end.
Cheers,
Yves
----------------------------------------
[Feb 20, 2021 8:45:58 PM]   Link   Report threatening or abusive post: please login first  Go to top 
PMH_UK
Veteran Cruncher
UK
Joined: Apr 26, 2007
Post Count: 772
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

Yves,

Apologies, more details in original thread here:
https://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=651733

Details in log depend on log options, adding optins for http revealed more details.

Paul.
----------------------------------------
Paul.
[Feb 20, 2021 10:47:35 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Mike.Gibson
Ace Cruncher
England
Joined: Aug 23, 2007
Post Count: 12425
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

Yves

I am still waiting for Uplinger to come back to me, However, he has been involved in getting the GPUs started on opn so he has been a bit busy, I presume.

I'll keep you posted.

In my case it is only my PC that has the problem. My phone, tablet & laptop are all ok.

However it is down to the last 25% of the last unit.

In your case, have you checked the result status for your uploaded units? Mine have validated. They will not report or fetch new work.

Mike
[Feb 21, 2021 1:34:27 AM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1673
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

In your case, have you checked the result status for your uploaded units? Mine have validated.

Hi Mike,
indeed all the WUs have been uploaded and validated.
Because the WUs cannot be reported, it is not possible to get new work.
I will turn on the log option and have a deeper look.
Cheers,
Yves
----------------------------------------
[Feb 21, 2021 7:49:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1673
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

Here is the debug log:
2021-02-21 08:51:02	Config: report completed tasks immediately	
2021-02-21 08:51:02 log flags: file_xfer, sched_ops, task, http_debug
World Community Grid 2021-02-21 08:51:02 Found app_config.xml
World Community Grid 2021-02-21 08:51:34 update requested by user
2021-02-21 08:51:34 [http] HTTP_OP::init_get(): https://www.worldcommunitygrid.org/viewNotice...b68cd78f1f27ca13ab0144bb5
2021-02-21 08:51:35 [http] [ID#0] Info: Connection 48 seems to be dead!
2021-02-21 08:51:35 [http] [ID#0] Info: Closing connection 48
2021-02-21 08:51:36 [http] [ID#0] Info: Trying 169.47.63.74...
2021-02-21 08:51:36 [http] [ID#0] Info: Connected to www.worldcommunitygrid.org (169.47.63.74) port 443 (#49)
2021-02-21 08:51:36 [http] [ID#0] Info: ALPN, offering http/1.1
2021-02-21 08:51:36 [http] [ID#0] Info: Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
2021-02-21 08:51:36 [http] [ID#0] Info: successfully set certificate verify locations:
2021-02-21 08:51:36 [http] [ID#0] Info: CAfile: ca-bundle.crt
2021-02-21 08:51:36 [http] [ID#0] Info: CApath: /etc/ssl/certs
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (OUT), TLS header, Certificate Status (22):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (OUT), TLS handshake, Client hello (1):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (IN), TLS handshake, Server hello (2):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (IN), TLS handshake, Certificate (11):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (IN), TLS handshake, Server finished (14):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (OUT), TLS change cipher, Client hello (1):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (OUT), TLS handshake, Finished (20):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (IN), TLS change cipher, Client hello (1):
2021-02-21 08:51:36 [http] [ID#0] Info: TLSv1.2 (IN), TLS handshake, Finished (20):
2021-02-21 08:51:36 [http] [ID#0] Info: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
2021-02-21 08:51:36 [http] [ID#0] Info: ALPN, server accepted to use http/1.1
2021-02-21 08:51:36 [http] [ID#0] Info: Server certificate:
2021-02-21 08:51:36 [http] [ID#0] Info: subject: C=US; ST=New York; L=Armonk; O=International Business Machines Corporation; CN=*.worldcommunitygrid.org
2021-02-21 08:51:36 [http] [ID#0] Info: start date: Jun 10 00:00:00 2020 GMT
2021-02-21 08:51:36 [http] [ID#0] Info: expire date: Sep 9 12:00:00 2022 GMT
2021-02-21 08:51:36 [http] [ID#0] Info: subjectAltName: www.worldcommunitygrid.org matched
2021-02-21 08:51:36 [http] [ID#0] Info: issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=Thawte RSA CA 2018
2021-02-21 08:51:36 [http] [ID#0] Info: SSL certificate verify ok.
2021-02-21 08:51:36 [http] [ID#0] Sent header to server: GET /viewNoticesRSSFeed.action?userIdHash=314381_f6174d6b68cd78f1f27ca13ab0144bb5 HTTP/1.1
2021-02-21 08:51:36 [http] [ID#0] Sent header to server: Host: www.worldcommunitygrid.org
2021-02-21 08:51:36 [http] [ID#0] Sent header to server: User-Agent: BOINC client (x86_64-pc-linux-gnu 7.6.31)
2021-02-21 08:51:36 [http] [ID#0] Sent header to server: Accept: */*
2021-02-21 08:51:36 [http] [ID#0] Sent header to server: Accept-Encoding: deflate, gzip
2021-02-21 08:51:36 [http] [ID#0] Sent header to server: Content-Type: application/x-www-form-urlencoded
2021-02-21 08:51:36 [http] [ID#0] Sent header to server: Accept-Language: en_US
2021-02-21 08:51:36 [http] [ID#0] Sent header to server:
2021-02-21 08:51:36 [http] [ID#0] Received header from server: HTTP/1.1 200 OK
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Date: Sun, 21 Feb 2021 07:51:36 GMT
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Server: Apache
2021-02-21 08:51:36 [http] [ID#0] Received header from server: X-Powered-By: Servlet/3.1
2021-02-21 08:51:36 [http] [ID#0] Received header from server: ETag: 1356985405
2021-02-21 08:51:36 [http] [ID#0] Received header from server: X-Content-Type-Options: nosniff
2021-02-21 08:51:36 [http] [ID#0] Received header from server: X-XSS-Protection: 1; mode=block
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Cache-Control: no-cache, no-store, max-age=0, must-revalidate
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Pragma: no-cache
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Expires: 0
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Strict-Transport-Security: max-age=31536000; includeSubDomains
2021-02-21 08:51:36 [http] [ID#0] Received header from server: X-Frame-Options: SAMEORIGIN
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Vary: Accept-Encoding
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Content-Encoding: gzip
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Referrer-Policy: no-referrer-when-downgrade
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://tagmanager.google.com https://d2bnxibecyz4h5.cloudfront.net https://www.google
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Content-Type: text/xml; charset=UTF-8
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Content-Language: en-US
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Set-Cookie: WCG-SESSION=0000j5uDXJcjGkJ3Y_YILejU0LG:-1; Expires=Sun, 21-Feb-21 08:21:35 GMT; Path=/; Domain=.worldcommunitygrid.org; Secure; HttpOnly
2021-02-21 08:51:36 [http] [ID#0] Received header from server: Transfer-Encoding: chunked
2021-02-21 08:51:36 [http] [ID#0] Received header from server:
2021-02-21 08:51:36 [http] [ID#0] Received header from server: 2ff
2021-02-21 08:51:36 [http] [ID#0] Received header from server: ‹
2021-02-21 08:51:36 [http] [ID#0] Info: Connection #49 to host www.worldcommunitygrid.org left intact
World Community Grid 2021-02-21 08:51:38 Sending scheduler request: Requested by user.
World Community Grid 2021-02-21 08:51:38 Reporting 21 completed tasks
World Community Grid 2021-02-21 08:51:38 Requesting new tasks for CPU
World Community Grid 2021-02-21 08:51:38 [http] HTTP_OP::init_post(): https://scheduler.worldcommunitygrid.org/boinc/wcg_cgi/fcgi
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: Trying 169.47.63.74...
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: Connected to scheduler.worldcommunitygrid.org (169.47.63.74) port 443 (#50)
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: ALPN, offering http/1.1
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: successfully set certificate verify locations:
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: CAfile: ca-bundle.crt
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: CApath: /etc/ssl/certs
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (OUT), TLS header, Certificate Status (22):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (OUT), TLS handshake, Client hello (1):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (IN), TLS handshake, Server hello (2):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (IN), TLS handshake, Certificate (11):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (IN), TLS handshake, Server finished (14):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (OUT), TLS change cipher, Client hello (1):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (OUT), TLS handshake, Finished (20):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (IN), TLS change cipher, Client hello (1):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: TLSv1.2 (IN), TLS handshake, Finished (20):
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: ALPN, server accepted to use http/1.1
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: Server certificate:
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: subject: C=US; ST=New York; L=Armonk; O=International Business Machines Corporation; CN=*.worldcommunitygrid.org
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: start date: Jun 10 00:00:00 2020 GMT
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: expire date: Sep 9 12:00:00 2022 GMT
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: subjectAltName: scheduler.worldcommunitygrid.org matched
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=Thawte RSA CA 2018
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: SSL certificate verify ok.
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: POST /boinc/wcg_cgi/fcgi HTTP/1.1
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: Host: scheduler.worldcommunitygrid.org
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: User-Agent: BOINC client (x86_64-pc-linux-gnu 7.6.31)
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: Accept: */*
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: Accept-Language: en_US
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: Content-Length: 99026
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server: Expect: 100-continue
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Sent header to server:
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Received header from server: HTTP/1.1 100 Continue
World Community Grid 2021-02-21 08:51:39 [http] [ID#1] Info: We are completely uploaded and fine
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: HTTP/1.1 500 Internal Server Error
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: Date: Sun, 21 Feb 2021 07:51:39 GMT
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: Server: Apache
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: Content-Length: 527
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: Content-Type: text/html; charset=iso-8859-1
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server:
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: <html><head>
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: <title>500 Internal Server Error</title>
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: </head><body>
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: <h1>Internal Server Error</h1>
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: <p>The server encountered an internal error or
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: misconfiguration and was unable to complete
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: your request.</p>
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: <p>Please contact the server administrator at
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: root@localhost to inform them of the time this error occurred,
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: and the actions you performed just before this error.</p>
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: <p>More information about this error may be available
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Received header from server: in the server error log.</p>
World Community Grid 2021-02-21 08:51:40
World Community Grid 2021-02-21 08:51:40 [http] [ID#1] Info: Connection #50 to host scheduler.worldcommunitygrid.org left intact
World Community Grid 2021-02-21 08:51:41 Scheduler request failed: HTTP internal server error

It looks like that it is not a certificate failure.
Cheers,
Yves
----------------------------------------
[Feb 21, 2021 8:03:16 AM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1673
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

Until now, it is interesting to notice that the 2 RPi and the Windows 7 machine are not impacted as well as the 2 Linux machines at the second location.
Yves
----------------------------------------
[Feb 21, 2021 8:08:27 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Mike.Gibson
Ace Cruncher
England
Joined: Aug 23, 2007
Post Count: 12425
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

In my case it is a Win7 PC but my Win7 Laptop is not affected, so that doesn't seem to be the reason.
[Feb 21, 2021 1:36:18 PM]   Link   Report threatening or abusive post: please login first  Go to top 
PMH_UK
Veteran Cruncher
UK
Joined: Apr 26, 2007
Post Count: 772
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: 2021-02-20 Scheduler request failed: HTTP internal server error

That log confirms also 500 Internal Server Error.
Suggest copy sched_request and sched_reply for each system and send to support if requested.

Paul.
----------------------------------------
Paul.
[Feb 21, 2021 1:59:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 24   Pages: 3   [ 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread