climateprediction.net home page
Scheduler request failed.

Scheduler request failed.

Message boards : Number crunching : Scheduler request failed.
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Dave Jackson
Volunteer moderator

Send message
Joined: 15 May 09
Posts: 2738
Credit: 3,388,112
RAC: 2,679
Message 57955 - Posted: 19 Mar 2018, 18:18:38 UTC

Getting this at the moment

19/03/2018 17:29:55 | climateprediction.net | Sending scheduler request: To send trickle-up message.
19/03/2018 17:29:55 | climateprediction.net | Not requesting tasks: don't need (job cache full)
19/03/2018 17:34:37 | climateprediction.net | [checkpoint] result wah2_eu25_qi1y_200712_13_709_011481271_1 checkpointed
19/03/2018 17:34:57 | climateprediction.net | Scheduler request failed: Error 408
19/03/2018 17:44:16 | climateprediction.net | [checkpoint] result wah2_sas50_q847_201612_13_708_011457636_2 checkpointed
19/03/2018 17:47:42 | climateprediction.net | Started upload of wah2_sas50_q847_201612_13_708_011457636_2_r1478752478_7.zip
19/03/2018 17:48:05 | climateprediction.net | Backing off 05:43:58 on upload of wah2_sas50_q847_201612_13_708_011457636_2_r1478752478_7.zip



Nothing useful from http debug.
ID: 57955 · Report as offensive     Reply Quote
Profile Dave Jackson
Volunteer moderator

Send message
Joined: 15 May 09
Posts: 2738
Credit: 3,388,112
RAC: 2,679
Message 57956 - Posted: 20 Mar 2018, 7:51:20 UTC - in response to Message 57955.  
Last modified: 20 Mar 2018, 8:04:15 UTC

Had the chance to try and eliminate some possibilities. Looking up the error I found this.

The Web server (running the Web site) thinks that there has been too long an interval of time between 1) the establishment of an IP connection (socket) between the client (e.g. your Web browser or our CheckUpDown robot) and the server and 2) the receipt of any data on that socket, so the server has dropped the connection. The socket connection has actually been lost - the Web server has 'timed out' on that particular socket connection. The request from the client must be repeated - in a timely manner.


I then tried an alternate project (numberfields@home) and scheduler request there worked fine and was able to get new work.

Could this possibly be related to a new router and the fact that the connection is wireless rather than a cable? The old router had also been wireless to other machines without problems. I am waiting to see if anyone else is experiencing problems before raising it with the project.

Edit: After another attempt manually clicking the update button for the project the scheduler request completed but the zip is still not uploading. While a few people might be happy about getting the credit, for me the science is way more important - anyone else struggling with zips on batch 708 at the moment?
ID: 57956 · Report as offensive     Reply Quote
Profile Dave Jackson
Volunteer moderator

Send message
Joined: 15 May 09
Posts: 2738
Credit: 3,388,112
RAC: 2,679
Message 57958 - Posted: 20 Mar 2018, 9:59:28 UTC - in response to Message 57956.  

Just for completeness, using old router connected by cable made no difference. Tasks on other projects are uploading fine.
ID: 57958 · Report as offensive     Reply Quote

Message boards : Number crunching : Scheduler request failed.

©2020 climateprediction.net