On 2008-02-14 09:56, Theodotos Andreou wrote:
Since a month ago I have the following problem appearing:

When amdump is completed amreport takes long to complete. When it finally finishes it won't send any mail. Running amreport manually results in a mail with subject:

It takes so long because the dump file contains lots of
"strange" lines probably.  "Strange" = not expected in the normal
output of tar:  Amanda collects those messages, prepends a '?' to
it and displays them in the mailreport.  Amanda then leaves it up
to you to decide if that is bad, or harmless.

Because there are so many lines, generating the report takes very
long.  And probably when sending the mail, it is refused by the
mailserver because the message is too large.
If it happens to be a full dump with many files, then the mail
was too large; when it contains only an incremental dump, it is
not that large, and you get the report.




Org DailyJob AMANDA MAIL REPORT FOR BogusMonth 0, 0

and body:

*** THE DUMPS DID NOT FINISH PROPERLY!

even though amstatus reports that all is OK. I even verified that the images are present with amrestore.

Yes, but are all the images intact, and do they contain all the
data that was on the disk?  Some DLE at least flagged as "not
good enough".  Or maybe the filesystem containing the amdump.XX log
file was full resulting in amreport not finding the normal log lines
indicating a good backup.



It is also peculiar that the problem is intermittent, It happens most of the time but not always. I was not able to figure out what triggers it.

I am using amanda 2.5.0p2 on CentOS 5.

I tried to strace on the running amreport and I got some strange results:

read(3, "Warning: Cannot fgetfilecon: No data available\n ? gtar: ./ionc/environment/3.4.old/kreatel/adk/mipsel-kreatel-linux-gnu/mozilla/include/uriloader/nsDocLoader.h: Warning: Cannot fgetfilecon: No data available\n ? gtar:

Is this maybe related to:

https://bugzilla.redhat.com/431879

Did you recently upgraded tar, which generates a warning for each
file where se_linux context is not defined?



--
Paul Bijnens, xplanation Technology Services        Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +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          *
***********************************************************************

Reply via email to