Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionPresian Yankulov
2016-02-12 10:53:34 UTC
Description of problem:
Older server always do the decompression.
In newer version (3.3.x), server compression is decompressed on the
server and client compression is decompressed on the client.
This bug is fixed in 3.3.6
Version-Release number of selected component (if applicable):
Server:
CentOS release 6.7 (Final)
amanda-2.6.1p2-9.el6_6.x86_64
amanda-client-2.6.1p2-9.el6_6.x86_64
amanda-server-2.6.1p2-9.el6_6.x86_64
Client:
CentOS Linux release 7.2.1511 (Core)
amanda-libs-3.3.3-13.el7.x86_64
amanda-client-3.3.3-13.el7.x86_64
amanda-3.3.3-13.el7.x86_64
How reproducible:
Connect to the Server from the Client with amrecover and add file to extract:
Added file /adduser.conf
amrecover> extract
[...]
Restoring files into directory /tmp/tmp.JwS8LFGzAS
All existing files in /tmp/tmp.JwS8LFGzAS can be deleted
Continue [?/Y/n]? y
tar: This does not look like a tar archive
tar: ./adduser.conf: Not found in archive
[...]
tar: ./xml: Not found in archive
tar: Exiting with failure status due to previous errors
Steps to Reproduce:
1.
2.
3.
Actual results:
And amrecover hangs, but can be interrupted with CTRL-C.
Expected results:
amrecover should proceed as normal and extract the archive to the client side.
Additional info:
same bug is reported:
http://archives.zmanda.com/amanda-archives/viewtopic.php?t=7322&sid=31bf5a8d21db35ad0e4fffeb511403d9https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687312.
Older server always do the decompression.
In newer version (3.3.x), server compression is decompressed on the
server and client compression is decompressed on the client.
This bug is fixed in 3.3.6
Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. Please keep in mind for future, that this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.
If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit:
https://www.redhat.com/support/process/production/#howto
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0674