Memcached decompression error Gzip:stdin:not in gzip format tar:child returned status 1 tar:error the workaround for recoverable:exiting now

Recently in the deployment environment, when extracting the memcached during installation,

Decompression command: TAR-ZVXF memcached-1.4.34.tar.gz

Has encountered a problem,

Gzip:stdin:not in gzip format

Tar:child returned status 1

Tar:error isn't recoverable:exiting now

Now I'm going to provide the solution I've summed up:

Method One:

#tar-VXF memcached-1.4.34.tar.gz

When the TAR packet is compressed with the CVF parameter, the decompression time with the XVF parameter
or compression with the CZVF parameter, when extracting with XZVF parameters

When the BZ package is met, replace the z parameter with the corresponding J parameter

Of course, if you and I do not solve your problem in the same way, then look at method two. Look, this baby is so bad not solved.

Method Two:

I found a method on the Internet at this time. is to rename the memcached compressed package, and then unzip.

Command: MV memcached-1.4.34.tar.gz Memcached-1.4.34.tar

Re-extract: Tar-zvxf Memcached-1.4.34.tar

However, it is not used, my file is still an error. This method does not solve my problem. And I feel that this method is actually similar to a OH.

Of course, some people use this method can be, the cause of this problem may be that the installation package was originally Memcached-1.4.34.tar, but later was changed after the prefix name.

Method Three:

I accidentally read an article saying that the installation package that I downloaded online might be corrupted.

How do you know if it is damaged?

Command: LS-LHT view file size

and is compared to the size of the installed packages that are stored on Windows.

Sure enough, there is a problem with the installation package itself.

╥﹏╥ ...

Well, I'll solve the problem here. Of course, if you have a small partner your problem solved and new problems arise, then you can look at method four.

Method Four:

Gzip:stdin:not in gzip format
Tar:child returned status 1
Tar:error exit delayed from previous errors

This is said to be an issue with FTP transmission, which may be transmitted using ASCII transmission. In this case, the binary transfer is changed.

Is your problem solved now?

No, I'll teach you a trick.

Baidu

Haha, I hope to help you.

Resources:

http://www.apoyl.com/?p=419

http://alany.blog.51cto.com/6125308/1422299

Http://www.myexception.cn/ruby-rails/1872329.html

Memcached decompression error Gzip:stdin:not in gzip format tar:child returned status 1 tar:error the workaround for recoverable:exiting now