Trouble with new BOINC Client boinc_4.05_i686-pc-linux-gnu

Questions and Answers : Unix/Linux : Trouble with new BOINC Client boinc_4.05_i686-pc-linux-gnu
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Jean-David Beyer

Send message
Joined: 10 Jun 99
Posts: 60
Credit: 1,301,105
RAC: 1
United States
Message 19631 - Posted: 30 Aug 2004, 1:40:36 UTC

I just downloaded and installed this. I also ran the old BOINC client with -reset_project URL to clear out the old setiathome stuff. Then I started the new BOINC clients. It does a lot of stuff, but it complains a lot like this:

Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: 2004-08-29 21:30:30 [SETI@home] Giving up on download of 25ap04aa.23553.13121.536080.198: File downloaded was not the correct file or was garbage from bad URL
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: 2004-08-29 21:30:30 [SETI@home] Giving up on download of 25ap04aa.23553.13121.536080.198: File downloaded was not the correct file or was garbage from bad URL
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: md5_file: can't open projects/setiathome.berkeley.edu/25ap04aa.23553.13121.536080.198
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: md5_file: No such file or directory
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: 2004-08-29 21:30:30 [SETI@home] verify_downloaded_file(): projects/setiathome.berkeley.edu/25ap04aa.23553.13121.536080.198: MD5 computation failed: -108
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: 2004-08-29 21:30:30 [SETI@home] Checksum or signature error for 25ap04aa.23553.13121.536080.198
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: 2004-08-29 21:30:30 [SETI@home] Unrecoverable error for result 25ap04aa.23553.13121.536080.198_5 (file transfer error: couldn't get input files:
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: 25ap04aa.23553.13121.536080.198: File downloaded was not the correct file or was garbage from bad URL
Aug 29 21:30:30 trillian boinc_4.05_i686-pc-linux-gnu: )

It has downloaded some files, apparently successfully:
]$ ls -lrt
total 8032
-rw------- 1 boinc root 361963 Aug 29 20:59 04my04aa.2277.15137.903384.226
-rw------- 1 boinc root 361963 Aug 29 21:01 04my04aa.2277.15137.903384.230
-rw------- 1 boinc root 361963 Aug 29 21:03 04my04aa.2277.15137.903384.234
-rw------- 1 boinc root 361814 Aug 29 21:10 04my04aa.2277.11168.197168.135
-rw------- 1 boinc root 372365 Aug 29 21:12 25ap04aa.23553.20145.959660.141
-rw------- 1 boinc root 372361 Aug 29 21:14 25ap04aa.23553.20145.959660.176
-rw------- 1 boinc root 372364 Aug 29 21:16 25ap04aa.23553.20145.959660.158
-rw-r--r-- 1 boinc root 5304320 Aug 29 21:17 setiathome_4.02_i686-pc-linux-gnu
-rw-r--r-- 1 boinc root 299008 Aug 29 21:17 25ap04aa.23553.20145.959660.140

I hope this helps.

ID: 19631 · Report as offensive
Profile Christian Patterson

Send message
Joined: 28 May 00
Posts: 4
Credit: 2,270,322
RAC: 0
United States
Message 24109 - Posted: 9 Sep 2004, 14:54:49 UTC

I had a very similar problem, it was do to me having a to restrictive umask. I reset my umask to 720 and I was able to detach and reattach fine. Every thing works great now.


Christian Patterson
Unix/Linux Geek




The Ursine Jester
ID: 24109 · Report as offensive
Profile Jean-David Beyer

Send message
Joined: 10 Jun 99
Posts: 60
Credit: 1,301,105
RAC: 1
United States
Message 25080 - Posted: 11 Sep 2004, 12:45:05 UTC - in response to Message 24109.  

> I had a very similar problem, it was do to me having a to restrictive umask. I
> reset my umask to 720 and I was able to detach and reattach fine. Every thing
> works great now.
>
My umask is 0027 for normal users (including boinc).
Yours seems to be backwards:

umask [-p] [-S] [mode]
The user file-creation mask is set to mode. If mode begins with
a digit, it is interpreted as an octal number; otherwise it is
interpreted as a symbolic mode mask similar to that accepted by
chmod(1). If mode is omitted, the current value of the mask is
printed. The -S option causes the mask to be printed in sym-
bolic form; the default output is an octal number. If the -p
option is supplied, and mode is omitted, the output is in a form
that may be reused as input. The return status is 0 if the mode
was successfully changed or if no mode argument was supplied,
and false otherwise.

In any case, I changed nothing and setiathome is now working, but predictor and climateprediction do not work (for different reasons. Predictor wants the old 3.20 BOINC client and I am running 4.05. Climateprediction likes 4.05, but the programs just do not work.
ID: 25080 · Report as offensive
Profile Christian Patterson

Send message
Joined: 28 May 00
Posts: 4
Credit: 2,270,322
RAC: 0
United States
Message 25896 - Posted: 13 Sep 2004, 13:51:49 UTC - in response to Message 25080.  

Indeed it is, must have had a dyslexic morning. Thank you for clearing it up for me.


Christian


> > I had a very similar problem, it was do to me having a to restrictive
> umask. I
> > reset my umask to 720 and I was able to detach and reattach fine. Every
> thing
> > works great now.
> >
> My umask is 0027 for normal users (including boinc).
> Yours seems to be backwards:
>
> umask [-p] [-S] [mode]
> The user file-creation mask is set to mode. If mode begins
> with
> a digit, it is interpreted as an octal number; otherwise it
> is
> interpreted as a symbolic mode mask similar to that accepted
> by
> chmod(1). If mode is omitted, the current value of the mask
> is
> printed. The -S option causes the mask to be printed in
> sym-
> bolic form; the default output is an octal number. If the
> -p
> option is supplied, and mode is omitted, the output is in a
> form
> that may be reused as input. The return status is 0 if the
> mode
> was successfully changed or if no mode argument was
> supplied,
> and false otherwise.
>
> In any case, I changed nothing and setiathome is now working, but predictor
> and climateprediction do not work (for different reasons. Predictor wants the
> old 3.20 BOINC client and I am running 4.05. Climateprediction likes 4.05, but
> the programs just do not work.
>
>
Christian Patterson
Unix/Linux Geek




The Ursine Jester
ID: 25896 · Report as offensive

Questions and Answers : Unix/Linux : Trouble with new BOINC Client boinc_4.05_i686-pc-linux-gnu


 
©2026 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.