| Subject: Re: Connections to ssl.berkeley not propagated yet? |
| From: Patrick Vervoorn |
| Date: 27/07/2005, 13:51 |
In article <ZeGCsWArN05CFwY$@consltec.demon.co.uk>,
John <fredclark@consltec.demon.co.uk> wrote:
[snip]
COMMENT
I assume my ISP is one of those with a finicky DNS server, or the DNS
change has yet to propagate in my ISPs direction.
QUESTION
Anyone else from the UK (or other areas) currently with the problem of
"No schedulers responded" on the BOINC messages tab?
Yes, I had the same problem, but after several hours the DNS server's
records were updated, and I could reach the seti servers again. I have no
idea if/how I could have speeded up this process.
What I was however seeing during this period is that SetiBOINC was idling,
while I had 3 workunits sitting in the projects/setiatime.berkeley.edu/
directory (this on a Linux machine).
I tried exiting/restarting BOINC, but it did not start computation of
those WU's, and after a restart automatically deferred contacting the seti
servers for several hours.
I then deleted the sched_* files in the main BOINC/ directory: no change.
I then finally deleted the the client_state*.xml files, and that caused
SetiBOINC to contact the servers again, and downloading some totally new
and different WU's, and started processing them.
I've now deleted the 3 other (older) WU's which were still sitting in that
directory, since I didn't expect SetiBOINC to start processing those.
All this with the Linux client version 4.43 (latest AFAIK).
My questions:
- Why did SetiBOINC not process the WU's it had already downloaded? This
is a P3-733MHz machine, so those 3 WU's should have lasted it for at
least a day or two. Instead it decided to just sit there idling, and
periodically checking the Berkeley site for 'something'?
- When I look at my Account page, I see those 3 WU's being listed as sent
out for that particular machine, but since I deleted them locally, the
results will never be returned. Is this a problem? Is there also a way
for me to redownload those WU's?
I also tried Googling for this problem, and it seems to happen, sometimes,
to other people, but I've not found any fixed problem. Mostly, I saw
people installing an older version. I suppose this 'fix' also loses some
WU's.
Anyone know of a solution for the above?
I do hope this doesn't happen more often, because it's quite a hassle. :(
Regards,
Patrick.