Linux Installation Problem

Message boards : BOINC client : Linux Installation Problem
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9485 - Posted: 10 Apr 2007, 13:04:43 UTC

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?
ID: 9485 · Report as offensive
Metod, S56RKO

Send message
Joined: 9 Sep 05
Posts: 128
Slovenia
Message 9486 - Posted: 10 Apr 2007, 13:07:43 UTC - in response to Message 9485.  

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?


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 ...
ID: 9486 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9487 - Posted: 10 Apr 2007, 13:31:05 UTC - in response to Message 9486.  

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?


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.



Thank you for a quick reply. You know how to get through a proxy using the cmd prompt?

ID: 9487 · Report as offensive
Nicolas

Send message
Joined: 19 Jan 07
Posts: 1179
Argentina
Message 9489 - Posted: 10 Apr 2007, 16:04:16 UTC

man wget

:)
ID: 9489 · Report as offensive
Metod, S56RKO

Send message
Joined: 9 Sep 05
Posts: 128
Slovenia
Message 9490 - Posted: 10 Apr 2007, 19:14:51 UTC - in response to Message 9487.  
Last modified: 10 Apr 2007, 19:15:10 UTC

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.


Thank you for a quick reply. You know how to get through a proxy using the cmd prompt?


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 ...
ID: 9490 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9491 - Posted: 10 Apr 2007, 20:32:13 UTC - in response to Message 9487.  

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?


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.




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!

ID: 9491 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9504 - Posted: 11 Apr 2007, 12:39:07 UTC

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?
ID: 9504 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5082
United Kingdom
Message 9514 - Posted: 11 Apr 2007, 16:20:26 UTC

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?
ID: 9514 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9522 - Posted: 11 Apr 2007, 17:46:13 UTC - in response to Message 9514.  

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?


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??
ID: 9522 · Report as offensive
Nicolas

Send message
Joined: 19 Jan 07
Posts: 1179
Argentina
Message 9524 - Posted: 11 Apr 2007, 19:48:47 UTC
Last modified: 11 Apr 2007, 19:49:02 UTC

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.
ID: 9524 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9527 - Posted: 11 Apr 2007, 21:17:34 UTC - in response to Message 9524.  

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.


e11a2c61520edb09af3ab9f9e52c8093 --- Yep it has downloaded correctly.

*sigh*

Is there a place I can download the tar file ??
ID: 9527 · Report as offensive
Nicolas

Send message
Joined: 19 Jan 07
Posts: 1179
Argentina
Message 9528 - Posted: 11 Apr 2007, 21:22:52 UTC

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
ID: 9528 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9530 - Posted: 11 Apr 2007, 21:27:25 UTC - in response to Message 9528.  
Last modified: 11 Apr 2007, 21:28:26 UTC

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


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.
ID: 9530 · Report as offensive
Nicolas

Send message
Joined: 19 Jan 07
Posts: 1179
Argentina
Message 9534 - Posted: 12 Apr 2007, 0:02:12 UTC

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"?
ID: 9534 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9540 - Posted: 12 Apr 2007, 12:47:10 UTC - in response to Message 9534.  

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"?


Yep. :(

I got the same error.

gunzip: stdin: not in gzip format
Tar: blocksize = 0; broken pipe?

Please don't give up!
ID: 9540 · Report as offensive
clownius

Send message
Joined: 17 Feb 07
Posts: 35
Australia
Message 9555 - Posted: 13 Apr 2007, 6:24:12 UTC

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.
ID: 9555 · Report as offensive
Metod, S56RKO

Send message
Joined: 9 Sep 05
Posts: 128
Slovenia
Message 9556 - Posted: 13 Apr 2007, 7:39:34 UTC - in response to Message 9540.  

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 ...
ID: 9556 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9558 - Posted: 13 Apr 2007, 16:07:12 UTC - in response to Message 9556.  
Last modified: 13 Apr 2007, 16:09:27 UTC

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.


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




ID: 9558 · Report as offensive
Nicolas

Send message
Joined: 19 Jan 07
Posts: 1179
Argentina
Message 9564 - Posted: 13 Apr 2007, 18:09:23 UTC - in response to Message 9558.  

YEP!!! now I tried

gunzip | tar xf foo.tar.gz

Correct syntax for that is:

gunzip foo.tar.gz | tar xf -
ID: 9564 · Report as offensive
Nunu

Send message
Joined: 10 Apr 07
Posts: 38
Message 9566 - Posted: 13 Apr 2007, 18:44:08 UTC - in response to Message 9564.  

YEP!!! now I tried

gunzip | tar xf foo.tar.gz

Correct syntax for that is:

gunzip foo.tar.gz | tar xf -


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??

ID: 9566 · Report as offensive
1 · 2 · Next

Message boards : BOINC client : Linux Installation Problem

Copyright © 2024 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.