39:19 PM GMT -05:00 US/Canada Eastern
Subject: Re: amidxtaped v3.1.1 bug (critical (fatal): Modification of
non-creatable array value attempted)
Fantastic! That did the trick.
Will you be including this in 3.1.2? For the moment, I patched the RPMSRC from
the Zmanda binary repo and it works g
?
Thanks!
- Original Message -
From: "Luc Lalonde"
To: "Dustin J. Mitchell"
Cc: amanda-users@amanda.org
Sent: Tuesday, August 10, 2010 2:39:19 PM GMT -05:00 US/Canada Eastern
Subject: Re: amidxtaped v3.1.1 bug (critical (fatal): Modification of
non-creatable array val
On Tue, Aug 10, 2010 at 1:39 PM, Luc Lalonde wrote:
> Fantastic! That did the trick.
Great - thanks!
> Will you be including this in 3.1.2? For the moment, I patched the RPMSRC
> from the Zmanda binary repo and it works great with your modifications.
No, 3.1.2 is tagged already and we're jus
t;
Cc: amanda-users@amanda.org
Sent: Monday, August 9, 2010 5:53:55 PM GMT -05:00 US/Canada Eastern
Subject: Re: amidxtaped v3.1.1 bug (critical (fatal): Modification of
non-creatable array value attempted)
Ok, I took a look at the logfiles, and they're *very* old-school. It
looks like th
Ok, I took a look at the logfiles, and they're *very* old-school. It
looks like there's been a longstanding bug in find.c that mis-parsed
some of these log entries, and now that we're up and running with
Amanda::DB::Catalog, that mis-parsing causes failures.
I managed to reproduce this by excerpt
On Mon, Aug 9, 2010 at 10:36 AM, Luc Lalonde wrote:
> All I can say is that I don't get this problem using 2.6.1p2 only 3.1.1 on
> the server side.
It's quite possible that the older versions were masking some
corruption in the trace logs -- or that you have some older trace logs
which the new v
;
Cc: amanda-users@amanda.org
Sent: Saturday, August 7, 2010 8:03:38 PM GMT -05:00 US/Canada Eastern
Subject: Re: amidxtaped v3.1.1 bug (critical (fatal): Modification of
non-creatable array value attempted)
On Fri, Aug 6, 2010 at 1:34 PM, Luc Lalonde wrote:
> amidxtaped: Modification
On Fri, Aug 6, 2010 at 1:34 PM, Luc Lalonde wrote:
> amidxtaped: Modification of non-creatable array value attempted, subscript -1
> at /usr/lib/perl5/site_perl/5.8.8/Amanda/DB/Catalog.pm line 636.
Here is the suspect line in Amanda/DB/Catalog.pm:
636 $dump->{'
d: CTL << DISK=^/store/homes/jl$
Fri Aug 6 14:20:18 2010: amidxtaped: CTL << DATESTAMP=20100803
Fri Aug 6 14:20:18 2010: amidxtaped: CTL << END
Fri Aug 6 14:20:18 2010: amidxtaped: pid 16100 ruid 515 euid 515 version
3.1.1: rename at Fri Aug 6 14:20:18 2010
Fri Aug 6 14:20
>The zd-mtx excitement continues...
No kidding :-).
>My solution is just to use "grep -w" instead of "grep" in the appropriate
>places. ...
How about we do this "the shell way" and get rid of grep and awk
altogether?
I don't know the format of the "labelfile" (where is it documented?),
but on
The zd-mtx excitement continues...
I found that the script was getting confused when I had an amlabel which
was a substring of another amlabel. i.e. "Kiva2" and "Kiva22". When the
script grepped the amlabel out of the labelfile it was matching more than
one line.
My solution is just to use "gre
Monserrat Seisdedos NuÓez wrote:
>
> Hello every body:
> i did a modification in the amstatus script, it looked for amdump file by
> default, but amanda creates amdump.1, as the newer file, so if i typed
> amstatus Diario, (Diario is where i have the amanda.conf), it said tha
>i did a modification in the amstatus script, it looked for amdump file by
>default, but amanda creates amdump.1, as the newer file, so if i typed
>amstatus Diario, (Diario is where i have the amanda.conf), it said that the
>$logdir/amdum doesn't exist, so you had to type th
Hello every body:
i did a modification in the amstatus script, it looked for amdump file by
default, but amanda creates amdump.1, as the newer file, so if i typed
amstatus Diario, (Diario is where i have the amanda.conf), it said that the
$logdir/amdum doesn't exist, so you had to typ
14 matches
Mail list logo
