Error is not recoverable exiting now centos

when I untar doctrine -rw-r--r-- 1 root root 660252 2010-10-16 23:06 Doctrine-1.2.0.tgz I always get this error messages root@X100e:/usr/local/lib/Doctrine/stable# tar -xvzf Doctrine-1.2.0.tgz ...

when I untar doctrine

-rw-r--r-- 1 root root 660252 2010-10-16 23:06 Doctrine-1.2.0.tgz

I always get this error messages

root@X100e:/usr/local/lib/Doctrine/stable# tar -xvzf Doctrine-1.2.0.tgz

.
.
.

Doctrine-1.2.0/tests/ViewTestCase.php
Doctrine-1.2.0/CHANGELOG

gzip: stdin: decompression OK, trailing garbage ignored
Doctrine-1.2.0/COPYRIGHT
Doctrine-1.2.0/LICENSE
tar: Child returned status 2
tar: Error is not recoverable: exiting now

The untar operation works, but I always get this error messages.

Any clues what I do wrong?

Paulo Boaventura's user avatar

asked Oct 16, 2010 at 21:18

udo's user avatar

0

I would try to unzip and untar separately and see what happens:

mv Doctrine-1.2.0.tgz Doctrine-1.2.0.tar.gz
gunzip Doctrine-1.2.0.tar.gz
tar xf Doctrine-1.2.0.tar

answered Oct 16, 2010 at 21:52

Peter G.'s user avatar

Peter G.Peter G.

14.6k7 gold badges55 silver badges75 bronze badges

2

It’s possible your tar file is not zipped. I just had this same error, but all I had was a plain old tar file. So try just removing the z from your flags. The z flag unzips your tar file as well as whatever other commands you requested with other flags. i.e. try:

tar -xvf Doctrine-1.2.0.tgz

Notice I removed the z from -xvzf

answered May 9, 2022 at 22:06

skittlebiz's user avatar

skittlebizskittlebiz

3403 silver badges8 bronze badges

If you got «Error is not recoverable: exiting now» You might have specified incorrect path references.

[me@host ~]$ tar -xvf nameOfMyTar.tar -C /someSubDirectory/
tar: /someSubDirectory: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
[me@host ~]$

Make sure you provide correct relative or absolute directory references e.g.:

[me@host ~]$ tar -xvf ./nameOfMyTar.tar -C ./someSubDirectory/
./foo/
./bar/
[me@host ~]$ 

answered Apr 17, 2018 at 15:58

Axelfoley's user avatar

2

Try to get your archive using wget, I had the same issue when I was downloading archive through browser. Than I just copy archive link and in terminal use the command:

wget http://PATH_TO_ARCHIVE

Vladimir Vagaytsev's user avatar

answered Oct 20, 2016 at 7:55

Aram's user avatar

The problem is that you do not have bzip2 installed. The tar program relies upon this external program to do compression.
For installing bzip2, it depends on the system you are using. For example, with Ubuntu that would be on Ubuntu

sudo apt-get install bzip2

The GNU tar program does not know how to compress an existing file such as user-logs.tar (bzip2 does that). The tar program can use external compression programs gzip, bzip2, xz by opening a pipe to those programs, sending a tar archive via the pipe to the compression utility, which compresses the data which it reads from tar and writes the result to the filename which the tar program specifies.

Alternatively, the tar and compression utility could be the same program. BSD tar does its compression using lib archive (they’re not really distinct except in name).

answered May 15, 2020 at 3:36

Jose Caicedo's user avatar

use sudo

sudo tar -zxvf xxxxxxxxx.tar.gz

answered Sep 12, 2020 at 7:43

Jyothsna Gadde's user avatar

Error messages
enter image description here

Easy way to fix this issue

  1. First Remove files
  2. Download file again
  3. Extract file again ( tar -xzvf(or -xvf) FreeFileSync**.tar.gz

enter image description here

answered Jun 24, 2022 at 1:39

Willie Cheng's user avatar

Willie ChengWillie Cheng

7,33813 gold badges52 silver badges67 bronze badges

Had the same error code:

tar -xvfz processed.json.gz

tar: z: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

Turned out the file had the .gz extension but wasn’t compressed. Just removed the .gz and opened it.

answered Dec 14, 2022 at 14:20

RicarHincapie's user avatar

Are you facing an error which says that gzip: stdin : not in gzip format -tar: error is not recoverable: exiciting now? When you find any error on your PC, including this error, of course you have to fix it so that it can work well again. Now, how about this error? How to solve this error?

Well, when we tried to search about the solution about this error, actually there are a lot of people who discuss about it in forums. Here are the problems and also the solutions that some other people give in the forums that you may try to apply for solving this error.

SOLVE gzip stdin not in gzip format centos 7 - tar error is not recoverable exiting now

A user named ServerSideSkittles in Stack Overflow tells that he has a bash script which creates a tar.gz and encrypts then sends to drive. But, he cannot open the .tar.gz afterwards. In that forum, he shows the process including the scripts. And then, when he tries this:

sudo tar -zxvf red-backup-2016-09-22.tar.gz, he gets this:

gzip: stdin: not in gzip format

tar: Child returned status 1

tar: Error is not recoverable: exiting now

Then, there are some people who try to give him some solutions. Roopendra says that this error happens might be because of his gzip version incompatibity. So, he can check points first: which gzip /usr/bin/gzip or /bin/gzip. It should be either /bin/gzip or /usr/bin/gzip. In case your gzip points to some other gzip application, he suggests to try by removing that path from your PATH env variable. Furthermore, he also suggest to do the next thing which is gzip -V. Gzip 1.3.5 (2002-09-30). He says that his problem is able to be resilve with these check points.

Souvik, another user, also tries to give solution. He says that when this error comes up, it means that the file is not really a gzipped tar file or, any kind of gzipped file, even though being named like one. In addition, he says that when he downloads a file with wget, he has to check for indications like Length: unspecified [text/html] which displays it is plain text and that it is supposed to be interpreted as html. Also, check file, head, less, view utilities to be able to check the file. Then, he also suggests to try downloading from the official site and then check whether the download links have changed. Also, he suggests to check proxy seting and make sure that you have the correct proxies enabled to download/wget it from the right source.

Then, Kamran Kausar, also give his suggestion about this error. He suggests to check the type of compression by using this file command:

 file name_name.tgz

O/P- If output is “XZ compressed data”

And then you have to use tar xf <archive name> to be able to unzip the file, for example:

  • tar xf archive.tar.xz
  • tar xf archive.tar.gz
  • tar xf archive.tar
  • tar xf archive.tgz

In the It’s Foss site, there is also a story about this error. Someone has a problem where when he tries to unzip a file MyFile.tar.gz which looks like a gzipped file by the name. However, while he is unzipping, he finds an error ‘gzip stdin not in gzip format’. The error means that the file is not in gZipped format. So, which format is it in? To be able to find out, you are able to run the file command on it:

file MyFile.tar.gz

MyFile.tar.gz: POSIX tar archive (GNU)

The reason of this error is quite evident. The file is not a gzipped file but it is a POSIX tar archive file. It means that it was not zipped at all but instead it was compressed using tar. It was simply renamed afterwards. The creator of the file may want to gzip a directory. However, he could not do that since the directory must be archived by using tar first. So, the solution is because it was not a gzipped file, a simple tar can extract the file:

tar xvf MyFile.tar.gz

So, you are able to run the file command on your file and see what kind of archive file it is. In case you see that your file too is in POSIX tar archive format, you are able to use the similar command that he used in the example above. However, in case it is in some other archive format, you are able to run the suitable command to extract the archive file.

In the Askubuntu, there is also a discussion about it. He says that when he runs this: tar -zxvf john-1.7.0.2.tar.gz and then he get this:

gzip: stdin: not in gzip format

tar: Child returned status 1

tar: Error is not recoverable: exiting now

Another user named Eliah Kagan, gives the suggestion to solve this problem as you can see below.

  • You have to diagnose a Downloading File of the Wrong Type. It means that the file is not really a gzipped tar file. You are able to use the file utility which examines a file and tells you what kind of file it looks to be.
  • You have to get the right file. It tells you how to find what went wrong in these conditions. You may wonder how to find and download the correct file. It varies from situation to situation. However, you are able to do the things below for a good start.

– First, you have to access the official site for the software and then see whether they provide download links. Even if you do it before, however, you need to know that if some time has passsed, you may find that the link has changed.

– Then, you have to go to the page that you were redirected to when you downloaded the file. In this case, that is www.openwall.com/john/. Or, you are able to examine the file that was downloaded or you are able to open it in a web browser.

    • Note that you do not always need to build from source. Sometimes, you want the recent version of a program and it is not in Ubuntu’s repositories. You may try to find a PPS, but if you do not find any you really trust or you want to build it with custom options, or you really like building from source code, then building from source code is valuable and useful technique. So, it is recommended to check at least the software that is available in Ubuntu’s offficial repositories for your system.

Alfin Dani

AUTHOR BIO

On my daily job, I am a software engineer, programmer & computer technician. My passion is assembling PC hardware, studying Operating System and all things related to computers technology. I also love to make short films for YouTube as a producer. More at about me…

I was attempting to untar a .tar.gz file, but came across this error:

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

The tar.gz file includes a .tar file, which when untarred results in:

tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

I tried both –ignore-zeros and –ignore-failed-read, although they both didn’t work.

Is there any way I could extract this file even if it is corrupted?

The file type in question: .tar.gz: Gzip Compressed Data, from a UNIX system.

asked Nov 5, 2012 at 11:54

iLinux85's user avatar

Check two items:

(1) Is the FILE INCOMPLETE due to a faulty download? Re-download, and use the -c option if your are using wget. (happens all the time).

(2) Does the .tar or .tar.gz filename have ILLEGAL CHARACTERS. It’s best to keep archive names simple, short, composed of letters and numbers. (happens all the time). So just rename the file. This one nailed me recently as I thought it would be convenient to include a time/date stamp as part of the archive name. BAD IDEA!

jasonwryan's user avatar

jasonwryan

70.1k33 gold badges191 silver badges224 bronze badges

answered Aug 9, 2015 at 4:20

SANDPOND's user avatar

SANDPONDSANDPOND

1411 silver badge3 bronze badges

1

You don’t. It appears the file has been truncated. How long is it? If you only have the first few bytes then you’re done.

answered Nov 5, 2012 at 13:55

psusi's user avatar

psusipsusi

16.8k3 gold badges37 silver badges47 bronze badges

are you unpacking the .tar.gz file on the same platform it was made on? there are some differences between older Unix versions of tar, such as the non-GNU versions of tar that have shipped with Solaris, and the GNU tar that ships with Linux, etc. If you’re going to unpack an archive with GNU tar, it’s best to create it with GNU tar.

how does your system look for disk space? was the disk full when you made the archive, or is it full as you attempt to unpack it?

did you create the archive with a cron job? without output redirection, cron can do funky things to archives due to limitations in the size of output it will allow to STDOUT. If you’re making an archive in cron, and you’re using -v with tar, try redirecting STDOUT to a file, and STDERR, too. See if that helps. tar -cvf archive.tar.gz /path/ 1>archive.stdout.log 2>archive.stderr.log or something like that.

answered Nov 5, 2012 at 14:24

Tim Kennedy's user avatar

Tim KennedyTim Kennedy

19k4 gold badges37 silver badges57 bronze badges

2

I had the same error.

My problem was trying to use tar to unzip before the upload was complete.

AdminBee's user avatar

AdminBee

20.8k18 gold badges47 silver badges69 bronze badges

answered Nov 30, 2022 at 20:40

Okomikeruko's user avatar

just faced this recently, solution was to rename the file (remove the _).E.g Bad file name which was causing issue MAA07-0100-0100-01AAA_show_tech_output.tgz , renaming this to MAA07-0100-0100-01AAA.tgz helped to resolve the issue.

answered Nov 23, 2018 at 9:48

fsociety's user avatar

My solution to the problem was to rename the tar archive twice. I know it does sound ridiculous, but it worked for me and saved a lot of time on rearchiving.

I had a big, 9 GB, tar gzip archive named ‘STRING152_20200221.tar.gz’ which produced the errors reported by the OP.
As advised above, I renamed it to just ‘STRING.tar.gz’. The errors persisted.
Then I renamed it back to the original name ‘STRING152_20200221.tar.gz’ and it unarchived successfully.

No manipulations with the archive except its name were done.

My tar version is ‘tar (GNU tar) 1.26’. I am also on CentOs (CentOS Linux release 7.4.1708 (Core))

answered Feb 25, 2020 at 9:39

user3804598's user avatar

Per How do I uncompress a tarball that uses .xz?, I tried tar xf php-5.6.0RC4.tar.xz and tar -xJf php-5.6.0RC4.tar.xz and in both cases I get the following:

tar (child): xz: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

It’s this php-5.6.0RC4.tar.xz.

I’m running Ubuntu 14.04 LTS.

What’s wrong?

Community's user avatar

asked Aug 21, 2014 at 16:19

neubert's user avatar

The line

tar (child): xz: Cannot exec: No such file or directory

gives you the real error. The xz programm cannot be executed, probably because it is not installed. To install the xz (de)compression tools, issue one of the following commands depending on your distibution:

sudo apt-get install xz-utils          # Debian / Ubuntu
sudo yum install xz                    # RHEL / CentOS
sudo zypper in xz                      # OpenSuSE
sudo pacman -S xz                      # Arch Linux

answered Aug 21, 2014 at 17:19

mpy's user avatar

mpympy

26.3k7 gold badges82 silver badges94 bronze badges

4

ali10086

Posts: 4
Joined: Fri Jul 16, 2021 12:24 pm

Os: Ubuntu 17x
Web: apache + nginx
tar: Error is not recoverable: exiting now

I need urgent help from your side. I have a VPS on AWS cloud having Vesta Cpanel install on Ubuntu 18 on it. I want to move my all vesta cpanel data into my locally installed vesta cpanel. So to archive this I give the below command

sudo /usr/local/vesta/bin/v-backup-user admin
the backup process is started but at the end of the backup its give me an error the
tar: Error is not recoverable: exiting now
and there is no disk spaces issue on my server.
could you please help me out on how to resolve this issue so that I can take backup successfully without any error?
Thanks in advance


ali10086

Posts: 4
Joined: Fri Jul 16, 2021 12:24 pm

Os: Ubuntu 17x
Web: apache + nginx
Re: tar: Error is not recoverable: exiting now

Post

by ali10086 » Sat Jul 17, 2021 5:30 am

anyone? please help me


grayfolk

Support team
Posts: 1111
Joined: Tue Jul 30, 2013 10:18 pm
Contact:

Os: CentOS 6x
Web: nginx + php-fpm
Re: tar: Error is not recoverable: exiting now

Post

by grayfolk » Sat Jul 17, 2021 6:06 am

ali10086 wrote: ↑

Sat Jul 17, 2021 5:30 am


anyone? please help me

Check if /backup/admin.log file exists.


ali10086

Posts: 4
Joined: Fri Jul 16, 2021 12:24 pm

Os: Ubuntu 17x
Web: apache + nginx
Re: tar: Error is not recoverable: exiting now

Post

by ali10086 » Sat Jul 17, 2021 11:30 am

Sir, there is not admin.log file exsit.

after the above error «Error is not recoverable: exiting now» system made a tar file which size is 22GB when i restore this tar file system given me error this tar is currpted,

i have attached the image for your reference.

https://drive.google.com/file/d/1zXSBBE … sp=sharing

grayfolk wrote: ↑

Sat Jul 17, 2021 6:06 am

ali10086 wrote: ↑

Sat Jul 17, 2021 5:30 am


anyone? please help me

Check if /backup/admin.log file exists.


ali10086

Posts: 4
Joined: Fri Jul 16, 2021 12:24 pm

Os: Ubuntu 17x
Web: apache + nginx
Re: tar: Error is not recoverable: exiting now

Post

by ali10086 » Sat Jul 17, 2021 4:38 pm

Very forum and very nice support.

fuck that find of forum. dirty community.

ali10086 wrote: ↑

Sat Jul 17, 2021 11:30 am


Sir, there is not admin.log file exsit.

after the above error «Error is not recoverable: exiting now» system made a tar file which size is 22GB when i restore this tar file system given me error this tar is currpted,

i have attached the image for your reference.

https://drive.google.com/file/d/1zXSBBE … sp=sharing

grayfolk wrote: ↑

Sat Jul 17, 2021 6:06 am

ali10086 wrote: ↑

Sat Jul 17, 2021 5:30 am


anyone? please help me

Check if /backup/admin.log file exists.



Команда sudo wget http://eclipse.org/downloads/download.php?file=/jetty/stable-9/dist/jetty-distribution-9.1.0.v20131115.tar.gz&r=1 неверна по двум причинам:

  1. Ссылка на скачивание должна быть указана, так как вы используете &, который является особенным в Bash. См. Http://www.gnu.org/software/bash/manual/bash.html#Definitions.
  2. Вы используете старую мертвую ссылку. Переход на страницу загрузки Jetty ( http://download.eclipse.org/jetty/ ) показывает http://eclipse.org/downloads/download.php?file=/jetty/stable-9/dist/jetty-distribution-9.1.3.v20140225.tar.gz&r=1 как правильная ссылка для скачивания.

Затем вы должны использовать следующую команду:

sudo wget "http://eclipse.org/downloads/download.php?file=/jetty/stable-9/dist/jetty-distribution-9.1.3.v20140225.tar.gz&r=1" -O jetty-distribution-9.1.3.v20140225.tar.gz`

Аргумент -O помогает в выводе на правильное имя файла.

После этого tar xvf jetty-distribution-9.1.3.v20140225.tar.gz должен работать.

Здесь опция x использует режим извлечения, v показывает дополнительную информацию (имя извлекаемого файла), а f указывает, что следующий аргумент — это путь к архиву, который нужно извлечь.

Вам не нужна опция z которая указывает сжатый архив gzip так как tar распознает его автоматически.

Наконец, - предыдущие варианты устарели AFAIK.

Другое дело: я не рекомендую использовать sudo когда это действительно не нужно. Здесь вы просто хотите скачать и распаковать архив, который не нуждается в привилегиях суперпользователя, и вы можете сделать это в своем домашнем каталоге. Это позволяет избежать ошибок, которые могут привести к серьезным проблемам, особенно когда вы действительно не знаете, что делаете.

Понравилась статья? Поделить с друзьями:
  • Error is not a class template
  • Error is mater ignorantia est
  • Error is logged with tag перевод
  • Error ipv4 fib table does not exist
  • Error ipc connection error connection refused