Frank Smith wrote:
Well, I stand corrected (and learned something in the process). I
was going to make a comment about this behavior not being adequately
documented, but it looks like it is, although in the dumperapi.txt
file, which I had never looked at. There is a mention of the '?' in
This time I've got a really strange error message from an amanda back-
up:
FAILURE AND STRANGE DUMP SUMMARY:
epo.dk /var lev 0 STRANGE
.. and further down the list:
FAILED AND STRANGE DUMP DETAILS:
/-- epo.dk /var lev 0 STRANGE
sendbackup: start [epo.dk:/var level 0]
sendbackup: info
Erik P. Olsen wrote:
| gtar: ./cache/samba/winbindd_privileged/pipe: socket ignored
? gtar: ./lib/slocate/slocate.db: file changed as we read it
| Total bytes written: 545894400 (521MiB, 3.1MiB/s)
sendbackup: size 533100
sendbackup: end
\
The weird messages do not make any sense
Erik P. Olsen wrote:
This time I've got a really strange error message from an amanda back-
up:
FAILURE AND STRANGE DUMP SUMMARY:
epo.dk /var lev 0 STRANGE
STRANGE means Amanda received unexpected output from the underlying
backup program (tar or dump). Whether or not it is something
Frank Smith wrote:
Erik P. Olsen wrote:
This time I've got a really strange error message from an amanda back-
up:
FAILURE AND STRANGE DUMP SUMMARY:
epo.dk /var lev 0 STRANGE
STRANGE means Amanda received unexpected output from the underlying
backup program (tar or dump). Whether or
On Tue, 2005-11-08 at 22:26 +0100, Paul Bijnens wrote:
? gtar: ./lib/slocate/slocate.db: file changed as we read it
This is the strange line. It is not an error. It is up to you
to decide if it is bad or not.
Thanks for shedding light in the darkness.
--
Regards,
Erik P. Olsen
On Tue, Nov 08, 2005 at 10:26:07PM +0100, Paul Bijnens wrote:
| gtar: ./cache/samba/winbindd_privileged/pipe: socket ignored
Tar is warning you that it came across a special file type (a socket)
and didn't back it up. You can safely ignore these messages.
Not 100% true actually.
Paul Bijnens wrote:
Not 100% true actually. Gnutar produces some output on stderr which
amanda classifies as normal (can safely be ignored), error (needs
to be flagged as error to the user, and implies that this dump is not
correct and will not be put on tape if dumping to holdingdisk).
And
