Hello all,
since more than a week, my BOINC client version 3.20 for windows_intelx86 can't establish a coummunication line in order do update the project status and for downloading new WU's.
I receive the following error mesage:
Master file fetch failed ... Deferring communication with project

I know, that there is a general issue regarding downloading new work, but in these cases the clients receive a clear message : 'no work from Project'.

In my case it looks like that some URL's have changed.

Thanx in advance ... Accolon

Accolon,

If you could post a few lines above and below that message from your messages tab, it would help us to help you.

It could be that you have not updated the new master URL yet.

Keep trying manual updates, as it should take 10 master fetch failed cycles until it searches for the new master URL.

A detach and re-attach should also reset this, but that's more drastic than is necessary.

Try the updates first, and if they don't work, see if you can post more from your log file as ralic says. :-)

<a> [/url]

Hello,

I've already tried to updated the master URL via this procedure and failed.
This morning I've tried it a second time without success.

as requested, my stderr log:
---------------------------------------------------------------------------
2004-07-25 10:37:44 [SETI@home] Deferring communication with project for 1 weeks, 1 days, 13 hours, 56 minutes, and 54 seconds
2004-07-25 10:38:10 [SETI@home] Master file fetch failed
2004-07-25 10:38:10 [SETI@home] Deferring communication with project for 1 weeks, 6 days, 11 hours, 30 minutes, and 2 seconds
2004-07-25 10:40:28 [SETI@home] Master file fetch failed
2004-07-25 10:40:28 [SETI@home] Deferring communication with project for 1 weeks, 1 days, 12 hours, 38 minutes, and 59 seconds
2004-07-25 10:40:55 [SETI@home] Master file fetch failed
2004-07-25 10:40:55 [SETI@home] Deferring communication with project for 1 days, 12 hours, 53 minutes, and 20 seconds
2004-07-25 10:41:21 [SETI@home] Master file fetch failed
2004-07-25 10:41:21 [SETI@home] Deferring communication with project for 5 days, 5 hours, 11 minutes, and 38 seconds
2004-07-25 10:41:49 [SETI@home] Master file fetch failed
2004-07-25 10:41:49 [SETI@home] Deferring communication with project for 1 weeks, 0 days, 13 hours, 7 minutes, and 40 seconds
2004-07-25 10:42:17 [SETI@home] Master file fetch failed
2004-07-25 10:42:17 [SETI@home] Deferring communication with project for 1 weeks, 5 days, 23 hours, 16 minutes, and 4 seconds
2004-07-25 10:42:45 [SETI@home] Master file fetch failed
2004-07-25 10:42:45 [SETI@home] Deferring communication with project for 4 days, 21 hours, 30 minutes, and 13 seconds
2004-07-25 10:43:12 [SETI@home] Master file fetch failed
2004-07-25 10:43:12 [SETI@home] Deferring communication with project for 1 days, 5 hours, 12 minutes, and 32 seconds
2004-07-25 10:43:39 [SETI@home] Master file fetch failed
2004-07-25 10:43:39 [SETI@home] Deferring communication with project for 21 hours, 36 minutes, and 2 seconds
2004-07-25 10:44:07 [SETI@home] Master file fetch failed
2004-07-25 10:44:07 [SETI@home] Deferring communication with project for 6 days, 1 hours, 45 minutes, and 46 seconds
2004-07-25 10:44:37 [SETI@home] Master file fetch failed
2004-07-25 10:44:37 [SETI@home] Deferring communication with project for 4 days, 9 hours, 41 minutes, and 29 seconds
2004-07-25 10:45:18 [SETI@home] Master file fetch failed
2004-07-25 10:45:18 [SETI@home] Deferring communication with project for 1 weeks, 0 days, 7 hours, 26 minutes, and 50 seconds
2004-07-25 10:45:53 [SETI@home] Master file fetch failed
2004-07-25 10:45:53 [SETI@home] Deferring communication with project for 5 days, 13 hours, 5 minutes, and 58 seconds
2004-07-25 10:46:58 [SETI@home] Master file fetch failed
2004-07-25 10:46:58 [SETI@home] Deferring communication with project for 1 weeks, 2 days, 0 hours, 38 minutes, and 48 seconds
2004-07-25 10:47:44 [SETI@home] Master file fetch failed
2004-07-25 10:47:44 [SETI@home] Deferring communication with project for 1 weeks, 2 days, 20 hours, 45 minutes, and 52 seconds
2004-07-25 10:48:14 [SETI@home] Master file fetch failed
2004-07-25 10:48:14 [SETI@home] Deferring communication with project for 4 days, 23 hours, 20 minutes, and 20 seconds
2004-07-25 10:48:43 [SETI@home] Master file fetch failed
2004-07-25 10:48:43 [SETI@home] Deferring communication with project for 1 weeks, 2 days, 9 hours, 14 minutes, and 58 seconds
2004-07-25 10:49:30 [SETI@home] Master file fetch failed
2004-07-25 10:49:30 [SETI@home] Deferring communication with project for 2 days, 3 hours, 14 minutes, and 39 seconds
2004-07-25 10:50:27 [SETI@home] Master file fetch failed
2004-07-25 10:50:27 [SETI@home] Deferring communication with project for 3 days, 8 hours, 16 minutes, and 57 seconds
2004-07-25 10:51:02 [SETI@home] Master file fetch failed
2004-07-25 10:51:02 [SETI@home] Deferring communication with project for 6 days, 1 hours, 39 minutes, and 37 seconds
2004-07-25 10:51:36 [SETI@home] Master file fetch failed
2004-07-25 10:51:36 [SETI@home] Deferring communication with project for 1 weeks, 4 days, 15 hours, 19 minutes, and 2 seconds
2004-07-25 10:52:07 [SETI@home] Master file fetch failed
2004-07-25 10:52:07 [SETI@home] Deferring communication with project for 2 days, 7 hours, 0 minutes, and 26 seconds
2004-07-25 10:52:41 [SETI@home] Master file fetch failed
2004-07-25 10:52:41 [SETI@home] Deferring communication with project for 1 weeks, 2 days, 12 hours, 0 minutes, and 28 seconds
2004-07-25 10:53:22 [SETI@home] Master file fetch failed
2004-07-25 10:53:22 [SETI@home] Deferring communication with project for 1 weeks, 4 days, 14 hours, 43 minutes, and 58 seconds
2004-07-25 10:54:00 [SETI@home] Master file fetch failed
2004-07-25 10:54:00 [SETI@home] Deferring communication with project for 1 days, 7 hours, 29 minutes, and 7 seconds
2004-07-25 10:54:30 [SETI@home] Master file fetch failed
2004-07-25 10:54:30 [SETI@home] Deferring communication with project for 3 days, 7 hours, 48 minutes, and 39 seconds
2004-07-25 10:55:01 [SETI@home] Master file fetch failed
2004-07-25 10:55:01 [SETI@home] Deferring communication with project for 3 days, 7 hours, 4 minutes, and 21 seconds
2004-07-25 10:55:35 [SETI@home] Master file fetch failed
2004-07-25 10:55:35 [SETI@home] Deferring communication with project for 1 weeks, 3 days, 8 hours, 54 minutes, and 17 seconds
2004-07-25 10:56:03 [SETI@home] Master file fetch failed
2004-07-25 10:56:03 [SETI@home] Deferring communication with project for 1 weeks, 5 days, 3 hours, 36 minutes, and 42 seconds
2004-07-25 10:57:06 [SETI@home] Master file fetch failed
2004-07-25 10:57:06 [SETI@home] Deferring communication with project for 1 weeks, 1 days, 21 hours, 36 minutes, and 42 seconds
2004-07-25 10:57:35 [SETI@home] Master file fetch failed
2004-07-25 10:57:35 [SETI@home] Deferring communication with project for 2 days, 0 hours, 58 minutes, and 4 seconds
2004-07-25 10:58:04 [SETI@home] Master file fetch failed
2004-07-25 10:58:04 [SETI@home] Deferring communication with project for 1 weeks, 5 days, 11 hours, 30 minutes, and 25 seconds
2004-07-25 10:58:41 [SETI@home] Master file fetch failed
2004-07-25 10:58:41 [SETI@home] Deferring communication with project for 2 days, 12 hours, 2 minutes, and 30 seconds
---------------------------------------------------------------------------

Thanx for your help.

Is it not possible to update the folowing ini files
1. account_setiboinc.ssl.berkeley.edu_sah.xml
2. sched_request.xml
3. client_state.xml

manualy ?

Hi,
sorry, no solution. Just wanted to tell you that you are not alone. I have similar experiences although changing messages (the notorious "no work from project" of course, "no schedulers responded"; the reason for these messages is known and has been mentioned often) but last Friday I had the "master file fetch failed" the whole time. I have shut down boinc for the weekend and hope for better luck on Monday ;-)...

Bye
Peter
</p>Getting no work from Boinc...

> Is it not possible to update the folowing ini files
> 1. account_setiboinc.ssl.berkeley.edu_sah.xml
> 2. sched_request.xml
> 3. client_state.xml
>
> manualy ?
>
It is possible but it is easier to just detach and reattach. There is no need to edit the request file. The account file also has to be renamed, and the project directory has to be renamed.

John Keck
BOINCing since 2002/12/08

> as requested, my stderr log:
> ---------------------------------------------------------------------------
> 2004-07-25 10:37:44 [SETI@home] Deferring communication with project for 1
> weeks, 1 days, 13 hours, 56 minutes, and 54 seconds
> 2004-07-25 10:38:10 [SETI@home] Master file fetch failed

Sorry, I was a little too vague in my request.
stderr.log only contains the error, but we need to see the url which is in the stdout.txt file.

Check that file for:
... Sending request to scheduler ...
and
... Scheduler RPC to ...

The scheduler my systems currently use is: http://setiboincdata.ssl.berkeley.edu

If yours is different, then this is possibly where your problem lies.
If yours is the same, then you could be having a generel network communication problem.

Try going to the projects tab and right click on SETI@home and choose the "update" option. Then post the message results of that action here. Please _don't_ copy your whole stderr and stdout files, since this just wastes bandwidth ;-)