Your message dated Thu, 29 Dec 2005 00:00:53 -0700
with message-id <[EMAIL PROTECTED]>
and subject line no longer a problem
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Jul 2001 11:34:06 +0000
>From [EMAIL PROTECTED] Thu Jul 26 06:34:06 2001
Return-path: <[EMAIL PROTECTED]>
Received: from relay.uni-heidelberg.de [::ffff:129.206.100.212] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 15PjOy-0003Cz-00; Thu, 26 Jul 2001 06:34:01 -0500
Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de 
[129.206.119.234])
        by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id 
f6QBXpB07427
        for <[EMAIL PROTECTED]>; Thu, 26 Jul 2001 13:33:51 +0200 (MET DST)
Received: from extmail.urz.uni-heidelberg.de (extmail.urz.uni-heidelberg.de 
[129.206.100.140])
        by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with SMTP id NAA32446
        for <[EMAIL PROTECTED]>; Thu, 26 Jul 2001 13:33:46 +0200
Received: (qmail 8830 invoked by uid 0); 26 Jul 2001 11:30:42 -0000
Received: from unknown (HELO wichtel.suspekt) (unknown)
  by unknown with SMTP; 26 Jul 2001 11:30:42 -0000
Received: from escher.suspekt ([192.168.1.2])
        by wichtel.suspekt with esmtp (Exim 3.22 #1 (Debian))
        id 15PjOf-0005Oz-00; Thu, 26 Jul 2001 13:33:41 +0200
Received: from thimo by escher.suspekt with local (Exim 3.22 #1 (Debian))
        id 15PjOe-0004MR-00; Thu, 26 Jul 2001 13:33:40 +0200
From: Thimo Neubauer <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Cannot get index with amrecover
X-Reportbug-Version: 1.21
X-Mailer: reportbug 1.21
Date: Thu, 26 Jul 2001 13:33:40 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: Thimo Neubauer <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]

Package: amanda-server
Version: 1:2.4.2-6
Severity: normal

Ok, that is about the most frequently bug (?) with Amanda and I did
check the different mail-archives first (my tar is tar (GNU tar)
1.13.19) ;-) Unfortunately, nothing in those mails helped me fixing my
problem...

First of all: I'm using the gtar-method to backup files, so there has
to be an index. It is correctly created:

escher escher/_home# l
insgesamt 120
-rw-------    1 backup   backup      90570 14. Jul 19:52 20010714_0.gz
-rw-------    1 backup   backup      23996 16. Jul 10:56 20010716_1.gz
escher escher/_home# pwd
/var/lib/amanda/DailySet1/index/escher/_home
escher escher/_home# 

Now if I start amrecover I get:

escher /home/thimo# amrecover
AMRECOVER Version 2.4.2. Contacting server on localhost ...
220 escher AMANDA index server (2.4.2) ready.
200 Access OK
Setting restore date to today (2001-07-26)
200 Working date set to 2001-07-26.
200 Config set to DailySet1.
200 Dump host set to escher.
Can't determine disk and mount point from $CWD
amrecover> setdisk /home
Warning: no log files found for tape WG04 written 2001-07-24
Warning: no log files found for tape WG03 written 2001-07-24
Warning: no log files found for tape WG02 written 2001-07-16
Warning: no log files found for tape WG01 written 2001-07-14
Scanning /data/backup...
200 Disk set to /home.
No index records for disk for specified date
If date correct, notify system administrator
amrecover> 
 
and (to provide the complete picture) /tmp/amanda/amindexd.debug says:

amindexd: debug 1 pid 16718 ruid 34 euid 34 start time Thu Jul 26 13:24:47 2001
amindexd: version 2.4.2
< 220 escher AMANDA index server (2.4.2) ready.
> SECURITY USER root
bsd security: remote host escher.suspekt user root local user backup
amandahosts security check passed
< 200 Access OK
> DATE 2001-07-26
< 200 Working date set to 2001-07-26.
> SCNF DailySet1
< 200 Config set to DailySet1.
> HOST escher
< 200 Dump host set to escher.
> DISK /
< 501 No index records for disk: /. Invalid?
> DISK sda5
< 501 No index records for disk: sda5. Invalid?
> DISK /home
< 200 Disk set to /home.
> OISD /
< 500 No dumps available on or before date "2001-07-26"
> OISD /
< 500 No dumps available on or before date "2001-07-26"

The index-file seems to be perfect as well:

escher escher/_home# zcat 20010716_1.gz | head
/
/johanna/
/johanna/.mozilla/
/johanna/.mozilla/chrome/
/johanna/.mozilla/chrome/locales/
/johanna/.mozilla/chrome/locales/en-DE/
/johanna/.mozilla/chrome/locales/en-US/
/johanna/.mozilla/chrome/locales/en-US/communicator/
/johanna/.mozilla/chrome/locales/en-US/communicator/locale/
/johanna/.mozilla/chrome/locales/en-US/communicator/locale/bookmarks/
escher escher/_home# 

This is my disklist-file:

# escher sichert sich selber
escher /etc high-tar
escher /home comp-user-tar
escher /usr/local comp-root-tar

wichtel /etc high-tar
wichtel /home comp-user-tar
wichtel /usr/local comp-root-tar
# exclude.gtar auf wichtel sollte /var/cache/* verhindern
wichtel /var comp-root-tar

bach /etc high-tar
bach /home comp-user-tar
bach /usr/local comp-root-tar

pong /etc high-tar
pong /home comp-user-tar

I'm using the CD-RW-stuff I got from
http://www.tivano.de/amanda/amanda.html but that shouldn't be the
reason, because this is just a drop-in-replacement for the taper which
should not deal with the index-creation.

What the heck am I doing wrong? Or is this really a bug?

CU
    Thimo

-- System Information
Debian Release: testing/unstable
Architecture: alpha
Kernel: Linux escher 2.2.19 #1 Sun Jun 10 06:04:03 UTC 2001 alpha
Locale: LANG=de_DE, LC_CTYPE=de_DE

Versions of packages amanda-server depends on:
ii  amanda-common             1:2.4.2-6      Advanced Maryland Automatic Networ
ii  libc6.1                   2.2.3-5        GNU C Library: Shared libraries an
ii  libncurses5               5.2.20010318-2 Shared libraries for terminal hand
ii  libreadline4              4.2-3          GNU readline and history libraries


---------------------------------------
Received: (at 106656-done) by bugs.debian.org; 29 Dec 2005 07:00:55 +0000
>From [EMAIL PROTECTED] Wed Dec 28 23:00:55 2005
Return-path: <[EMAIL PROTECTED]>
Received: from winfree.gag.com ([192.133.104.8] ident=postfix)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1ErrmQ-0005XI-Tg
        for [EMAIL PROTECTED]; Wed, 28 Dec 2005 23:00:55 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])
        by winfree.gag.com (Postfix) with ESMTP id 470A3781E0
        for <[EMAIL PROTECTED]>; Thu, 29 Dec 2005 00:00:54 -0700 (MST)
Received: from winfree.gag.com ([127.0.0.1])
        by localhost (winfree [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 29202-04 for <[EMAIL PROTECTED]>;
        Thu, 29 Dec 2005 00:00:53 -0700 (MST)
Received: from reverse.gag.com (reverse.gag.com [192.133.104.19])
        by winfree.gag.com (Postfix) with SMTP id 1DE3C781D5
        for <[EMAIL PROTECTED]>; Thu, 29 Dec 2005 00:00:53 -0700 (MST)
Received: by reverse.gag.com (sSMTP sendmail emulation); Thu, 29 Dec 2005 
00:00:53 -0700
From: "Bdale Garbee" <[EMAIL PROTECTED]>
Date: Thu, 29 Dec 2005 00:00:53 -0700
To: [EMAIL PROTECTED]
Subject: no longer a problem
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at gag.com
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02

I can't reproduce the reported amrecover index problem in the current versions
of Amanda that are in Debian, so I have to assume something upstream or I did
in the past four and a half years fixed this.  Closing this bug with no further
action taken.

Bdale


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to