Message boards : BOINC client : Linux Installation Problem
Message board moderation
Author | Message |
---|---|
Send message Joined: 10 Apr 07 Posts: 38 |
I have downloaded boinc_5.8.15_i686-pc-linux-gnu.sh onto my linux server. When I try installing it by typing: sh boinc_5.8.15_i686-pc-linux-gnu.sh I get the error message: gunzip: stdin: not in gzip format Tar: blocksize = 0; broken pipe? Any suggestions? |
Send message Joined: 9 Sep 05 Posts: 128 |
I have downloaded boinc_5.8.15_i686-pc-linux-gnu.sh onto my linux server. When I try installing it by typing: Your browser probably downloaded file as ASCII instead of BINARY. I guess that running wget http://boinc.berkeley.edu/dl/boinc_5.8.17_i686-pc-linux-gnu.sh from linux command prompt should do it properly. Metod ... |
Send message Joined: 10 Apr 07 Posts: 38 |
I have downloaded boinc_5.8.15_i686-pc-linux-gnu.sh onto my linux server. When I try installing it by typing: Thank you for a quick reply. You know how to get through a proxy using the cmd prompt? |
Send message Joined: 19 Jan 07 Posts: 1179 |
man wget :) |
Send message Joined: 9 Sep 05 Posts: 128 |
Your browser probably downloaded file as ASCII instead of BINARY. I guess that running Your question is answered on this web page: http://wiki.archlinux.org/index.php/How_to_make_wget_to_work_with_proxy_and_proxy_authentification. Metod ... |
Send message Joined: 10 Apr 07 Posts: 38 |
I have downloaded boinc_5.8.15_i686-pc-linux-gnu.sh onto my linux server. When I try installing it by typing: Okay, downloaded it this way, and confirmed the file is there. Still having the same error: gunzip: stdin: not in gzip format Tar: blocksize = 0; broken pipe? Any other suggestions? You guys are really awsome with all the help! Thx! |
Send message Joined: 10 Apr 07 Posts: 38 |
Still having the same problem, file downloaded in binary, but still won't run: gunzip: stdin: not in gzip format Tar: blocksize = 0; broken pipe? Any suggestions? |
Send message Joined: 5 Oct 06 Posts: 5139 |
It's beginning to sound as if you need to do some detective work, to find out whether it's a corrupt download or a broken (un)zipper. Do you have any chance of downloading the package on another machine - preferably using a different ISP - and transferring via CD or memory stick? That would help to track down whether it's getting mangled in transit. And for the other half of the test, have you tried to install any gzipped packages from other sources recently, to test that all your local tools are working properly? |
Send message Joined: 10 Apr 07 Posts: 38 |
It's beginning to sound as if you need to do some detective work, to find out whether it's a corrupt download or a broken (un)zipper. Yeah, I have tried to download the file to another machine, and transfered it to the current machine. I also have been installing other software via the same fashion. However, I also tried tar on spereate packages that were just tar'ed and it worked. I think there is some reason why tar isn't working before it's piped to zip... At least that is what I think is trying to happen?? |
Send message Joined: 19 Jan 07 Posts: 1179 |
Do this after downloading: md5sum <filename> The output should match the one below. I don't know if you downloaded 5.8.15 or 5.8.17, so I'll give the output for both: 2b02e40d741ee1cc6732c2832439935f *boinc_5.8.15_i686-pc-linux-gnu.sh e11a2c61520edb09af3ab9f9e52c8093 *boinc_5.8.17_i686-pc-linux-gnu.sh If it doesn't match, means the download was corrupted. |
Send message Joined: 10 Apr 07 Posts: 38 |
Do this after downloading: e11a2c61520edb09af3ab9f9e52c8093 --- Yep it has downloaded correctly. *sigh* Is there a place I can download the tar file ?? |
Send message Joined: 19 Jan 07 Posts: 1179 |
Try this, instead of using sh: chmod u+x boinc_5.8.17_i686-pc-linux-gnu.sh ./boinc_5.8.17_i686-pc-linux-gnu.sh |
Send message Joined: 10 Apr 07 Posts: 38 |
Try this, instead of using sh: I originally tried chmod +x, but I undid that, and just tried with the u flag. Still no luck. What are the individual files inside the pack? It's been a long time since I used Linux... it's slowly coming back. :) I appreciate your help man. |
Send message Joined: 19 Jan 07 Posts: 1179 |
u+x means add eXecute privileges to the User. Did you try "./boinc_5.8.17_i686-pc-linux-gnu.sh" (after giving execute permissions) instead of "sh boinc_5.8.17_i686-pc-linux-gnu.sh"? |
Send message Joined: 10 Apr 07 Posts: 38 |
u+x means add eXecute privileges to the User. Yep. :( I got the same error. gunzip: stdin: not in gzip format Tar: blocksize = 0; broken pipe? Please don't give up! |
Send message Joined: 17 Feb 07 Posts: 35 |
What distro are you using there may be other options if its debian based. If not i have no idea what next unless someone unpackages it and mails it to you or something. |
Send message Joined: 9 Sep 05 Posts: 128 |
Please don't give up! If you execute the following: ( read l; read l; read l; exec cat ) < boinc_5.8.17_i686-pc-linux-gnu.sh > foo.tar.gz do you get a valid gzipped tar file? file should be something like this: $ file foo.tar.gz foo.tar.gz: gzip compressed data, from Unix, last modified: Thu Mar 8 03:29:46 2007 The date part will be different in your case of course. Metod ... |
Send message Joined: 10 Apr 07 Posts: 38 |
Please don't give up! YEP!!! now I tried gunzip | tar xf foo.tar.gz buy got the error: directoy checksum error gunzip: compressed data not read from a terminal. Use -f to force decompression. I also tried: gunzip -fd foo.tar.gz and got the error: gunzip: foo.tar.gz: not in gzip format |
Send message Joined: 19 Jan 07 Posts: 1179 |
YEP!!! now I tried Correct syntax for that is: gunzip foo.tar.gz | tar xf - |
Send message Joined: 10 Apr 07 Posts: 38 |
YEP!!! now I tried That provides the same error as before: gunzip: foo.tar.gz: not in gzip format Tar: blocksize = 0; broken pipe? So it's clear there seems to be a problem with the zip file, as it's not unzipping correctly. Any suggestions? I also tried re-downloading the file and starting fresh to make the foo.tar.gz file, and still get stuck with the gunzip. Okay, what next?? |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.