Re: amoverview under 3.1.2
On Mon, Sep 13, 2010 at 04:43:19PM -0500, Dustin J. Mitchell wrote: I'm sorry, I gave the wrong patch before. The patch I intended hasn't been committed yet, because I failed to correctly request review :) http://github.com/djmitche/amanda/commit/z11892 If anyone can review and confirm that patch, I'll get it committed. In the above patch one single to double dash was missed (skipmissed) On Mon, Sep 13, 2010 at 3:27 PM, Jon LaBadie j...@jgcomp.com wrote: More important, I found lots of other uninitialized errors with the various options. Patched I still get uninitialized value errors. --num0: uninitialized value in pattern match (m//) at /usr/sbin/amoverview line 138. --togo0: uninitialized value in pattern match (m//) at /usr/sbin/amoverview line 153 --last: uninitialized value in string eq at /usr/sbin/amoverview line 122 In general, amoverview needs some TLC. Orion's done a good job so far, hopefully my patch above helps, and certainly others are welcome to step up. I'm surprised that the long options with a single dash work at all, but the only need a unique prefix thing is well-known. I'll get the docs and usage fixed up to use double-dashes for long options. With your patch the long options still seem to work with a single dash. And another surprise, single letter options, or shortened versions of the options, work with single or double dash. Jon -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: amoverview under 3.1.2
On Tue, Sep 14, 2010 at 1:42 AM, Jon LaBadie j...@jgcomp.com wrote: In the above patch one single to double dash was missed (skipmissed) I'd say I left that in there just to see if you were looking at the patch, but that's not true. I'll fix it up. Patched I still get uninitialized value errors. --num0: uninitialized value in pattern match (m//) at /usr/sbin/amoverview line 138. --togo0: uninitialized value in pattern match (m//) at /usr/sbin/amoverview line 153 --last: uninitialized value in string eq at /usr/sbin/amoverview line 122 Orion, can you take a look, please? With your patch the long options still seem to work with a single dash. And another surprise, single letter options, or shortened versions of the options, work with single or double dash. Yes, this is expected (apparently). It's a feature of Perl's GetOpt::Long. Let's just pretend it doesn't exist :) Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amoverview under 3.1.2
On Tue, Sep 14, 2010 at 8:16 AM, McGraw, Robert P rmcg...@purdue.edu wrote: I went to github and got the latest amoverview.pl file (this morning), saved it in my src directory, ran gmake to recompile and gmake -install to install the new version of amoverview. When I run I get the WARNINGS as shown in the attached file. I have also attached the amoverview.pl file that I used to compile. That looks like the version that still used 'eval' and was thus full of warnings. Try this version: http://github.com/zmanda/amanda/blob/master/server-src/amoverview.pl Which will probably still have the warnings that Jon noted. Dustin -- Open Source Storage Engineer http://www.zmanda.com
RE: amoverview under 3.1.2
Attached is the output from the following commands. amoverview daily -diskwidth 30 -num0 -togo0 amoverview.output2.txt and amoverview daily only produces the following WARNINGS lines. ** (process:15681): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15681): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. -num0 and -togo0 produce the other WARNING line numbers as show in the attachmeht. Robert -Original Message- From: djmit...@gmail.com [mailto:djmit...@gmail.com] On Behalf Of Dustin J. Mitchell Sent: Tuesday, September 14, 2010 1:53 PM To: McGraw, Robert P Cc: amanda-users@amanda.org; Orion Poplawski Subject: Re: amoverview under 3.1.2 On Tue, Sep 14, 2010 at 8:16 AM, McGraw, Robert P rmcg...@purdue.edu wrote: I went to github and got the latest amoverview.pl file (this morning), saved it in my src directory, ran gmake to recompile and gmake -install to install the new version of amoverview. When I run I get the WARNINGS as shown in the attached file. I have also attached the amoverview.pl file that I used to compile. That looks like the version that still used 'eval' and was thus full of warnings. Try this version: http://github.com/zmanda/amanda/blob/master/server-src/amoverview.pl Which will probably still have the warnings that Jon noted. Dustin -- Open Source Storage Engineer http://www.zmanda.com amoverview daily -diskwidth 30 -num0 -togo0 xxx ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 108. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 138. ** (process:15527): WARNING
amoverview under 3.1.2
I have compiled and installed amanda 3.1.2 My dumps ran ok over the weekend with no errors. But I am getting the following warnings in amoverview. Robert ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. date 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 09 09 09 09 09 09 09 09 09 09 09 09 host disk 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 01 02 03 04 05 06 07 08 09 10 11 12 banach / 3 0 0 1 2 2 2 0 E1 0 0 1 1 1 2 0 1 0 1 2 3 0 0 1 2 2 ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. banach /boot 1 0 1 1 1 0 1 1 1 0 1 1 1 1 0 1 E0 1 1 1 1 0 1 1 1 ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. _ Robert P. McGraw, Jr. Manager, Computer SystemEMAIL: rmcg...@purdue.edu Purdue UniversityROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street West Lafayette, IN 47907-2067
RE: amoverview under 3.1.2
As a followup, I ran amoverview and removed the WARNINGS messages and it seems to be working correctly. Here is a snippet date NM TO 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 09 09 09 09 09 09 09 09 09 09 09 09 host disk L0 GO 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 01 02 03 04 05 06 07 08 09 10 11 12 banach / 9 22 3 0 0 1 2 2 2 0 E1 0 0 1 1 1 2 0 1 0 1 2 3 0 0 1 2 2 banach /boot 6 21 1 0 1 1 1 0 1 1 1 0 1 1 1 1 0 1 E0 1 1 1 1 0 1 1 1 bers / 7 24 0 1 1 0 1 1 1 1 0 1 1 1 1 1 0 1 0 1 1 1 1 0 1 1 0 1 bessel / 7 24 0 1 1 0 1 1 1 1 0 1 1 1 1 1 0 1 0 1 1 1 0 1 1 1 0 1 bohr / 7 24 0 1 1 0 1 1 1 1 0 1 1 1 1 1 0 1 0 1 1 1 0 1 1 1 0 1 conon/ 6 21 0 1 1 1 1 0 1 1 1 0 1 1 1 1 0 1 0 1 1 1 1 0 1 1 1 Robert -Original Message- From: McGraw, Robert P Sent: Monday, September 13, 2010 11:40 AM To: McGraw, Robert P Subject: RE: amoverview under 3.1.2 As a followup, I ran amoverview and removed the WARNINGS and it seems to be working correctly. Robert -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda- us...@amanda.org] On Behalf Of McGraw, Robert P Sent: Monday, September 13, 2010 11:24 AM To: 'amanda-users@amanda.org' Subject: amoverview under 3.1.2 I have compiled and installed amanda 3.1.2 My dumps ran ok over the weekend with no errors. But I am getting the following warnings in amoverview. Robert ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. date 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 09 09 09 09 09 09 09 09 09 09 09 09 host disk 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 01 02 03 04 05 06 07 08 09 10 11 12 banach / 3 0 0 1 2 2 2 0 E1 0 0 1 1 1 2 0 1 0 1 2 3 0 0 1 2 2 ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. banach /boot 1 0 1 1 1 0 1 1 1 0 1 1 1 1 0 1 E0 1 1 1 1 0 1 1 1 ** (process:11519): WARNING **: Use of uninitialized value in substr at (eval 15) line 3. _ Robert P. McGraw, Jr. Manager, Computer SystemEMAIL: rmcg...@purdue.edu Purdue UniversityROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street West Lafayette, IN 47907-2067
Re: amoverview under 3.1.2
Robert, can you try the attached patch?
Jean-Louis
McGraw, Robert P wrote:
As a followup, I ran amoverview and removed the WARNINGS messages and it seems
to be working correctly.
Here is a snippet
date NM TO 08 08 08 08 08 08 08 08 08 08 08
08 08 08 08 08 09 09 09 09 09 09 09 09 09 09 09 09
host disk L0 GO 16 17 18 19 20 21 22 23 24 25 26
27 28 29 30 31 01 02 03 04 05 06 07 08 09 10 11 12
banach / 9 22 3 0 0 1 2 2 2 0 E1 0 0
1 1 1 2 0 1 0 1 2 3 0 0 1 2 2
banach /boot 6 21 1 0 1 1 1 0 1 1 1 0 1
1 1 1 0 1 E0 1 1 1 1 0 1 1 1
bers / 7 24 0 1 1 0 1 1 1 1 0 1 1
1 1 1 0 1 0 1 1 1 1 0 1 1 0 1
bessel / 7 24 0 1 1 0 1 1 1 1 0 1 1
1 1 1 0 1 0 1 1 1 0 1 1 1 0 1
bohr / 7 24 0 1 1 0 1 1 1 1 0 1 1
1 1 1 0 1 0 1 1 1 0 1 1 1 0 1
conon/ 6 21 0 1 1 1 1 0 1 1 1 0 1
1 1 1 0 1 0 1 1 1 1 0 1 1 1
Robert
-Original Message-
From: McGraw, Robert P
Sent: Monday, September 13, 2010 11:40 AM
To: McGraw, Robert P
Subject: RE: amoverview under 3.1.2
As a followup, I ran amoverview and removed the WARNINGS and it seems
to be working correctly.
Robert
-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-
us...@amanda.org] On Behalf Of McGraw, Robert P
Sent: Monday, September 13, 2010 11:24 AM
To: 'amanda-users@amanda.org'
Subject: amoverview under 3.1.2
I have compiled and installed amanda 3.1.2
My dumps ran ok over the weekend with no errors.
But I am getting the following warnings in amoverview.
Robert
** (process:11519): WARNING **: Use of uninitialized value in substr
at
(eval 15) line 3.
** (process:11519): WARNING **: Use of uninitialized value in substr
at
(eval 15) line 3.
date 08 08 08 08 08 08 08 08 08 08 08 08 08
08
08 08 09 09 09 09 09 09 09 09 09 09 09 09
host disk 16 17 18 19 20 21 22 23 24 25 26 27 28
29
30 31 01 02 03 04 05 06 07 08 09 10 11 12
banach / 3 0 0 1 2 2 2 0 E1 0 0 1 1
1
2 0 1 0 1 2 3 0 0 1 2 2
** (process:11519): WARNING **: Use of uninitialized value in substr
at
(eval 15) line 3.
** (process:11519): WARNING **: Use of uninitialized value in substr
at
(eval 15) line 3.
** (process:11519): WARNING **: Use of uninitialized value in substr
at
(eval 15) line 3.
banach /boot 1 0 1 1 1 0 1 1 1 0 1 1 1
1
0 1 E0 1 1 1 1 0 1 1 1
** (process:11519): WARNING **: Use of uninitialized value in substr
at
(eval 15) line 3.
_
Robert P. McGraw, Jr.
Manager, Computer SystemEMAIL: rmcg...@purdue.edu
Purdue UniversityROOM: MATH-807
Department of Mathematics PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067
diff --git a/perl/Amanda/Tapelist.swg b/perl/Amanda/Tapelist.swg
index e1e029d..6e39d08 100644
--- a/perl/Amanda/Tapelist.swg
+++ b/perl/Amanda/Tapelist.swg
@@ -35,6 +35,29 @@ use File::Copy;
## package functions
+sub new {
+my ($filename, $lock ) = @_;
+my $self = {
+ filename = $filename,
+ lock = $lock,
+};
+bless $self, Amanda::Tapelist;
+
+# let C read the file
+C_read_tapelist($filename);
+
+# and then read it ourselves
+open(my $fh, , $filename) or return $self;
+$self-{'fh'} = $fh;
+
+if ($lock) {
+ flock($lock, LOCK_EX);
+}
+
+$self-_read_tapelist_fh();
+return $self;
+}
+
sub read_tapelist {
my ($filename) = @_;
my $self = {
@@ -134,24 +157,35 @@ sub write {
my $new_tapelist_file = $filename . -new- . time();
-open(my $fh, , $new_tapelist_file) or die(Could not open '$new_tapelist_file' for writing: $!);
+open(my $fhn, , $new_tapelist_file) or die(Could not open '$new_tapelist_file' for writing: $!);
for my $tle (@{$self-{tles}}) {
my $datestamp = $tle-{'datestamp'};
my $label = $tle-{'label'};
my $reuse = $tle-{'reuse'} ? 'reuse' : 'no-reuse';
my $comment = (defined $tle-{'comment'})? ( # . $tle-{'comment'}) : '';
- print $fh $datestamp $label $reuse$comment\n;
+ print $fhn $datestamp $label $reuse$comment\n;
}
-close($fh);
+close($fhn);
unless (move($new_tapelist_file, $filename)) {
die (failed to rename '$new_tapelist_file' to '$filename': $!);
}
+$self-close();
+
# re-read from the C side
Re: amoverview under 3.1.2
On Mon, Sep 13, 2010 at 10:23 AM, McGraw, Robert P rmcg...@purdue.edu wrote: I have compiled and installed amanda 3.1.2 My dumps ran ok over the weekend with no errors. But I am getting the following warnings in amoverview. We just saw a similar warning with a Zmanda customer, and did some significant reorganization in fixing it: http://github.com/zmanda/amanda/commit/78d97fad2a79d8928ae1d1cc79ce3701d70fce4a You can probably apply that patch relatively easily, or even just copy the amoverview script from the source tree, being careful to change @amperldir@ to point to the Amanda perl modules, wherever those might be on your system. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amoverview under 3.1.2
On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau martin...@zmanda.com wrote: Robert, can you try the attached patch? (only the amoverview hunk is required, right Jean-Louis?) Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amoverview under 3.1.2
Dustin J. Mitchell wrote:
On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau
martin...@zmanda.com wrote:
Robert, can you try the attached patch?
(only the amoverview hunk is required, right Jean-Louis?)
yes, The correct patch is attached.
Jean-Louis
diff --git a/server-src/amoverview.pl b/server-src/amoverview.pl
index 4f721e5..5dbd625 100644
--- a/server-src/amoverview.pl
+++ b/server-src/amoverview.pl
@@ -195,13 +195,13 @@ my $top_format = format TOP =\n\n .
join(' ', map((/..(..)/)[0], sort keys %dates)) . \n .
\n.\n;
-+ local ($::thishost,$::thisdisk);
+local ($::thishost,$::thisdisk);
my $out_format = format STDOUT =\n .
@ . x ($opt_hostwidth - 1) . ' ' .
@ . x ($opt_diskwidth - 1) . ' ' .
'@ ' x scalar(keys %dates) . \n .
join(', ', '$::thishost', '$::thisdisk',
- map(substr(\$level{\$::thishost}{\$::thisdisk}{'$_'},-2), sort keys %dates)) . \n .
+ map(defined(\$level{\$::thishost}{\$::thisdisk}{'$_'})?substr(\$level{\$::thishost}{\$::thisdisk}{'$_'},-2):' ', sort keys %dates)) . \n .
.\n;
eval $top_format;
RE: amoverview under 3.1.2
Sorry I spoke a little to soon as I did not see the WARNING messages go by, which were outputted first then the overview output. I get 11 of the following WARNING messages ** (process:14893): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. Then I get the overview output which looks correct. date 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 09 09 09 09 09 09 09 09 09 09 09 09 host disk 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 01 02 03 04 05 06 07 08 09 10 11 12 banach / 0 0 1 2 2 2 0 E1 0 0 1 1 1 2 0 1 0 1 2 3 0 0 1 2 2 banach /boot 0 1 1 1 0 1 1 1 0 1 1 1 1 0 1 E0 1 1 1 1 0 1 1 1 1 bers / 1 1 0 1 1 1 1 0 1 1 1 1 1 0 1 0 1 1 1 1 0 1 1 0 1 Robert -Original Message- From: Jean-Louis Martineau [mailto:martin...@zmanda.com] Sent: Monday, September 13, 2010 12:38 PM To: Dustin J. Mitchell Cc: McGraw, Robert P; amanda-users@amanda.org Subject: Re: amoverview under 3.1.2 Dustin J. Mitchell wrote: On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau martin...@zmanda.com wrote: Robert, can you try the attached patch? (only the amoverview hunk is required, right Jean-Louis?) yes, The correct patch is attached. Jean-Louis
RE: amoverview under 3.1.2
Applied the patch and the problem has been resolved. Thanks Robert -Original Message- From: Jean-Louis Martineau [mailto:martin...@zmanda.com] Sent: Monday, September 13, 2010 12:38 PM To: Dustin J. Mitchell Cc: McGraw, Robert P; amanda-users@amanda.org Subject: Re: amoverview under 3.1.2 Dustin J. Mitchell wrote: On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau martin...@zmanda.com wrote: Robert, can you try the attached patch? (only the amoverview hunk is required, right Jean-Louis?) yes, The correct patch is attached. Jean-Louis
RE: amoverview under 3.1.2
I thought it was fixed but this time the warnings were at the beginning of the output and I did not catch them. I have attached the output from an amoverview run. The output looks correct. Robert -Original Message- From: Jean-Louis Martineau [mailto:martin...@zmanda.com] Sent: Monday, September 13, 2010 12:38 PM To: Dustin J. Mitchell Cc: McGraw, Robert P; amanda-users@amanda.org Subject: Re: amoverview under 3.1.2 Dustin J. Mitchell wrote: On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau martin...@zmanda.com wrote: Robert, can you try the attached patch? (only the amoverview hunk is required, right Jean-Louis?) yes, The correct patch is attached. Jean-Louis [96][amandaba...@hertz]:~/sbin% amoverview daily -diskwidth 30 -num0 -togo0 ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in string eq at /local/amanda/amanda/sbin/amoverview line 107. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized value in pattern match (m//) at /local/amanda/amanda/sbin/amoverview line 137. ** (process:15864): WARNING **: Use of uninitialized
Re: amoverview under 3.1.2
On Mon, Sep 13, 2010 at 1:44 PM, McGraw, Robert P rmcg...@purdue.edu wrote: I thought it was fixed but this time the warnings were at the beginning of the output and I did not catch them. Jean-Louis' patch only addresses one of the warnings. Try applying the patch I linked to, instead. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: amoverview under 3.1.2
On Mon, Sep 13, 2010 at 11:09:41AM -0500, Dustin J. Mitchell wrote: On Mon, Sep 13, 2010 at 10:23 AM, McGraw, Robert P rmcg...@purdue.edu wrote: I have compiled and installed amanda 3.1.2 My dumps ran ok over the weekend with no errors. But I am getting the following warnings in amoverview. We just saw a similar warning with a Zmanda customer, and did some significant reorganization in fixing it: http://github.com/zmanda/amanda/commit/78d97fad2a79d8928ae1d1cc79ce3701d70fce4a You can probably apply that patch relatively easily, or even just copy the amoverview script from the source tree, being careful to change @amperldir@ to point to the Amanda perl modules, wherever those might be on your system. My install is from a Zmanda prebuilt binary and already had the changes the above URL mentions. But I get the same error (see my 8/22 post to the hackers list. Not having the source I manually applied Jean-Louis' patch and that did correct the problem. But ... I decided to try some of the amoverview options. I was surprised that the long options can be shortened. For example -verbose can be given as -verb or -v but not -verbose0 or -verbosf. This same behavior was true for each of the amoverview options. Good thing they all start with different letters. BTW -verbose did not show an differences from regular output. More important, I found lots of other uninitialized errors with the various options. With -last WARNING **: Use of uninitialized value in string eq at /usr/sbin/amoverview line 118. WARNING **: Use of uninitialized value in string eq at /usr/sbin/amoverview line 121. With -num0 WARNING **: Use of uninitialized value in pattern match (m//) at /usr/sbin/amoverview line 137. With -togo0 WARNING **: Use of uninitialized value in pattern match (m//) at /usr/sbin/amoverview line 152. I did not include the other 88 duplicats of each of the above messages :) Jon -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: amoverview under 3.1.2
I'm sorry, I gave the wrong patch before. The patch I intended hasn't been committed yet, because I failed to correctly request review :) http://github.com/djmitche/amanda/commit/z11892 If anyone can review and confirm that patch, I'll get it committed. On Mon, Sep 13, 2010 at 3:27 PM, Jon LaBadie j...@jgcomp.com wrote: More important, I found lots of other uninitialized errors with the various options. In general, amoverview needs some TLC. Orion's done a good job so far, hopefully my patch above helps, and certainly others are welcome to step up. I'm surprised that the long options with a single dash work at all, but the only need a unique prefix thing is well-known. I'll get the docs and usage fixed up to use double-dashes for long options. Dustin -- Open Source Storage Engineer http://www.zmanda.com
amoverview question
Amanda 3.1.1. on Solaris 10 x86 There was recent talk about a problem and possible fix for the amoverview in amanda 3.1.1. Was there a patch for this problem? Robert _ Robert P. McGraw, Jr. Manager, Computer SystemEMAIL: rmcg...@purdue.edu Purdue UniversityROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street West Lafayette, IN 47907-2067
Re: amoverview question
On Fri, Aug 6, 2010 at 8:58 AM, McGraw, Robert P rmcg...@purdue.edu wrote: Was there a patch for this problem? Thanks to Orion, yes: http://github.com/zmanda/amanda/commit/6ab225a354869f0c85a86e4407dd56193f3872c2 http://github.com/zmanda/amanda/commit/c1fec3ef1b20b0426d7ea702590231740ee4db21 http://github.com/zmanda/amanda/commit/78d97fad2a79d8928ae1d1cc79ce3701d70fce4a Dustin -- Open Source Storage Engineer http://www.zmanda.com
amoverview something wrong
I am running amanda 2.5.1p1 from amanda.org. When I run amoverview I get this type of output. Has anybody seen this and if it is a know problem has there been a fix. Thanks Robert ' '2006-09-27 zuse / 0 D00011 8 -- OK ' '2006-09-28 zuse / 1 D00012 12 -- OK ' '2006-09-29 20:10:19 zuse / 0 D00013 11 -- OK ' date LA 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 host disk ST 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 bers / bessel / bohr / coriolis /local euler/ _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
amoverview bug
On 2006-06-05 18:09, Jon LaBadie wrote: Besides the gnutar-lists problem, I just noticed another wierd result. If I run amoverview, lots of the columns report two runs per day, not one. And I assure you only one was run each day. Here is a portion of the output: bigcow ROOT-MISC 1 1 1 0 1 0 1 1 1 1 1 1 0 bigcow USR0 0011 11 11 11 11 11 00 11 1 1 1 bigcow VAR1 1111 00 00 11 11 11 11 22 2 00 1 All the DLE's having many tape chunks have this bug. However in the case of tape-chunked file, it returns a line for each chumber where only the filenumber is different. When parsing the output of amadmin daiy find, amoverview does not take into account the partnumber field, and hence believes there are multiple dumps of that level on one tape. (it shows only the last two of them). It should take into account also the partnumber. And maybe verify that each partnumber has status OK at least once? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview bug
On Tue, Jun 06, 2006 at 09:42:06AM +0200, Paul Bijnens wrote: On 2006-06-05 18:09, Jon LaBadie wrote: Besides the gnutar-lists problem, I just noticed another wierd result. If I run amoverview, lots of the columns report two runs per day, not one. And I assure you only one was run each day. Here is a portion of the output: bigcow ROOT-MISC 1 1 1 0 1 0 1 1 1 1 1 1 0 bigcow USR0 0011 11 11 11 11 11 00 11 1 1 1 bigcow VAR1 1111 00 00 11 11 11 11 22 2 00 1 All the DLE's having many tape chunks have this bug. However in the case of tape-chunked file, it returns a line for each chumber where only the filenumber is different. When parsing the output of amadmin daiy find, amoverview does not take into account the partnumber field, and hence believes there are multiple dumps of that level on one tape. (it shows only the last two of them). Seems like a good explanation, thanks. It should take into account also the partnumber. And maybe verify that each partnumber has status OK at least once? And a different letter than E error, maybe M for missing? Though I guess that would be an error also. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amoverview error codes
Hello everyone, I'm a bit foggy on one case of error codes in the amoverview output. The documentation says that E indicates an error, and that E followed by a number indicated an error flushing that was later corrected. Cool. I sometimes see errors that are of the form 1E and I can't figure out what this would mean. A level 1 dump was flushed, and then the second time there was an error? Doesn't make much sense to flush twice, and I don't see this case in the documentation. Any hints? -- Ross Vandegrift [EMAIL PROTECTED] The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell. --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37
amoverview
Can anyone help me in getting the things work for me when i run [EMAIL PROTECTED] amanda]$ amoverview DailySet1 | grep oaks oaks.mum /home/kaushal 1 22 3 [EMAIL PROTECTED] amanda]$ But doesnot gives me the date info. how do i get the date information viz [EMAIL PROTECTED] amanda]$ amoverview DailySet1 date 09 09 09 09 09 09 09 host disk 16 17 18 19 20 21 22 Would appreciate if anyone can help me? -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. Tel : +91-22-22881326/27 Fax : +91-22-22881318 Cell : +91-9820367783 signature.asc Description: This is a digitally signed message part
Re: amoverview
On Thursday 23 September 2004 09:00, Kaushal Shriyan wrote: when i run [EMAIL PROTECTED] amanda]$ amoverview DailySet1 | grep oaks oaks.mum /home/kaushal 1 22 3 But doesnot gives me the date info. how do i get the date information viz amoverview DailySet1 |head -3 amoverview DailySet1 |grep oaks ?? /andreas
amoverview
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, On one server I have this result after running amoverview conf : ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 host disk 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 client /etc 0 E E 0 0 0 0 1 1 0 0 0 0 0 0 On another I have this one : ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 host disk 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 client2 /space1/local/progs/ 4 4 5 0 1 2 3 4 4 EE 1 2 3 EE I'd to know what do mean E and EE ? Is there someone who can explain me what kind of symbol I can find and what do they mean ? - -- Cordialement, Sincerely, Christian MOLIERE Tél : 01.43.60.11.60 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAhhtUZ30NRCZKZ48RArqPAJ9H/DepX6agLeCEmmADte8BE484gACglHXX +FmyE6filoGzcuEqxQOF2tc= =YpdM -END PGP SIGNATURE-
Re: amoverview
Christian Molière wrote: On one server I have this result after running amoverview conf : ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 host disk 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 client /etc 0 E E 0 0 0 0 1 1 0 0 0 0 0 0 On another I have this one : ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 host disk 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 client2 /space1/local/progs/ 4 4 5 0 1 2 3 4 4 EE 1 2 3 EE I'd to know what do mean E and EE ? Is there someone who can explain me what kind of symbol I can find and what do they mean ? amoverview is a summary of the output of amadmin conf find. When the last column of amadmin find contains anything other than OK, amoverview translates this into 'E' for that day. A number indicates the level of backup and it succeeded. An E indicates an error for that day. You get an 'E' for all errors, like failed to connect, datatimeout, computer crashed, etc, but also for failing to write to tape. You can have an E followed by a number if a filesystem ran into end-of-tape once (gives an 'E', and later that day, you flush it to a second tape (a number: the level, indicating success). If the flush failed too, you get a double EE for that day. You can also have a double code if you have two tapes in the changer and amanda failed to write to tape the first time because it hit end of tape (resulting in E0, for a full, E1 for an incremental etc) or twice with error (EE), and may a successfull flush afterwards giving maybe EE0. (I've never that last one happen). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I saw this morning this result of amadmin command on one server : 2004-04-20 client /space1/processed 0 --- 0 FAILED (driver) [dump to tape failed] 2004-04-20 client /space1/processed 0 --- 0 FAILED (dumper) [data write: Connection reset by peer] 2004-04-20 client /space1/processed 0 TAPE_27 1 OK As amanda server wasn't able to write on selected tape, it changed it and was able to write on the following tape. But when I use amoverview command here it is the result : client /space1/processed 4 4 5 0 1 2 3 4 4 EE 1 ~ 2 3 EE As you can see, it is EE code and not as you explained me EE0. Could you explain me why it's like that ? Paul Bijnens wrote: | Christian Molière wrote: | | On one server I have this result after running amoverview conf : | | ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04 | 04 04 | host disk 06 07 08 09 10 11 12 13 14 15 16 17 18 | 19 20 | client /etc 0 E E 0 0 0 0 1 1 0 0 0 0 0 0 | | On another I have this one : | | ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04 | 04 04 | host disk 06 07 08 09 10 11 12 13 14 15 16 17 18 | 19 20 | client2 /space1/local/progs/ 4 4 5 0 1 2 3 4 4 EE 1 2 3 EE | | | I'd to know what do mean E and EE ? Is there someone who can explain | me what kind of symbol I can find and what do they mean ? | | | amoverview is a summary of the output of amadmin conf find. | When the last column of amadmin find contains anything other than OK, | amoverview translates this into 'E' for that day. | | A number indicates the level of backup and it succeeded. | An E indicates an error for that day. | You get an 'E' for all errors, like failed to connect, datatimeout, | computer crashed, etc, but also for failing to write to tape. | | You can have an E followed by a number if a filesystem ran into | end-of-tape once (gives an 'E', and later that day, you flush it to a | second tape (a number: the level, indicating success). If the flush | failed too, you get a double EE for that day. | | You can also have a double code if you have two tapes in the changer and | amanda failed to write to tape the first time because it hit end of tape | (resulting in E0, for a full, E1 for an incremental etc) | or twice with error (EE), and may a successfull flush afterwards | giving maybe EE0. (I've never that last one happen). | | - -- Cordialement, Sincerely, Christian MOLIERE Tél : 01.43.60.11.60 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAhjDnZ30NRCZKZ48RAjyXAKCdWL9yitwNSz1meIAK9VjD9XHExACfURv3 XQn5PrPG7JZ3VlfyiLtYVYc= =aDRe -END PGP SIGNATURE-
Re: amoverview
Christian Molière wrote:
I saw this morning this result of amadmin command on
one server :
2004-04-20 client /space1/processed 0 --- 0 FAILED
(driver) [dump to tape failed]
2004-04-20 client /space1/processed 0 --- 0 FAILED
(dumper) [data write: Connection reset by peer]
2004-04-20 client /space1/processed 0 TAPE_27 1 OK
As amanda server wasn't able to write on selected tape, it changed it
and was able to write on the following tape.
But when I use amoverview command here it is the result :
client /space1/processed 4 4 5 0 1 2 3 4 4 EE 1
~ 2 3 EE
As you can see, it is EE code and not as you explained me EE0.
Could you explain me why it's like that ?
The best documentation is the source, and amoverview is a little perl
script. Here is part with the format for the output line:
152 my $out_format = format STDOUT =\n .
153 @ . x ($opt_hostwidth - 1) . ' ' .
154 @ . x ($opt_diskwidth - 1) . ' ' .
155 '@ ' x scalar(keys %dates) . \n .
156 join(', ', '$host', '$disk',
157 map(\$level{\$host}{\$disk}{'$_'}, sort keys %dates))
. \n .
158 .\n;
159
And, indeed, line 155 is the format to print the codes. The format @
right justifies, AND truncates to two characters...
That's probably why I never seen three codes like EE0.
Maybe it would indeed be better to see the last two characters instead
of the first two: it's the end result that counts.
Line 157 could be written as:
map(substr(\$level{\$host}{\$disk}{'$_'},-2), sort keys %dates)) ...
Can you try this out?
Paul Bijnens wrote:
| Christian Molière wrote:
|
| On one server I have this result after running amoverview conf :
|
| ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04
| 04 04
| host disk 06 07 08 09 10 11 12 13 14 15 16 17 18
| 19 20
| client /etc 0 E E 0 0 0 0 1 1 0 0 0 0
0 0
|
| On another I have this one :
|
| ~ date 04 04 04 04 04 04 04 04 04 04 04 04 04
| 04 04
| host disk 06 07 08 09 10 11 12 13 14 15 16 17 18
| 19 20
| client2 /space1/local/progs/ 4 4 5 0 1 2 3 4 4 EE 1
2 3 EE
|
|
| I'd to know what do mean E and EE ? Is there someone who can explain
| me what kind of symbol I can find and what do they mean ?
|
|
| amoverview is a summary of the output of amadmin conf find.
| When the last column of amadmin find contains anything other than
OK,
| amoverview translates this into 'E' for that day.
|
| A number indicates the level of backup and it succeeded.
| An E indicates an error for that day.
| You get an 'E' for all errors, like failed to connect, datatimeout,
| computer crashed, etc, but also for failing to write to tape.
|
| You can have an E followed by a number if a filesystem ran into
| end-of-tape once (gives an 'E', and later that day, you flush it to a
| second tape (a number: the level, indicating success). If the flush
| failed too, you get a double EE for that day.
|
| You can also have a double code if you have two tapes in the
changer and
| amanda failed to write to tape the first time because it hit end of
tape
| (resulting in E0, for a full, E1 for an incremental etc)
| or twice with error (EE), and may a successfull flush afterwards
| giving maybe EE0. (I've never that last one happen).
|
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: amoverview
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
I tried in using your code line but it doesn't
run with this error message :
syntax error at (eval 4) line 3, near },
Paul Bijnens wrote:
| Christian Molière wrote:
|
| I saw this morning this result of amadmin command on
| one server :
|
| 2004-04-20 client /space1/processed 0 --- 0 FAILED
| (driver) [dump to tape failed]
| 2004-04-20 client /space1/processed 0 --- 0 FAILED
| (dumper) [data write: Connection reset by peer]
| 2004-04-20 client /space1/processed 0 TAPE_27 1 OK
|
| As amanda server wasn't able to write on selected tape, it changed it
| and was able to write on the following tape.
|
| But when I use amoverview command here it is the result :
|
| client /space1/processed 4 4 5 0 1 2 3 4 4 EE 1
| ~ 2 3 EE
|
| As you can see, it is EE code and not as you explained me EE0.
|
| Could you explain me why it's like that ?
|
|
| The best documentation is the source, and amoverview is a little perl
| script. Here is part with the format for the output line:
|
| 152 my $out_format = format STDOUT =\n .
| 153 @ . x ($opt_hostwidth - 1) . ' ' .
| 154 @ . x ($opt_diskwidth - 1) . ' ' .
| 155 '@ ' x scalar(keys %dates) . \n .
| 156 join(', ', '$host', '$disk',
| 157 map(\$level{\$host}{\$disk}{'$_'}, sort keys %dates))
| . \n .
| 158 .\n;
| 159
|
| And, indeed, line 155 is the format to print the codes. The format @
| right justifies, AND truncates to two characters...
| That's probably why I never seen three codes like EE0.
| Maybe it would indeed be better to see the last two characters instead
| of the first two: it's the end result that counts.
|
| Line 157 could be written as:
|
| map(substr(\$level{\$host}{\$disk}{'$_'},-2), sort keys
%dates)) ...
|
|
| Can you try this out?
|
|
|
|
| Paul Bijnens wrote:
| | Christian Molière wrote:
| |
| | On one server I have this result after running amoverview conf :
| |
| | ~ date 04 04 04 04 04 04 04 04 04 04 04
04 04
| | 04 04
| | host disk 06 07 08 09 10 11 12 13 14 15 16
17 18
| | 19 20
| | client /etc 0 E E 0 0 0 0 1 1 0 0 0 0
| 0 0
| |
| | On another I have this one :
| |
| | ~ date 04 04 04 04 04 04 04 04 04 04 04
04 04
| | 04 04
| | host disk 06 07 08 09 10 11 12 13 14 15 16
17 18
| | 19 20
| | client2 /space1/local/progs/ 4 4 5 0 1 2 3 4 4 EE 1
| 2 3 EE
| |
| |
| | I'd to know what do mean E and EE ? Is there someone who can
explain
| | me what kind of symbol I can find and what do they mean ?
| |
| |
| | amoverview is a summary of the output of amadmin conf find.
| | When the last column of amadmin find contains anything other than
| OK,
| | amoverview translates this into 'E' for that day.
| |
| | A number indicates the level of backup and it succeeded.
| | An E indicates an error for that day.
| | You get an 'E' for all errors, like failed to connect, datatimeout,
| | computer crashed, etc, but also for failing to write to tape.
| |
| | You can have an E followed by a number if a filesystem ran into
| | end-of-tape once (gives an 'E', and later that day, you flush it
to a
| | second tape (a number: the level, indicating success). If the flush
| | failed too, you get a double EE for that day.
| |
| | You can also have a double code if you have two tapes in the
| changer and
| | amanda failed to write to tape the first time because it hit end of
| tape
| | (resulting in E0, for a full, E1 for an incremental etc)
| | or twice with error (EE), and may a successfull flush afterwards
| | giving maybe EE0. (I've never that last one happen).
| |
|
|
|
- --
Cordialement,
Sincerely,
Christian MOLIERE
Tél : 01.43.60.11.60
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAhk67Z30NRCZKZ48RAmoMAKCc+Ls8QHLy5WVED0m6tf4kZ8YeQgCeM5wp
Xy/t9Acc5A+8pTDte3hmdic=
=z9Tv
-END PGP SIGNATURE-
Re: amoverview
Christian Molière wrote:
I tried in using your code line but it doesn't
run with this error message :
syntax error at (eval 4) line 3, near },
Of course, substr should have been inside the quotes.
Like this:
map(substr(\$level{\$host}{\$disk}{'$_'},-2), sort keys %dates)) ...
Giving this block:
152 my $out_format = format STDOUT =\n .
153 @ . x ($opt_hostwidth - 1) . ' ' .
154 @ . x ($opt_diskwidth - 1) . ' ' .
155 '@ ' x scalar(keys %dates) . \n .
156 join(', ', '$host', '$disk',
157 map(substr(\$level{\$host}{\$disk}{'$_'},-2), sort keys
%dates)) . \n .
158 .\n;
Aoperently not enough cafeine yet when I wrote my previous mail :-)
Now I tested it out myself (but not having a 3-byte code in my overview
to really really verify if it works).
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: amoverview
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
with this line : map(substr(\\$level{\$host}{\$disk}{'$_'}\,-2),
sort keys %dates))
it runs.
Thanks for your help and your explanations.
Paul Bijnens wrote:
| Christian Molière wrote:
|
| I tried in using your code line but it doesn't
| run with this error message :
| syntax error at (eval 4) line 3, near },
|
|
| Of course, substr should have been inside the quotes.
| Like this:
|
| map(substr(\$level{\$host}{\$disk}{'$_'},-2), sort keys %dates)) ...
|
|
| Giving this block:
|
| 152 my $out_format = format STDOUT =\n .
| 153 @ . x ($opt_hostwidth - 1) . ' ' .
| 154 @ . x ($opt_diskwidth - 1) . ' ' .
| 155 '@ ' x scalar(keys %dates) . \n .
| 156 join(', ', '$host', '$disk',
| 157 map(substr(\$level{\$host}{\$disk}{'$_'},-2), sort
keys
| %dates)) . \n .
| 158 .\n;
|
| Aoperently not enough cafeine yet when I wrote my previous mail :-)
| Now I tested it out myself (but not having a 3-byte code in my overview
| to really really verify if it works).
|
- --
Cordialement,
Sincerely,
Christian MOLIERE
Tél : 01.43.60.11.60
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAhlO1Z30NRCZKZ48RAlEDAKCYkFmy6205uWszjCXmz60jwgdAOwCeK8zZ
8YKe0w7GdajGUjO2osb0zEI=
=JW6h
-END PGP SIGNATURE-
Re: amoverview; history database
Urs Forster wrote: It apears to be quite hard to balance for amanda using whole file systems. Would it not be more conveinent to define subdirs rather than mountpoints in the disklist? (could one do that anyway?) You can use subdirs in the disklist if you use GNUtar as backup program. And yes, it's easier to juggle small things around than a few large ones (all relative to the tapesize). However, when amanda runs the first few times, it has too many DLE's (DiskList Entries) that are all due, and she tries to scram as much as possible on the give tapesize. After two, three cycles, things should have levelled out however. To avoid the rush to tape during the first days, some people add entries to the disklist a few at a time each day only. Or you could run one or more amdumps extra on the first days, asuming the tapecycle is larger than the dumpcycle. Cheers Urs Bitte keine Antwort an diese Mailadresse. Wird nicht gelesen. Don't reply to this address. Sorry, I had to reply to the list, the sender address just bounces. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview; history database
On Thursday 25 March 2004 10:57, Urs Forster wrote: Hi From: Gene Heskett [EMAIL PROTECTED] Date: Thu, 25 Mar 2004 09:58:16 -0500 On Thursday 25 March 2004 08:14, Urs Forster wrote: Hi When using amoverview I get a wide output (more than 3 month). This is not readable and anyway the data is obsolete, I only work on a cycle of 5 days. How can I purge old data from the history? Cheers Urs Good question perhaps. Here, its quite wide, but the dates coincide with the number of tapes in my tapecycle of 28. That seems to be a reasonable display. What is your tapecycle set to? I think thats the point. Now it's 5, but it used to be that high! Somwhere amanda remembers the higher number, but where? If you changed it in one swell foop, that which would have been bypassed is still there, it only deletes that which references the tape(s) just re-written. I don't think there is a problem in that case of you going into the index and currinfo dirs and doing a bit of obviously overdue housekeeping. Ok, I deletet all indexes, all curinfo, removed all extra tapes from changer.conf, ran amrmtape, amtape update, amcheckdb and I found out what fell swoop means (rather than swell foop; that was the harder part ;-). Despite all of those, amoverview still shows around 90 days across. Any more ideas? But why down to 5? One really should have a tapecycle thats at least 2*runtapes*runspercycle in order to have at least the 2 most recent full backups on hand at any one time. Anything less and you're playing russian roulette with a Morgolin Target Pistol as far as your data's safety is concerned... YMMV of course. :) I'm doing backup to disk (tapeless). In order to fit the largest filesystem I had to define the 'tape'-size to be around 3 Gb. Now, amanda seems to be a bit greedy - meaning it tries to fill every tape (by promoting full dumps). Since all 'tapes' lie on the same disk, I ran into space problems. Therefore I had to go back to 5! (until I can overcome the diskspace-shortage). Could one prevent amanda from promoting fulldumps? (like only one fulldump in a cycle, even thoug the tape is nearly emtpy? Cheers Urs As far as purging old history in the indexes and such, amanda does that automaticly, removing that which would refer to what was on a tape that has been re-written, therefore rendering that data moot. Bitte keine Antwort an diese Mailadresse. Wird nicht gelesen. Don't reply to this address.
Re: amoverview; history database
Urs Forster wrote: Ok, I deletet all indexes, all curinfo, removed all extra tapes from changer.conf, ran amrmtape, amtape update, amcheckdb and I found out what fell swoop means (rather than swell foop; that was the harder part ;-). Despite all of those, amoverview still shows around 90 days across. Any more ideas? Did you also clean out the holdingdisk directory? I believe a command like: amadmin YourConfig find --sort d | head will quickly show which entry is around 90 days old. Probably something left in your holdingdisk. I'm doing backup to disk (tapeless). In order to fit the largest filesystem I had to define the 'tape'-size to be around 3 Gb. Now, amanda seems to be a bit greedy - meaning it tries to fill every tape (by promoting full dumps). Since all 'tapes' lie on the same disk, I ran into space problems. Therefore I had to go back to 5! (until I can overcome the diskspace-shortage). Could one prevent amanda from promoting fulldumps? (like only one fulldump in a cycle, even thoug the tape is nearly emtpy? For promoting full dumps, amanda does not look at the tapesize (except to see if it will fit). Amanda tries to level out the amount of full dumps over the runs in a tapecycles. The command amadmin YourConfig balance will tell you how much big the full dumps are in total, and how much amanda will do each run. From one of my configs: $ amadmin daily balance due-date #fsorig KB out KB balance -- 3/29 Mon 35 52076537 21884417-13.0% 3/30 Tue 47 65993395 25774163 +2.5% 3/31 Wed 26 45819482 25694830 +2.2% 4/01 Thu 17 53597714 27243524 +8.3% 4/02 Fri0 0 0 --- 4/03 Sat0 0 0 --- 4/04 Sun0 0 0 --- -- TOTAL 126 217487722 100597534 25149383 DISTINCT 123 217485940 100595734 There is about 100 Gbyte of data (after compression) to be spread over 4 runs in a week, giving about 25 Gbyte each run. (The fact that on monday, there was 13% less, was a result of a failed computer.) Amanda tries to level out the full dumps so that each run is about the same size, i.e. 25149383 Kbytes. What is not run as full dump is done with an incremental level, which has his own method (bumpsize, bumpdays, etc) to tune. If the tape is too small, amanda will delay full dumps, but if the tape has plenty of room left, amanda will not promote dumps just because. If the balance is good enough, there will be no promotions. Conclusion: there must be some other reason than changing the tape-length. If the tapes are filled around 100% each day, then you probably configured amanda with a tapecycle too low for that tape-capacity. In that case, amanda tries desperately to find her balance, by promoting and delaying the full dumps, but she will never succeed completely. Bitte keine Antwort an diese Mailadresse. Wird nicht gelesen. Don't reply to this address. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
amoverview; history database
Hi When using amoverview I get a wide output (more than 3 month). This is not readable and anyway the data is obsolete, I only work on a cycle of 5 days. How can I purge old data from the history? Cheers Urs
Re: amoverview; history database
Urs Forster wrote: When using amoverview I get a wide output (more than 3 month). This is not readable and anyway the data is obsolete, I only work on a cycle of 5 days. This is an indication that you do have somewhere some backup that dates that long ago. Probably on the holdingdisk or so. You can find out which one: amadmin ConFig find | sort | head How can I purge old data from the history? If you find out that that tape or holdingdisk file is really not available, you could do: amadmin Config delete hostname diskname but this deletes ALL the information about that host/disk (and if the disk is still in the disklist file, the disk will get a level 0 backup next time!) If it is only one specific entry that you want to delete you could do some careful surgery on the curinfo files: ~amanda/ConFig/curinfo/host/_disk_name/info they are plain text files, so you can delete the stats line that you want to get rid of. (the stats line is the line that shows on which tape/holdingdiskfile the backup is). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview; history database
On Thursday 25 March 2004 08:14, Urs Forster wrote: Hi When using amoverview I get a wide output (more than 3 month). This is not readable and anyway the data is obsolete, I only work on a cycle of 5 days. How can I purge old data from the history? Cheers Urs Good question perhaps. Here, its quite wide, but the dates coincide with the number of tapes in my tapecycle of 28. That seems to be a reasonable display. What is your tapecycle set to? As far as purging old history in the indexes and such, amanda does that automaticly, removing that which would refer to what was on a tape that has been re-written, therefore rendering that data moot. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amoverview; history database
Hi From: Gene Heskett [EMAIL PROTECTED] Date: Thu, 25 Mar 2004 09:58:16 -0500 On Thursday 25 March 2004 08:14, Urs Forster wrote: Hi When using amoverview I get a wide output (more than 3 month). This is not readable and anyway the data is obsolete, I only work on a cycle of 5 days. How can I purge old data from the history? Cheers Urs Good question perhaps. Here, its quite wide, but the dates coincide with the number of tapes in my tapecycle of 28. That seems to be a reasonable display. What is your tapecycle set to? I think thats the point. Now it's 5, but it used to be that high! Somwhere amanda remembers the higher number, but where? As far as purging old history in the indexes and such, amanda does that automaticly, removing that which would refer to what was on a tape that has been re-written, therefore rendering that data moot. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved. Bitte keine Antwort an diese Mailadresse. Wird nicht gelesen. Don't reply to this address.
Re: amoverview; history database
Urs Forster wrote: From: Gene Heskett [EMAIL PROTECTED] Date: Thu, 25 Mar 2004 09:58:16 -0500 On Thursday 25 March 2004 08:14, Urs Forster wrote: When using amoverview I get a wide output (more than 3 month). This is not readable and anyway the data is obsolete, I only work on a cycle of 5 days. How can I purge old data from the history? Good question perhaps. Here, its quite wide, but the dates coincide with the number of tapes in my tapecycle of 28. That seems to be a reasonable display. What is your tapecycle set to? I think thats the point. Now it's 5, but it used to be that high! Somwhere amanda remembers the higher number, but where? In ~amanda/ConFig/curinfo/hostname/_disk_name/info To be manipulated with amadmin ConFig Delete to delete the entire info for that host/disk or to by editing the info file directly. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview; history database
On Thursday 25 March 2004 10:57, Urs Forster wrote: Hi From: Gene Heskett [EMAIL PROTECTED] Date: Thu, 25 Mar 2004 09:58:16 -0500 On Thursday 25 March 2004 08:14, Urs Forster wrote: Hi When using amoverview I get a wide output (more than 3 month). This is not readable and anyway the data is obsolete, I only work on a cycle of 5 days. How can I purge old data from the history? Cheers Urs Good question perhaps. Here, its quite wide, but the dates coincide with the number of tapes in my tapecycle of 28. That seems to be a reasonable display. What is your tapecycle set to? I think thats the point. Now it's 5, but it used to be that high! Somwhere amanda remembers the higher number, but where? If you changed it in one swell foop, that which would have been bypassed is still there, it only deletes that which references the tape(s) just re-written. I don't think there is a problem in that case of you going into the index and currinfo dirs and doing a bit of obviously overdue housekeeping. But why down to 5? One really should have a tapecycle thats at least 2*runtapes*runspercycle in order to have at least the 2 most recent full backups on hand at any one time. Anything less and you're playing russian roulette with a Morgolin Target Pistol as far as your data's safety is concerned... YMMV of course. :) As far as purging old history in the indexes and such, amanda does that automaticly, removing that which would refer to what was on a tape that has been re-written, therefore rendering that data moot. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved. Bitte keine Antwort an diese Mailadresse. Wird nicht gelesen. Don't reply to this address. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
amoverview trouble
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, When I use amoverview tool on one server, it displays dates since november : 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 12 12 ~ 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 01 01 01 01 01 01 01 0 1 01 01 01 01 01 01 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 01 02 ~ 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 01 02 03 04 05 06 07 0 8 09 10 11 12 13 14 And it displays dump level of the 6th and 7th of november. 1 1 ~ 1 0 1 1 0 1 1 1 1 1 0 Here are they some parameters of my amanda.conf file : dumpcycle 11 days runspercycle 4 tapecycle 15 tapes runtapes 3 Why does amoverview work like that ? - -- Cordialement, Sincerely, Christian MOLIERE Tél : 01.43.60.11.60 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFABmcSZ30NRCZKZ48RAvQAAKCKByuW7eKFirptZhO+itYVC/kghwCeL32U wxaSS67BDttItcyZrLoq8xQ= =p0I7 -END PGP SIGNATURE-
Re: amoverview trouble
Christian Molière wrote: When I use amoverview tool on one server, it displays dates since november : ... And it displays dump level of the 6th and 7th of november. ... Here are they some parameters of my amanda.conf file : dumpcycle 11 days runspercycle 4 tapecycle 15 tapes runtapes 3 Why does amoverview work like that ? Maybe because there are some images on the holdingdisk and never got flushed to tape? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview trouble
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Bijnens wrote: | Christian Molière wrote: | | When I use amoverview tool on one server, it displays dates since november : | | ... | | And it displays dump level of the 6th and 7th of november. | | ... | | Here are they some parameters of my amanda.conf file : | dumpcycle 11 days | runspercycle 4 | tapecycle 15 tapes | runtapes 3 | | Why does amoverview work like that ? | | | Maybe because there are some images on the holdingdisk | and never got flushed to tape? | | No there aren't, I have already checked it. - -- Cordialement, Sincerely, Christian MOLIERE Tél : 01.43.60.11.60 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFABn36Z30NRCZKZ48RAqQCAJdOPKT1tq0x0YJTV0zYumm8/EoCAKCba+u8 jgTx3K/SVWzTbvTr8Rjblg== =3cQG -END PGP SIGNATURE-
Re: amoverview trouble
Christian Molière wrote: | Maybe because there are some images on the holdingdisk | and never got flushed to tape? | No there aren't, I have already checked it. amoverview gets it's data from the command: amadmin ConFig find | ... What has that command to say about those entries? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview trouble
Christian Molière wrote: |amadmin ConFig find | ... | | What has that command to say about those entries? | Here it is result: date host disk lv tape or file file status 2003-11-06 carte-mailer /etc/postfix 1 TAPE_1619 OK 2003-11-07 carte-mailer /etc/postfix 1 TAPE_1719 OK ... So you do have actually 17 tapes. From the previous mail: Here are they some parameters of my amanda.conf file : dumpcycle 11 days runspercycle 4 tapecycle 15 tapes runtapes 3 The tapecycle instructs to amanda that it will cycle through _at_least_ 15 tapes. You may always feed more tapes. You seem to have 17. My archive config has a tapecycle of 12, but I have about 70 tapes already, the oldest dating from 1999. Most of them are marked no-reuse because they are archived, so amanda won't even ask for them. But they do exist. (yes, my amoverview archive is quite wide, currently 4463 columns; too wide to show on screen, or even on A3-landscape in point 6.) If those tapes are lost or damaged, you may forget about them with the command amrmtape ConFig TAPE_16. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview trouble
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Bijnens wrote: | Christian Molière wrote: | | |amadmin ConFig find | ... | | | | What has that command to say about those entries? | | | Here it is result: | | date host disk lv tape or file file status | 2003-11-06 carte-mailer /etc/postfix 1 TAPE_1619 OK | 2003-11-07 carte-mailer /etc/postfix 1 TAPE_1719 OK | | ... | | So you do have actually 17 tapes. Yes I do | | From the previous mail: | | Here are they some parameters of my amanda.conf file : | dumpcycle 11 days | runspercycle 4 | tapecycle 15 tapes | runtapes 3 | | | The tapecycle instructs to amanda that it will cycle through _at_least_ 15 tapes. You may always feed more tapes. You seem | to have 17. | My archive config has a tapecycle of 12, but I have about 70 tapes | already, the oldest dating from 1999. Most of them are marked | no-reuse because they are archived, so amanda won't even ask for | them. But they do exist. | (yes, my amoverview archive is quite wide, currently 4463 columns; | too wide to show on screen, or even on A3-landscape in point 6.) | | If those tapes are lost or damaged, you may forget about them | with the command amrmtape ConFig TAPE_16. | I'd like to use again the two missing tapes. Is it just to set tapecycle to 17 in amanda.conf file ? - -- Cordialement, Sincerely, Christian MOLIERE Tél : 01.43.60.11.60 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFABpU9Z30NRCZKZ48RAlh8AKC4gv+JINolq9FT0o6wKvoBCuskqwCgsR7X b1eEcfuNRf+r/LwYGGVjOYI= =M5gl -END PGP SIGNATURE-
Re: amoverview trouble
Christian Molière wrote: I'd like to use again the two missing tapes. Is it just to set tapecycle to 17 in amanda.conf file ? If you set it to 17 amanda will immediately ask for those, and insist on those tapes. Probably this will bring the numbering out of order. You may also just feed TAPE_16 after TAPE_15, even when amanda asks for TAPE_01 (unless they were marked no-reuse). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amoverview trouble
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for your help, I'll have results tomorrow morning. Paul Bijnens wrote: | Christian Molière wrote: | | I'd like to use again the two missing tapes. Is it just to set tapecycle to 17 in amanda.conf file ? | | | If you set it to 17 amanda will immediately ask for those, and insist | on those tapes. Probably this will bring the numbering out of order. | You may also just feed TAPE_16 after TAPE_15, even when amanda asks | for TAPE_01 (unless they were marked no-reuse). | | - -- Cordialement, Sincerely, Christian MOLIERE Tél : 01.43.60.11.60 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFABpvVZ30NRCZKZ48RAoo4AJ47bxoro6JfFwO0KS3/X+9w/3cjMgCgj+tX T63HPNty6eGaIN7wCLIVaQU= =doJO -END PGP SIGNATURE-
amoverview output
Attached are my amoverview and disklist files. I see some { brackets,
include
statements etc., in my amoverview output. These were not there before I
introduced include,exclude in the disklist file. Amreports everything fine
for
all in the disklists though.
Any idea?
Rohit
# localhost /etc comp-root-tar
machine1 /vl tar-low
machine1 /vw tar-high
machine1 /vm tar-high
machine1 /htar-low
machine3 /rp cvs-backup-full -1 local
machine3 /vw tar-low
machine3 /vm tar-low
machine3 /hAM /h {
tar-low
include ./[a-m]*
} -1 local
machine3 /hNZ /h {
tar-low
include ./[n-z]*
} -1 local
machine2 /vmtar-low
machine2 /vwtar-med
machine2 /hAM /h {
tar-med
include ./[a-m]*
} 1
machine2 /hNZ /h {
tar-med
include ./[n-z]*
} 1
machine2 /h2AM /h2 {
tar-med
include ./[a-m]*
} 1
machine2 /h2NZ /h2 {
tar-med
include ./[n-z]*
} 1
machine2 /h3NZ /h3 {
tar-med
include ./rohit
} 1
# machine2/vl tar-low
# machine2 //meosis/users windows-high
# machine2 //meosis/UsersG2 windows-high
# machine2 //meosis/UsersG3 windows-high
date 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
host disk 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
machine1 /h0 E E E E1 2 2 2 2 E 0
machine1 /vl E 0 E E EE 0 1 0 1 E 1 0 1
machine1 /vm 0 1 1 0 00 1 0 1 1 1 1 0 1
machine1 /vw E 0 E 1 22 0 1 0 1 1 1 1 1
machine2 /h2AM 0 1 1
machine2 /h2NZ 0 1 1
machine2 /h3NZ
machine2 /hAM 0 1 1
machine2 /hNZ 0 1 1
machine2 /vm
machine2 /vw E E 0 E1 1 0 1 1 2 0 1
include ./[a-m]*
include ./[n-z]*
include ./rohit
machine3/hAM 0
machine3/hNZ 0
machine3/rp0
machine3/vm
machine3/vw
tar-low
tar-med
}-1
}1
Re: amoverview output
Hi Rohit,
Could you try this patch
Jean-Louis
On Thu, Oct 23, 2003 at 07:00:56PM +0530, Rohit Peyyeti wrote:
Attached are my amoverview and disklist files. I see some { brackets,
include
statements etc., in my amoverview output. These were not there before I
introduced include,exclude in the disklist file. Amreports everything fine
for
all in the disklists though.
Any idea?
Rohit
# localhost /etc comp-root-tar
machine1 /vl tar-low
machine1 /vw tar-high
machine1 /vm tar-high
machine1 /htar-low
machine3 /rp cvs-backup-full -1 local
machine3 /vw tar-low
machine3 /vm tar-low
machine3 /hAM /h {
tar-low
include ./[a-m]*
} -1 local
machine3 /hNZ /h {
tar-low
include ./[n-z]*
} -1 local
machine2 /vmtar-low
machine2 /vwtar-med
machine2 /hAM /h {
tar-med
include ./[a-m]*
} 1
machine2 /hNZ /h {
tar-med
include ./[n-z]*
} 1
machine2 /h2AM /h2 {
tar-med
include ./[a-m]*
} 1
machine2 /h2NZ /h2 {
tar-med
include ./[n-z]*
} 1
machine2 /h3NZ /h3 {
tar-med
include ./rohit
} 1
# machine2/vl tar-low
# machine2 //meosis/users windows-high
# machine2 //meosis/UsersG2 windows-high
# machine2 //meosis/UsersG3 windows-high
date 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
host disk 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
machine1 /h0 E E E E1 2 2 2 2 E 0
machine1 /vl E 0 E E EE 0 1 0 1 E 1 0 1
machine1 /vm 0 1 1 0 00 1 0 1 1 1 1 0 1
machine1 /vw E 0 E 1 22 0 1 0 1 1 1 1 1
machine2 /h2AM 0 1 1
machine2 /h2NZ 0 1 1
machine2 /h3NZ
machine2 /hAM 0 1 1
machine2 /hNZ 0 1 1
machine2 /vm
machine2 /vw E E 0 E1 1 0 1 1 2 0 1
include ./[a-m]*
include ./[n-z]*
include ./rohit
machine3/hAM 0
machine3/hNZ 0
machine3/rp0
machine3/vm
machine3/vw
tar-low
tar-med
}-1
}1
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Département IRO, Université de Montréal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montréal, Canada, H3C 3J7Fax: (514) 343-5834
--- amanda-2.4.4p1.orig/server-src/amadmin.c2003-01-03 22:35:54.0 -0500
+++ amanda-2.4.4p1.new/server-src/amadmin.c 2003-10-23 09:44:08.0 -0400
@@ -1454,7 +1454,7 @@
ip-name[0] ? ip-name : default);
printf(disk %s:\n, dp-name);
-if(dp-device) printf(device: %s\n, dp-device);
+if(dp-device) printf(device %s\n, dp-device);
printf(program \%s\\n, dp-program);
if(dp-exclude_file != NULL dp-exclude_file-nb_element 0) {
Re: amoverview output
Thanks Jean, but I have a binary RPM version installed on my
tape server. I'll download sources and try this later later.
Thanks again.
- Original Message -
From: Jean-Louis Martineau [EMAIL PROTECTED]
To: Rohit Peyyeti [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 7:40 PM
Subject: Re: amoverview output
Hi Rohit,
Could you try this patch
Jean-Louis
On Thu, Oct 23, 2003 at 07:00:56PM +0530, Rohit Peyyeti wrote:
Attached are my amoverview and disklist files. I see some { brackets,
include
statements etc., in my amoverview output. These were not there before I
introduced include,exclude in the disklist file. Amreports everything
fine
for
all in the disklists though.
Any idea?
Rohit
# localhost /etc comp-root-tar
machine1 /vl tar-low
machine1 /vw tar-high
machine1 /vm tar-high
machine1 /htar-low
machine3 /rp cvs-backup-full -1 local
machine3 /vw tar-low
machine3 /vm tar-low
machine3 /hAM /h {
tar-low
include ./[a-m]*
} -1 local
machine3 /hNZ /h {
tar-low
include ./[n-z]*
} -1 local
machine2 /vmtar-low
machine2 /vwtar-med
machine2 /hAM /h {
tar-med
include ./[a-m]*
} 1
machine2 /hNZ /h {
tar-med
include ./[n-z]*
} 1
machine2 /h2AM /h2 {
tar-med
include ./[a-m]*
} 1
machine2 /h2NZ /h2 {
tar-med
include ./[n-z]*
} 1
machine2 /h3NZ /h3 {
tar-med
include ./rohit
} 1
# machine2/vl tar-low
# machine2 //meosis/users windows-high
# machine2 //meosis/UsersG2 windows-high
# machine2 //meosis/UsersG3 windows-high
date 10 10 10 10 10 10 10 10 10 10 10 10 10 10
10 10 10
host disk 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23
machine1 /h0 E E E E1 2 2 2 2 E
0
machine1 /vl E 0 E E EE 0 1 0 1 E
1 0 1
machine1 /vm 0 1 1 0 00 1 0 1 1 1
1 0 1
machine1 /vw E 0 E 1 22 0 1 0 1 1
1 1 1
machine2 /h2AM
0 1 1
machine2 /h2NZ
0 1 1
machine2 /h3NZ
machine2 /hAM
0 1 1
machine2 /hNZ
0 1 1
machine2 /vm
machine2 /vw E E 0 E1 1 0 1 1 2
0 1
include ./[a-m]*
include ./[n-z]*
include ./rohit
machine3/hAM
0
machine3/hNZ
0
machine3/rp
0
machine3/vm
machine3/vw
tar-low
tar-med
}-1
}1
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Dpartement IRO, Universit de Montral
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montral, Canada, H3C 3J7Fax: (514) 343-5834
Re: amoverview bug?
Mathias Koerber wrote: Is this bug known or due to something wrong in my setup? amoverview not only lists my DLEs but also some other lines from the disklist file. My guess is that this is due to amoverview not being in sync with the new disklist format yet??? can someone confirm? Yes, it's a bug. in Line 87 we find: ($host, $disk, $type, $spindle) = split ' ', $_; but the syntax of a DLE has been extended since. It is now: hostname diskname [ diskdevice ] dumptype [ spindle [ interface ] ] and dumptype can be defined inline by enclosing it in curly braces and spans multiple lines. Ugh. Not easy to parse with a perl one liner. It's probably better to parse the output of amadmin ConFig disklist, instead of parsing the disklist file itself. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
amoverview bug?
Is this bug known or due to something wrong in my setup? amoverview not only lists my DLEs but also some other lines from the disklist file. My guess is that this is due to amoverview not being in sync with the new disklist format yet??? can someone confirm? should amoverview not also honour the ColumnSpec settings for those columns it outputs? $ amoverview Daily date 05 05 05 05 host disk 25 26 27 28 comp-hig comp-roo comp-use exclude ./home* exclude ./public exclude list include list localhos /boot 0 0 1 localhos /home 0 0 1 localhos /root 0 0 1 localhos /usr 0 1 1 localhos Imap 0 1 1 localhos ShareNonPublic0 1 1 localhos SharePublic 0 0 1 localhos VarOther 0 0 1 }1 }2 }3 }4 }5 Mathias Körber [EMAIL PROTECTED]
Small bug in amoverview
I found a little bug in amoverview. I curently have a couple of days dumps in the holding directory and when I ran amoverview I get: amanda@moca:~ amoverview TIZ bad date 20020418: in 20020418: found Amanda directory. bad date 20020420: in 20020420: found Amanda directory. date 04 04 04 04 04 host disk 16 17 18 19 20 A tiny bit of research showed that this was related to the output from amadmin find which beginss: amanda@moca:~ amadmin TIZ find Scanning /data/amandahold... 20020418: found Amanda directory. 20020420: found Amanda directory. date host disk lv tape or file file status 2002-04-16 moca / 0 TIZdaily01 3 OK 2002-04-18 moca / 1 /data/amandahold/20020418/moca._.1 0 OK amoverview parses the output of amadmin find and doesn't handle the found Amanda directory lines. The fix is so trivial that I'm just mentioning it inline here because that's actually smaller than the patch :-) After next if $date eq ; insert an extra line next if $host eq found; I don't know if that's the best solution - another solution is next if $date =~ /:$/; Anyway, I've patched my amoverview, and perhaps the maintainer of amoverview can either take my patch on board or do something else appropriate. Regards, Niall O Broin
Re: Small bug in amoverview
amoverview parses the output of amadmin find and doesn't handle the found Amanda directory lines. The fix is so trivial that I'm just mentioning it inline here because that's actually smaller than the patch :-) After Thanks for the fix.
amoverview
hello, After doing a start backup, of many filesystem, I run amoverview to check the state of the backup, every filesystem is 0 except two of them (the two that failed first write cause of tape space and were successful on second try) that are with EE code. Whats the meaning of that? Is that correct? In amdump.log seems its everything ok.
Re: Build dies trying to make amoverview
I am attempting to make amanda 2.4.2p2 on a NetBSD 1.5_ALPHA system The make dies with the following message: cat amcheckdb.sh amcheckdb chmod a+x amcheckdb cat amcleanup.sh amcleanup chmod a+x amcleanup cat amdump.sh amdump chmod a+x amdump make: don't know how to make amoverview. Stop *** Error code 1 Use GNU make (gmake)
Build dies trying to make amoverview
I am attempting to make amanda 242p2 on a NetBSD 15_ALPHA system The make dies with the following message: cat amcheckdbsh amcheckdb chmod a+x amcheckdb cat amcleanupsh amcleanup chmod a+x amcleanup cat amdumpsh amdump chmod a+x amdump make: don't know how to make amoverview Stop *** Error code 1 I googled, and discovered that this is fixed in the pkgsrc for amanda, but I can't use the pkgsrc because I need to build amanda with kerberos Any idea what I need to make this work, or how I can not build amoverview, as I am unlikely to use it? Thanks for any help, --Ruth Anne
Problem with amoverview: Bad interpreter?
I just noticed a problem this morning. When I run amoverview, I get: amanda@admin:~ amoverview DailySet1 bash: /usr/local/sbin/amoverview: bad interpreter: No such file or directory amanda@admin:~ I could have sworn I've run amoverview on this system before without problems. The listing doesn't seem to indicate that anything has changed with the file: -rwxr-xr-x1 amanda disk 4351 Jan 4 11:21 /usr/local/sbin/amoverview However, amcheck seems to work fine: amanda@admin:~ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/amanda: 5664532 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet106 label ok Server check took 20.453 seconds Amanda Backup Client Hosts Check Client check: 5 hosts checked in 0.065 seconds, 0 problems found (brought to you by Amanda 2.4.3b1) amanda@admin:~ I also got what looks like a normal backup off the system last night. I searched the archives for interpreter but got no hits. Anyone seen this problem before? Any suggestions for fixing it? Thanks for your thoughts and time. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Problem with amoverview: Bad interpreter?
KEVIN ZEMBOWER wrote: I just noticed a problem this morning. When I run amoverview, I get: amanda@admin:~ amoverview DailySet1 bash: /usr/local/sbin/amoverview: bad interpreter: No such file or directory Somebody moved perl to another place, or simply renamed it (or removed it?) See the first line in amoverview. It looks like: #!/bin/perl at me, and it should point to the perl executable. -- Paul Bijnens, Lant Tel +32 16 40.51.40 Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 http://www.lant.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Problem with amoverview: Bad interpreter?
Thank you so much, Paul. Yes, it was that simple. I did change a symlink for perl, but I just didn't realize that amoverview was a perl program until I looked at it. Thanks for your help. -Kevin Zembower Paul Bijnens [EMAIL PROTECTED] 01/24/02 10:40AM KEVIN ZEMBOWER wrote: I just noticed a problem this morning. When I run amoverview, I get: amanda@admin:~ amoverview DailySet1 bash: /usr/local/sbin/amoverview: bad interpreter: No such file or directory Somebody moved perl to another place, or simply renamed it (or removed it?) See the first line in amoverview. It looks like: #!/bin/perl at me, and it should point to the perl executable. -- Paul Bijnens, Lant Tel +32 16 40.51.40 Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 http://www.lant.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Amanda fails to build: amoverview
I just got around to installing Amanda-2.4.2 stable unfortunately I can't get it to build on FreeBSD 4.11. The following error is reported: make: don't know how to make amoverview. Stop *** Error code 1 Any help would be appreciated Best regards Rod
Re: Amanda fails to build: amoverview
From: "ROD" [EMAIL PROTECTED] Date: Tue, 19 Dec 2000 15:36:31 - I just got around to installing Amanda-2.4.2 stable unfortunately I can't get it to build on FreeBSD 4.11. The following error is reported: make: don't know how to make amoverview. Stop *** Error code 1 Any help would be appreciated Please see http://www.egroups.com/message/amanda-hackers/2333 (and following thread). (Summary: yes; appears to be a problem with FreeBSD make; see http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23328 for that part. A circumvention is to hack the Makefiles; another is to use gmake.) Cheers, david -- David Wolfskill [EMAIL PROTECTED] UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823
Re: make fails: don't know how to make amoverview
Installing amanda-2.4.2-20001025-beta2.tar.gz like this: ... results in: make: don't know how to make amoverview. Stop There was a problem with that beta release. As I recall, using GNU make should get around it. Eric Wadsworth John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
