Message boards :
Number crunching :
freeproxy question
Message board moderation
Author | Message |
---|---|
nairb Send message Joined: 18 Mar 03 Posts: 201 Credit: 5,447,501 RAC: 5 |
So I go away for a few days... when I get back I find that Predictor/climate/einstein can all up/download/update fine. Seti - Well you know ..... it will up/download fine. BUT will NOT update at all - so cannot report completed work. 7/23/05 9:26:46 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 7/23/05 9:26:46 PM|SETI@home|No schedulers responded It will update on a machine thats directly connected to the internet but non of the machines that connect thru freeproxy will update. A reboot/start/stop/console mode dosent change it. Anybody else having problems with freeproxy?? Ta Nairb |
ChristianB Send message Joined: 11 Jul 01 Posts: 139 Credit: 90,213 RAC: 0 |
Yes i have these problems to. I have done some testing and tracing and found out that there is a request limit of 8kb within freeproxy. This means if your request to the scheduler is larger than 8 kb you receive a 500 Internal Server Error. To test this out you have to trace your boinc-traffic. I have created a new listening port (for example: 8080) just for boinc and activated the content tracing within freeproxy. In these logfiles you can see the request to the server and thge answer from the server. The solution for this problem is a bit difficult so if you still have problems to report your seti-wu's email to djangofett at gmx dot net and i will provide you a step by step guide. BOINC Doc | Team-Site | BOINC-Podcast |
Paul D. Buck Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0 |
Can you provide me with the same guide for adding to the Wiki? |
ralic Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0 |
Yes i have these problems to. I have done some testing and tracing and found out that there is a request limit of 8kb within freeproxy. This means if your request to the scheduler is larger than 8 kb you receive a 500 Internal Server Error. I have to admit that I find this very odd. I have scheduler requests that greatly exceed 8kb (e.g. 70kb for another project) and I have no problems whatsoever with freeproxy. The scheduler of the other project certainly does not reply with a 500 error. I don't get a 500 error back, unless the server has a temporary glitch and actually sends back a 500 error. This almost always happens with SAH and I believe it to be a problem with the SAH scheduler, not freeproxy. There are buffer sizes within freeproxy that can be customised if required, but I find that the defaults work just fine. On occasion, I have adjusted these buffer sizes in order to improve the readability of the trace logs, but that is all. When I'm finished with my tracing, I set them back to their defaults. The buffer sizes don't affect the performance of freeproxy here. I would certainly like to know more about how you determined that there is an 8kb limit in freeproxy. |
Thierry Van Driessche Send message Joined: 20 Aug 02 Posts: 3083 Credit: 150,096 RAC: 0 |
I have to admit that I find this very odd. I tried here in Belgium using a freeproxy in the country, could return the results but can't get fresh WU's with it. |
fic Send message Joined: 15 Jul 99 Posts: 57 Credit: 1,075,709 RAC: 0 |
I tried here in Belgium using a freeproxy in the country, could return the results but can't get fresh WU's with it. Try this one 128.32.18.173 (port 80) Worked for me (also Belgium). |
Thierry Van Driessche Send message Joined: 20 Aug 02 Posts: 3083 Credit: 150,096 RAC: 0 |
Thanks fic, I tried another one which seems to work 62.58.201.18 port 444. |
ralic Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0 |
I tried here in Belgium using a freeproxy in the country, could return the results but can't get fresh WU's with it. I think the topic under discussion is not a free proxy, but "FreeProxy", which is a free of charge windows proxy product by Hand Crafted Software. But then again, I could be wrong... :) |
ChristianB Send message Joined: 11 Jul 01 Posts: 139 Credit: 90,213 RAC: 0 |
Yes i have these problems to. I have done some testing and tracing and found out that there is a request limit of 8kb within freeproxy. This means if your request to the scheduler is larger than 8 kb you receive a 500 Internal Server Error. I used freeproxy to trace the requests between my Client and Seti-Server. It just gets Internal Server Errors until the request size drops under 7842 byte. I've tested this several times and can send you my log-files. To adjust the size of the request i edited my client_state.xml. I just cut out some results and the request is smaller. btw: where can i set these internal buffer size? BOINC Doc | Team-Site | BOINC-Podcast |
ralic Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0 |
I used freeproxy to trace the requests between my Client and Seti-Server. It just gets Internal Server Errors until the request size drops under 7842 byte. I've tested this several times and can send you my log-files. To adjust the size of the request i edited my client_state.xml. I just cut out some results and the request is smaller. From what you're saying, I would still be inclined to maintain that the SAH scheduler (or the Apache config on the scheduler?) is the problem, rather than FreeProxy. You can check this yourself if you are attached to another project. I'll bet that you'll find scheduler requests > 8kb work just fine through FreeProxy to the other projects. With the recent problems plaguing SAH, I haven't been able to get any reasonable number of wu's from here, but once things are back to normal, I'll try remember to keep an eye on it. btw: where can i set these internal buffer size? The buffer sizes are located in the registry at HKLM\\SOFTWARE\\Hand-Crafted Software\\FreeProxy\\Buffer There are 5 buffers (default values in brackets): FTPBuffer (2000) HTTPBuffer (4000) SocksBuffer (1000) TunnelBuffer (2000) WebBuffer (2000) Off hand I seem to recall that the maximum values are 10000, but I'm sure you can find more details at their web site. You can play with these buffer sizes, but you may actually find degraded service if they are set too high/low. I only find it useful to resize them when tracing because it makes the traces easier to assemble. Thereafter, I set them back to the defaults. [edit] Reading your explanation regarding scheduler requests > 8kb to SAH in relation to nairb's problem, I expect that you could well have identified the source of that particular problem. IMHO FreeProxy is not the cause. Rather, it is that the SAH scheduler cannot interpret and respond correctly to requests > than 8kb. nairb, I would suggest that you liase with Boba Fett to manually reduce the size of your SAH scheduler requests if they are > 8kb. I seem to recall a similar problem with CPDN when the number of trickles exceeded a certain number. It was tagged and fixed, but I don't recall the specifics. I'll do some digging and see if the same solution could be applied to SAH. [/edit] |
ralic Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0 |
... I just cut out some results and the request is smaller. Boba, In your experiences, approximately how many results in the "ready to report" state cause a request file size > 8kb? TIA |
nairb Send message Joined: 18 Mar 03 Posts: 201 Credit: 5,447,501 RAC: 5 |
First - thanks for the replies. I ended up with six machines that would not Update. This evening I decided to check the 8k limit on freeproxy having tried the following:- Start/stop freeproxy change the proxyserver change the type of proxy reboot the whole network take a dead machine off the net and contact directly (no proxyserver) ipconfig /flushdns compare the xml file from a good machine with bad - could not find a problem. Set up a second boinc on the dead machine which worked fine but the dead boinc still would not Update. Did this to all dead machines. Endless start/stop freeproxy - in console mode and service. Tried Updating all the dead boinc each day. Used Ethereal to watch the server request fail Nothing helped at all. So, tonight I stopped freeproxy and started it with debug/logging. Started up a dead boinc and did an update......... work fine!!! Started up all the boinc on the machines which would not update....... ALL Updated fine. Repeat... They all updated fine. So..... the other thing which happened tonight was the database backup. Schedulers down. Did a scheduler restart fix it??? This 8k limit. I run predictor on one machine that does a wu in half an hour. In 3.5 days thats 168 wu or so to return. Way more than any seti machine I have. It always updates fine. But I will check next time to see what the result size is. My money is on the scheduler restart fixing it. Freeproxy has worked fine for a couple of years for me until now. Thanks Nairb |
ChristianB Send message Joined: 11 Jul 01 Posts: 139 Credit: 90,213 RAC: 0 |
... I just cut out some results and the request is smaller. approx. 6 Results but this depeds on how much data is in the <std_err> fields. I have mailed my first request that failed (24 Results) to davea and he checked it against the scheduler with no error. Later i send him the traces and he said that this probably could be a buffer size within freeproxy. Next time (friday or saturday) i will try another proxy-software. BOINC Doc | Team-Site | BOINC-Podcast |
ChristianB Send message Joined: 11 Jul 01 Posts: 139 Credit: 90,213 RAC: 0 |
Her is an actual report. I tryed to reproduce the problem with freeproxy and had 10 Results to upload. So BOINC starts to upload the first three results and reports them via RPC to the Scheduler. It automatically reported every 3 results so the sched_request was 20 WU's in Queue and will try next week again. Is there a way to suppress the RPC and only allow to upload the results but not report them?? BOINC Doc | Team-Site | BOINC-Podcast |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
Is there a way to suppress the RPC and only allow to upload the results but not report them?? Try with setting all projects to "No new work" before enable uploading... |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
Taking a look in the logs, it doesn't seem there is any problems returning many results to SETI@home either... 2005-07-21 03:11:12 [SETI@home] Requesting 0 seconds of work, returning 49 results 2005-07-21 03:11:19 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded Using freeproxy v3.81 build 1514, in case it's a version-problem... |
ChristianB Send message Joined: 11 Jul 01 Posts: 139 Credit: 90,213 RAC: 0 |
I have freeproxy v3.81 build 1514 also. Today i've tested some other proxy software after getting a 500 Internal Server Error with freeproxy. I've used Proxy+ 3.00 (Build #232) and there the whole request (20,7 KB) went to the server without an error. So this problem is solved in my case. BOINC Doc | Team-Site | BOINC-Podcast |
©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.