Subject: Re: Is anybody getting WU's for BOINC SETI?
From: "uray" <remove-uray@att.net>
Date: 30/12/2005, 02:37
Newsgroups: alt.sci.seti,sci.astro.seti

"Ulysse Keller" <DwarfPPE2004@swissonline.ch> wrote in message 
news:43b37637.457562@news.swissonline.ch...
On Fri, 23 Dec 2005 01:36:10 GMT, "uray" <remove-uray@att.net> wrote:

I haven't had any in weeks.  I keep getting "Master file fetch failed".  I
can't even get the website to come up.  Is it just me or is everybody 
having
this problem?

I have stopped even trying since about 10 days. I tried my first
BOINC-Install. some months ago, but had problems with it and "not
much time for these things" - so I continued with SETI classic
"until the last moment" which was in fact already on Dec.12 when
Classic stopped working normally. Then I de-installed SETI classic
and BOINC, then re-installed BOINC which "looks now a bit better"
(I tried this time to apply the config. tips for my system with WinXP
and several users defined.) But when BOINC seems to be ready
to get data from the internet (and even when it asks for them) I only
get following messages, where I am using the %% signs to mean
"this line appears in red":

(...)
15.12.2005 00:48:35|SETI@home|Sending scheduler request to

http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
15.12.2005 00:48:35|SETI@home|Reason: Requested by user
15.12.2005 00:48:35|SETI@home|Requesting 86400 seconds of new work
%% 15.12.2005 00:48:36||Couldn't resolve hostname
%%   [setiboinc.ssl.berkeley.edu]
%% 15.12.2005 00:48:36|SETI@home|Scheduler request to
%% http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
%%   failed with a return value of -113
%% 15.12.2005 00:48:36|SETI@home|No schedulers responded
15.12.2005 00:48:39||Suspending computation and network activity
- user is active
(... end of this messages quoting)

I don't understand why 'setiboinc.ssl.berkeley.edu' is not found ...

I was getting that as well.  Ultimately I fixed it by setting it to go 
through a proxy.  Funny thing is that after I did that I could remove the 
proxy and it continued to work.  After reading some posts at the SETI 
message board I discovered there's an issue with packet size.  Others have 
had the same problem and hopefully they will fix it in the BOINC software.