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, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* 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 *
***********************************************************************
|
