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/aman
On Tue, Sep 14, 2010 at 8:16 AM, McGraw, Robert P 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 WARNI
tialized 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
ious 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/sbi
at 3:27 PM, Jon LaBadie 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 surpris
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 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
On Mon, Sep 13, 2010 at 1:44 PM, McGraw, Robert P 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 Sourc
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]
g
> Subject: Re: amoverview under 3.1.2
>
> Dustin J. Mitchell wrote:
> > On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau
> > wrote:
> >
> >> Robert, can you try the attached patch?
> >>
> >
> > (only the amoverview hunk is required, right
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/amo
Dustin J. Mitchell wrote:
On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau
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
On Mon, Sep 13, 2010 at 11:04 AM, Jean-Louis Martineau
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
On Mon, Sep 13, 2010 at 10:23 AM, McGraw, Robert P 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 s
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
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
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
On Fri, Aug 6, 2010 at 8:58 AM, McGraw, Robert P 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/zm
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 System
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
&#x
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 yo
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
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
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
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
-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
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 blo
nt /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/processe
ction 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
;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
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
-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
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'
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
>
>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
>>>
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
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 cycl
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 i
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 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
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
-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 i
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
fig 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 4
sk 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 ConF
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
-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 para
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
-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
c: <[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 disklis
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 inc
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
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
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
> 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.
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.
d
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
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)
Thanks, it worked!
--Ruth Anne
mdump
> make: don't know how to make amoverview. Stop
> *** Error code 1
Use GNU make (gmake)
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 am
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
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.
>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 amov
ROD-
If I remember the previous discussion properly, Amanda seems to tickle a bug
in the FreeBSD "make" program. You might try again with GNU make (installed
as /usr/local/bin/gmake or available in the ports as devel/gmake).
-Ben
--
Benjamin LewisThank goodness modern
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
>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 Softwar
make amoverview. Stop
*** Error code 1
What is wrong?
===
Eric Wadsworthemail: [EMAIL PROTECTED]
Conceptual Systems and Software http://www.consys.com
===
On Nov 9, 2000, Eric Wadsworth <[EMAIL PROTECTED]> wrote:
> Before I start tearing into stuff, I thought I'd check to see if this were a
> known problem.
It is. We're probably using some non-portable construct in the
Makefile. It works with GNU make.
--
Alexandre Oliva Enjoy Guarana', see
Before I start tearing into stuff, I thought I'd check to see if this were a
known problem. This is amanda beta 2.
===
Eric Wadsworthemail: [EMAIL PROTECTED]
Conceptual Systems and Software http://www.consys.com
69 matches
Mail list logo
