Scheduler request failed: Error 403

Questions and Answers : Windows : Scheduler request failed: Error 403
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile startrekforever

Send message
Joined: 5 Dec 99
Posts: 36
Credit: 17,772,420
RAC: 0
United States
Message 940858 - Posted: 17 Oct 2009, 19:38:49 UTC

I have several machines running BOINC for Seti@home and over the course of the past few months as I ramp up CUDA systems I seem to be getting 'Scheduler request failed: Error 403' messages about once a month. When it happens it seems the only way to correct the issue has been to disconnect/uninstall and reinstall/reconnect. It bit me again today as I saw my MLIDVWINTA02 system getting the message after finishing up over 500 tasks and trying to report them. The tasks I did still see in my task window all finished within a minute which was very strange too. Since the system is in the office, running Server 2008 under a domain account, I cannot reset it remotely. (When using Remote Desktop and doing any restart of BOINC, BOINC never sees the CUDA processor since Remote Desktop goes in using a pseudo graphic system, so I always have to be in front of the system to do an install.)

Anyone else been plagued with the 403 (HTTP code meaning 'forbidden') message?

ID: 940858 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 940912 - Posted: 17 Oct 2009, 22:28:16 UTC - in response to Message 940858.  

I assume it goes through a proxy? if so, try setting that system up with HTTP 1.0

For this, make a cc_config.xml file in the BOINC Data directory.
Add into it these lines:

<cc_config>
<options>
<http_1_0>1</http_1_0>
</options>
</cc_config>


Save the file, make sure the extension is .xml, not something else (like Notepad likes to make it .txt).

Then either restart BOINC, or open BOINC Manager->Advanced view->Advanced->Read config file.
ID: 940912 · Report as offensive
Profile startrekforever

Send message
Joined: 5 Dec 99
Posts: 36
Credit: 17,772,420
RAC: 0
United States
Message 941340 - Posted: 19 Oct 2009, 14:18:26 UTC

I added the cc_config file, but a read of it did not fix the issue. I wound up resetting the project, and I am back up for now.

ID: 941340 · Report as offensive
Profile startrekforever

Send message
Joined: 5 Dec 99
Posts: 36
Credit: 17,772,420
RAC: 0
United States
Message 941382 - Posted: 19 Oct 2009, 17:01:02 UTC - in response to Message 941340.  

Turns out that cc_config on my 'proxied' machine prevented all internet access. Had to disable that config.
ID: 941382 · Report as offensive
Alessandro Freda

Send message
Joined: 18 May 99
Posts: 2
Credit: 510,881
RAC: 0
Italy
Message 944633 - Posted: 2 Nov 2009, 16:43:06 UTC

Since I'll like to test the new x86_64 test application for windows I've attached a 64 bit server and see the same problem:

11/2/2009 5:38:20 PM|boincsimap|Sending scheduler request: Requested by user. Requesting 2033120 seconds of work, reporting 0 completed tasks
11/2/2009 5:38:25 PM|boincsimap|Scheduler request failed: Error 403

but only on the win2003 server x86_64, all the other 32bit PCs works fine with the same proxy configuration (that already include the cc_config.xml file with the <http_1_0>1</http_1_0> param).

Any ideas ?

ID: 944633 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 944635 - Posted: 2 Nov 2009, 16:55:28 UTC - in response to Message 944633.  

You don't say which BOINC version you're testing with.
ID: 944635 · Report as offensive
Alessandro Freda

Send message
Joined: 18 May 99
Posts: 2
Credit: 510,881
RAC: 0
Italy
Message 944679 - Posted: 2 Nov 2009, 20:13:48 UTC - in response to Message 944635.  

Ops, wrong forum, the problem was about SIMAP ... my mistake sorry :)

ID: 944679 · Report as offensive

Questions and Answers : Windows : Scheduler request failed: Error 403


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.