From WCG support : Scheduler request failed: HTTP file not found

From WCG support forum

Scheduler request failed: HTTP file not found
Your BOINC client will now start seeing this message as we transition from having our schedulers located at https://grid.worldcommunitygrid.org/boinc/wcg_cgi/fcgi to having them located at https://scheduler.worldcommunitygrid...c/wcg_cgi/fcgi

Unfortunately, there is no way to do this 'gracefully'. Instead your client will attempt 10-15 times to connect to the old scheduler before contacting the main website page in order to find out the current location of the scheduler. Once that happens, it will resume communicating properly. This will all happen automatically if left alone.

If you wish to complete this process faster on your machine, then please go to the 'Advanced View' of the software, then go to the 'Projects' tab, Select 'World Community Grid' and click on the 'Update' button. If you do this repeatedly (10-15 times) it will eventually fetch the new location.

If you are more technically inclined, then you can stop the BOINC client, edit the client_state.xml and find the line that says:

<scheduler_url>https://grid.worldcommunitygrid.org/boinc/wcg_cgi/fcgi</scheduler_url>

and replace it with

<scheduler_url>https://scheduler.worldcommunitygrid.org/boinc/wcg_cgi/fcgi</scheduler_url>


Save the file and then start your the BOINC client again. You should now be able to connect successfully.
"

Hit the update button about 30x and it'll trigger the master file download :up:

Good luck on the bigger farms.

It'll sort itself out on it's own if you just ignore it. I suspect the big farm guys use something like BOINCTasks to manage their farms so the whole plot can update at once if need be.

Both of my rigs have already been updated automatically.

I was wondering what happened to my farm... That explains it! (Thanks Karl)


and 1396 results just waiting to be returned - talk about a huge dump! :rofl:

I found this link:
https://secure.worldcommunitygrid.or...d_thread,33481

Looks like it was intentional.

Having a problem with downloads/uploads today.

They like taking those servers offline first thing in the morning. Can't upload ATM.

My office PC is jammed up trying to download. Been trying to download files most of today. Occasionally it'll get a piece of a file through but that's it. My queue is starting to run a little thin (this PC always has a very short queue for some reason, no matter what I tell it to do).

I am also getting "servers may be down" for the last couple of hours......

Quote:

---

Originally Posted by karl.martin

If you are more technically inclined, then you can stop the BOINC client, edit the client_state.xml and find the line that says:

<scheduler_url>https://grid.worldcommunitygrid.org/boinc/wcg_cgi/fcgi</scheduler_url>

and replace it with

<scheduler_url>https://scheduler.worldcommunitygrid.org/boinc/wcg_cgi/fcgi</scheduler_url>


Save the file and then start your the BOINC client again. You should now be able to connect successfully.
"

---

Worked for me - thanks karl.martin! :up:

I keep getting the following message on and off for the past couple of days

Attachment 128828

same here - cant upload any files but i can download them

I've edited the file and clicked on update more than 20 times but I still can't get it working.

It eventually says master file download succeeded but the scheduler request still fails.

From World Community Grid Tech

Quote:

---

We experienced an outage that caused the website to be unavaible for about 30 minutes. The website and the forums are now back up. We are working towards getting the backend processes (which include BOINC uploads and downloads) up and running. There is not an ETA on this yet. We will let you know as soon as possible.

Thank you for your patience,

--------------------------------
It is going to take a while. During some testing of the SAN performance, a small portion of the GPFS file system was corrupted. We are taking the time to create a current copy of the filesystem now before we attempt any sort of repair activity.
Unfortunately when you are moving nearly a TB of data around it takes a lot of time.

---

Ah! Thank you.

Update

Quote:

---

We are estimating at this point that with backups and restores and related work to recover it is going to take us 12-18 hours before we will be able to resume operations. We will advise and update as we go

---

didn't even notice my pc was almost out of work, well it will get new work when the servers are up:)

Update:

Quote:

---

We have completed the backup of the filesystem and have rebuilt it. We are now in the process of copying the data back onto the filesystem.

However, because the filesystem was corrupted when we copied data off, we are in the process of validating files in different ways. We already have our work underway to ensure that no corrupted files are returned to the researchers and these scans against the files are running now. We are now working on validating the workunit input files. This is being done in order to minimize the disruptions in workunit distribution when we resume sending/receiving work. The boinc client will verify the download file and application binaries against signatures and hashes that were computed before the file system issue occurred. As a result, they will be rejected if we miss a few corrupt files. However, we are running scans now to ensure that will only be a very small number of files and not 1000's.

---

We have completed the restore back to the filesystems.

Quote:

---

We have done a scan of the job input files and we are seeing about 0.2% of input files corrupted. We are going to cancel the impact jobs and reload those jobs. This may cause some aborts on jobs in progress.

Also - for results that are in progress and due less than 24 hours from now, we are moving the report deadline to 24 hours from now. This will minimize issues with jobs that have missed their deadline. You will not see this on the client - but only in the website.

Files that have already been uploaded will be examined as they pass through normal validation.

---

Uploads are active again but the "reporting tasks" is still returing "project down for maintenance". The message is misleading as the project is not down but this is the message we get when it is too busy. Due to the heavy weight nature of "reporting tasks" the servers are likely swamped but I think we just need to be patient a little longer :up:

And report completed tasks are being processed again !!!

so this is why i'm running out of tasks?

thought i had :banana::banana::banana::banana:ed something up :rofl: