wiki:Error/Scheduler request failed

Version 1 (modified by Didactylos, 17 years ago) (diff)

Initial version

Errors

Core client errors

Scheduler request failed: peer certificate cannot be authenticated with known CA certificates

This error most frequently occurs because of incorrect date settings on your computer. To correct the problem, correct your computer clock. 

9-2-2006 4:33:20|World Community Grid|Resetting project
9-2-2006 4:33:28|World Community Grid|Sending scheduler request: Requested by user
9-2-2006 4:33:28|World Community Grid|Requesting 527040 seconds of new work
9-2-2006 4:33:29||Project communication failed: attempting access to reference site
9-2-2006 4:33:31||Access to reference site succeeded - project servers may be temporarily down.
9-2-2006 4:33:34|World Community Grid|Scheduler request failed: peer certificate cannot be authenticated with known CA certificates
9-2-2006 4:33:34|World Community Grid|Deferring communication for 15 min 27 sec
9-2-2006 4:33:34|World Community Grid|Reason: scheduler request failed

Why does this problem only affect WCG, and not other BOINC projects? This is because WCG is (at the time of writing) the only BOINC project that requires a secure connection to the server. Other projects permit falling back to an insecure connection.

Scheduler request failed: problem with the SSL CA cert (path? access rights?)

This is a known problem with some ported BOINC releases, especially certain Linux x64 ports. The reason for the error is that a file (ca-bundle.crt) was omitted from the release.

If you see this error message in your message log, then you probably need to apply this fix.

  1. Determine your BOINC data directory. Check the beginning of your message log. There will be a line near the beginning like this: 
    08/06/2007 13:18:00||Data directory: C:\Program Files\BOINC
  2. Download the missing file. You can get it from here: trunk/boinc/curl/ca-bundle.crt?format=raw - make sure you name the file ca-bundle.crt.
  3. Place the file in your BOINC data directory.
  4. Restart BOINC. The way you do this will depend on your installation.

Why does this problem only affect WCG, and not other BOINC projects? This is because WCG is (at the time of writing) the only BOINC project that requires a secure connection to the server. Other projects permit falling back to an insecure connection.

FreeBSD note: this issue has been fixed, please update your port-tree and rebuild BOINC.

Manager errors