amrecover fails due to warnings in amidxtaped

Bug #1156858 reported by Heiko Schlittermann on 2013-03-18
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
amanda (Ubuntu)
Undecided
Unassigned

Bug Description

The amrecover can't successfully talk to the amidxtaped.

amidxtaped creates some warnings. These warnings seem to be translated into ERRORS. For testing purposes I fixed the places pointed to by the warnings. After applying these changes, amrecover works as expected.

I'd say this is critical. Because if somebody w/o knowledge of perl has to recover somethind, he/she would be lost. And w/o access to the server where the amidxtaped runs even Perl knowledge would not help!

Best regards from Dresden,
--
Heiko Schlittermann

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: amanda-server 1:3.3.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Mon Mar 18 22:21:11 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MarkForUpload: True
SourcePackage: amanda
UpgradeStatus: No upgrade log present (probably fresh install)

Heiko Schlittermann (hs12) wrote :
description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in amanda (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers