Dump gives a strange dump summary if file system is not mounted - is this
required or a bug ?
To illustrate in my disk list:
tx5019 /mnt /dev/lofi/2 comp-root
STRANGE DUMP DETAILS:
/-- tx5019 /mnt lev 1 STRANGE
sendbackup: start [tx5019:/mnt level 1]
sendbackup: info BACKUP=/usr/sbin
daily, i get this email message:
Hostname: myserver.mydomain.com
Org : localhost
Config : daily
Date: August 16, 2007
These dumps were to tape daily5.
The next tape Amanda expects to use is: daily6.
FAILURE AND STRANGE DUMP SUMMARY:
myclient.mydomain.com /Users/amanda/sync lev 0
On 2007-06-18 20:53, Robert Echlin wrote:
FAILURE AND STRANGE DUMP SUMMARY:
cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset
by peer]
Have you read/understood/checked:
http://wiki.zmanda.com/index.php/Mesg_read:_Connection_reset_by_peer
cpu.ind.com /var/lib/mysql
FAILURE AND STRANGE DUMP SUMMARY:
cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by
peer]
Means that Amanda client on cpu.ind.com closed connection with Amanda
server before the dump (or estimate was finished).
Olivier
Hi,
fedora schrieb:
cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by
peer]
Maybe the client was rebooted during the backup or xinetd restarted.
cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0
instead of 32768]
The server didn't send an
Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78
http://www.medizinische-genetik.de
--
View this message in context:
http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY
FAILURE AND STRANGE DUMP SUMMARY:
cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset
by peer]
cpu.ind.com /var/lib/mysql lev 0 FAILED [cannot read header: got 0
instead of 32768]
cpu.ind.com /var/lib/mysql lev 0 was successfully retried
Olivier notes that the network
fedora wrote:
Hi guys. I am newbie here. I got problem with my Amanda.
here is the result in mail report:
FAILURE AND STRANGE DUMP SUMMARY:
ind.ayo.com/var/lib/mysql lev 0 STRANGE
STATISTICS: All OK. Showed the progress
FAILED AND STRANGE DUMP DETAILS
not have such a file. Is it
important or not if you loose it? If it is only a log file, like the
name suggests, maybe loosing it would not be so dramatic.
Best regards,
Olivier
--
View this message in context:
http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11056985
fedora wrote:
Almost files which is the extension ./databasename/*.MYI changed not only
./mysql/general_log.CSV
Of course they changed.
I usually try to avoid Read the documentation type responses, but I
think this might be a good time to suggest it. The mysql docs tell you
pretty clearly
any solutions for me?
fedora wrote:
Hi guys. I am newbie here. I got problem with my Amanda.
here is the result in mail report:
FAILURE AND STRANGE DUMP SUMMARY:
ind.ayo.com/var/lib/mysql lev 0 STRANGE
STATISTICS: All OK. Showed the progress
FAILED AND STRANGE
FAILED AND STRANGE DUMP DETAILS:
/-- ind.ayo.com /var/lib/mysql lev 0 STRANGE
sendbackup: start [ind.ayo.com:/var/lib/mysql level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ...
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
|
://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a11022275
Sent from the Amanda - Users mailing list archive at Nabble.com.
Hi,
fedora schrieb:
Is there any proper mysql backup that can backup database without stopping
it??
If so, I don't have to worry about it? Of course it wasn't failed but I just
worried if I recover it and the database or tables might be corrupt just
because Amanda detected strange. Please
Is there any proper mysql backup that can backup database without stopping
it??
If so, I don't have to worry about it? Of course it wasn't failed but I just
worried if I recover it and the database or tables might be corrupt just
because Amanda detected strange. Please advice.
I remember I
On Jun 8, 2007, at 1:15 AM, fedora wrote:
Is there any proper mysql backup that can backup database without
stopping
it??
If so, I don't have to worry about it? Of course it wasn't failed
but I just
worried if I recover it and the database or tables might be corrupt
just
because
We use the following script (via a cron job) to get a distinct file for
each database. We then only back up the /var/spool/mysqldumps directory.
We run the script about an hour before the backups kick off.
LP
#!/bin/bash
# Daily database dumps for inclusion in amanda backups.
MYU=/mysql user
Hi,
fedora schrieb:
Is there any proper mysql backup that can backup database without stopping
it??
If so, I don't have to worry about it? Of course it wasn't failed but I just
worried if I recover it and the database or tables might be corrupt just
because Amanda detected strange. Please
On Fri, Jun 08, 2007 at 01:15:51AM -0700, fedora wrote:
Is there any proper mysql backup that can backup database without stopping
it??
You've already had a number of suggestions, so I'll just add one (and a
shameless one, at that): ZRM for MySQL can back up MySQL databases
without the need to
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
assume that from the message at the bottom of the report that - file
changed as we read it has caused a FAILURE AND STRANGE DUMP.
Have I got anything to worry about here!.
On the myserver machine, the file _.1.tmp: has changed
On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator
wrote:
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
assume that from the message at the bottom of the report that - file
changed as we read it has caused a FAILURE AND STRANGE DUMP.
Have I
Hi
Cheers for the reassurance.
I will make note of your comments to file.
Thanks
On Thu, 2005-09-29 at 07:15 -0400, Jon LaBadie wrote:
On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator
wrote:
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
On Thursday 29 September 2005 07:15, Jon LaBadie wrote:
On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems
Administrator wrote:
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
assume that from the message at the bottom of the report that - file
changed as we
It's very rare that I don't come up here in the morning and don't see
failed and strange dumps in my 10 machines backup.
Most of the time, this occurs because some housekeeping/cleaning is
between the time the estimates and backups are done.
Most of the time, the message is there because a file
On Wed, 21 Sep 2005 at 9:04am, Guy Dallaire wrote
It's very rare that I don't come up here in the morning and don't see
failed and strange dumps in my 10 machines backup.
FAILED is a lot different than STRANGE.
Most of the time, this occurs because some housekeeping/cleaning is
between the
On Wednesday 21 September 2005 09:31, Joshua Baker-LePain wrote:
On Wed, 21 Sep 2005 at 9:04am, Guy Dallaire wrote
It's very rare that I don't come up here in the morning and don't
see
failed and strange dumps in my 10 machines backup.
FAILED is a lot different than STRANGE.
Most of the
Looks like some temporary compressed index files from the current run
should be there but are not. ...
Do you see similar behavior ?
As Joshua said, this is to be expected. Amanda is creating those files
and removing them during the time GNU tar is also backing them up.
You *might* (haven't
On Wed, 21 Sep 2005 at 11:11am, Gene Heskett wrote
That mans your indices and such are all out of date by one run. I
On tape, they are, yes. But I store the taballs on a couple of different
servers with multi-disk-failure-proof RAIDs. It's not perfect, but it's
worked well me for this far.
---
-Original Message-
From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 6:46 PM
To: Brian Tima
Subject: Re: failure and strange dump summary
Hi, Brian,
on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users:
BT I've been
Hi, Brian Tima,
on Freitag, 29. Oktober 2004 at 17:20 you wrote to amanda-users:
BT Does anyone have any more suggestions I can look into for resolving my sda3
BT disk?
BT amcheck does not report any problems.
BT my amanda user is part of the disk group
BT /dev/sda1
BT performs without
Brian Tima wrote:
Does anyone have any more suggestions I can look into for resolving my sda3
disk?
What filesystem is sda? ext2 reiserfs? ...
What is in the debug file on the client: /tmp/amanda/*.debug
concerning this DLE ?
(I thought someone already asked, but I never saw the answer.)
--
Paul
PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens
Sent: Friday, October 29, 2004 10:56 AM
To: Brian Tima
Cc: Amanda Mailing List
Subject: Re: failure and strange dump summary -- disk offline
Brian Tima wrote:
File system is ext3
Which debug file do I check?
Here are the files showing
and strange dump summary -- disk offline
Brian Tima wrote:
File system is ext3
Which debug file do I check?
Here are the files showing in the directory /tmp/amanda
All the ones relevant to /dev/sda3 ?
You never posted (afaik) which program you used to
dump the filesystem (dump or gnutar
Amanda expects to use is: LinC.
FAILURE AND STRANGE DUMP SUMMARY:
mn-py-linu /dev/sda3 lev 0 FAILED [disk /dev/sda3 offline on
mn-py-linuxsvr?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Client check: 1 host checked in 0.017 seconds, 0 problems found
-Original Message-
From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 6:46 PM
To: Brian Tima
Subject: Re: failure and strange dump summary
Hi, Brian,
on Freitag, 29
Message-
From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 6:46 PM
To: Brian Tima
Subject: Re: failure and strange dump summary
Hi, Brian,
on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users:
BT I've been messing with AMANDA now for a couple months
Subject: Re: failure and strange dump summary
Hi, Brian,
on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users:
BT I've been messing with AMANDA now for a couple months, I keep putting
BT off trying to resolve my issues. But once again, here I am.
BT Attempting
BT
, September 02, 2003 6:51 PM
Subject: Re: strange dump summary
Is there a way to force a backup to the holding disk? I want to keep
several days worth of incrementals on disk and then flush them to disk
on Friday.
) involved
BE here:
BE FAILURE AND STRANGE DUMP SUMMARY:
BE localhost feff9f0 lev 0 ERROR [not in disklist]
What does your disklist look like?
And PLEASE don´t use localhost, use the FQDN instead
(myhost.mydomain.com or something like that ...)
Using localhost does no good ... ;-)
--
best
On Tue, Sep 02, 2003 at 06:51:43PM -0500, David Barcelo enlightened us:
Is there a way to force a backup to the holding disk? I want to keep
several days worth of incrementals on disk and then flush them to disk
on Friday.
I do the same thing by just leaving the tape out of the drive.
Is there a way to force a backup to the holding disk? I want to keep
several days worth of incrementals on disk and then flush them to disk
on Friday.
Tks,
David
Matt Hyclak [EMAIL PROTECTED] writes:
I do the same thing by just leaving the tape out of the drive. The other
option is to configure amanda to use for example, /dev/amtape as its no
rewind device.
Might want to search the archives for /dev/fridaytape, we've
discussed this before.
Run a
Hi,
I recently upgraded a system from RHL8 to RHL9 and am seeing the
following errors from Amanda's mailed backup report. I'm not sure if
it's Amanda or some of the underlying tools like dump(1) involved
here:
FAILURE AND STRANGE DUMP SUMMARY:
localhost feff9f0 lev 0 ERROR
I'm a newbie to amanda and I'm having problems with my backups.
Sometimes they work but more often they don't. The report I get is:
FAILURE AND STRANGE DUMP SUMMARY:
localhost /usr/local lev 0 FAILED [data timeout]
localhost /usr/local lev 0 FAILED [dump to tape failed]
I am trying
.
Thank you,
ed
FAILURE AND STRANGE DUMP SUMMARY:
mov/ RESULTS MISSING
mov/usr RESULTS MISSING
mov/home/mp1 RESULTS MISSING
mov/home/mp2 RESULTS MISSING
mov/home/mp5 RESULTS MISSING
mov/home/mp3 RESULTS MISSING
mov/home/mp4 RESULTS
have much of a clue
as to what could be happening.
Thank you,
ed
FAILURE AND STRANGE DUMP SUMMARY:
mov/ RESULTS MISSING
*snip*
rst/ RESULTS MISSING
Basically, amanda was able to communicate with those clients but didn't
get anything meaningful back. Look in /tmp
with:
Subject: aug AMANDA MAIL REPORT FOR May 2, 2002
These dumps were to tape 3117.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
localhost hda5a lev 0 FAILED [missing result for hda5a in localhost response]
STATISTICS:
Total
On Fri, 3 May 2002 at 2:52pm, Michael Kopach wrote
FAILURE AND STRANGE DUMP SUMMARY:
localhost hda5a lev 0 FAILED [missing result for hda5a in localhost response]
Two things:
o You want to use a hostname. Even if you don't think you do, you do.
localhost will more than likely come
On Tue, 29 Jan 2002 16:12:17 -0500
John R. Jackson [EMAIL PROTECTED] wrote:
[..]
I looked at the code and that error only comes from one place, when driver
has tried doing a dump once and it failed but was requeued to TRYAGAIN,
then the second attempt also failed. I'm not sure the message
On Mon, 28 Jan 2002 13:01:40 -0500
John R. Jackson [EMAIL PROTECTED] wrote:
... suddenly 3 of 14 mountpoints on the same machine failed
for reasons I don't get.
...
machine /some/mountpoint_1 lev 1 FAILED [could not connect to machine]
Some things to check:
* See if there are left
Checking running processes is a nightshift job, I'd like to avoid :)
Understood. I'm on a first name basis with all three Operations shifts
(plus weekends) here, and I'm not sure that's necessarily a good thing.
They're nice people, but at 3 AM ...
:-) :-)
Any more tips left?
I looked at the
Hi Helpers,
as you can see, I am currently backing up just one client using gnutar.
Now, having one tapecycle run, suddenly 3 of 14 mountpoints on the same machine failed
for reasons I don't get.
The mail from today, report from the night 25.-26.
---cut-on---
...
machine /some/mountpoint_1 lev
... suddenly 3 of 14 mountpoints on the same machine failed
for reasons I don't get.
...
machine /some/mountpoint_1 lev 1 FAILED [could not connect to machine]
Some things to check:
* See if there are left over amandad (or dumper) processes laying
around still running from a previous
Hi,
Thks for zour former helps..
I do a special configuration with only the host that I'm having a
problem with (atalante).
and amanda success to do this.
So i'm kind of puzzled about it.
To give you more information I would like to tell you that
-atalante is the backup client host
I do a special configuration with only the host that I'm having a
problem with (atalante).
and amanda success to do this.
So i'm kind of puzzled about it.
That could just mean whatever made ufsdump upset doesn't happen to be
active at the moment.
-atalante is the backup client host and
Hi,
I get the fellowing error after launching amdump.
Stuff to know:
-atalante is the server that contains the holding disk on
/export/diskE/amanda
-in the disklist (atalante /export/diskE/ comp-user)
FAILURE AND STRANGE DUMP SUMMARY:
atalante /export/diskD lev 0 FAILED
I get the fellowing error after launching amdump.
...
sendbackup: info BACKUP=/usr/sbin/ufsdump
...
| DUMP: SIGBUS() ABORTING!
? DUMP: bread: dev_seek error: Invalid argument
Actually, Amanda gets it after it launches ufsdump. This is not an
Amanda problem -- it's a ufsdump problem. If
- What does this mean?(extract from a amdump report)
FAILURE AND STRANGE DUMP SUMMARY:
planner: FATAL protocol out of handles
- When amanda tells that it is expecting a new tape, what do i have to
do?
Giving an already labeled or unlabeled tape it's the same.
- Is there any chance
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Thu, Apr 26, 2001 at 04:36:29AM -0700)
HI,
I got the following, and was wondering what the Strange meant, and what I could do
about the File too large failures :
File too large:
_
your dumping a 2G file to your linux holding disk,
Either upgrade your
HI,
I got the following, and was wondering what the Strange meant, and what I could do
about the File too large failures :
...
FAILURE AND STRANGE DUMP SUMMARY:
pipe10 /dev/hda1 lev 1 STRANGE
workshop /dev/hdc lev 0 FAILED [data write: File too large]
workshop /dev/hda1 lev 0 FAILED
On Feb 20, 2001, "FFx" [EMAIL PROTECTED] wrote:
my exact version is : amanda 2.4.2-19991216-beta1
Then yours pre-dates the patch. Time to upgrade :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com,
AIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, February 20, 2001 12:51 PM
Subject: Re: Failure and strange dump summary
On Feb 20, 2001, "FFx" [EMAIL PROTECTED] wrote:
my exact version is : amanda 2.4.2-19991216-beta1
Then yours pre-dates the patch. Time to upgrade :-)
--
when i run the "new" amcheck utility "/usr/local/sbin/amcheck conf" i got
the error:
/usr/local/etc/amanda/conf/amanda.conf", line 85: configuration keyword
expected
"/usr/local/etc/amanda/conf/amanda.conf", line 85: end of line expected
"/usr/local/etc/amanda/conf/amanda.conf", line 88:
Hi !
i have installed amanda 2.4.2 with Debian 2.2 core
2.2.16fix1 in a compaq proliant server
i created the host list, tape labels, volume
indexand configured my changer ( autoloader 7x DAT DDS-3)
all dumps complete successfully but one fails with
the following error :
/--
luisinII / lev
BTW, I can backup "/etc" filesystem using dump on the client machines.
But no luck from Amanda server.
Can you do those backups as the Amanda user?
Is the group that owns the disks the primary Amanda user group or an
alternate? If an alternate and you're using xinetd, are you using the
option
w it fails.
Messages from log files -
Amanda report:
=
FAILURE AND STRANGE DUMP SUMMARY:
mogadon/etc lev 0 FAILED [disk /etc offline on mogadon?]
[snip]...
mogadon /etc 0 FAILED
[snip]...
amdump.1:
setting up estimates f
got result for host mogadon disk /etc: 0 - -1K, -1 - -1K, -1 - -1K
What's in /tmp/amanda/sendsize*debug on mogadon?
smallA
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Thank you all for your prompt reply. Here comes the output of
/tmp/amanda/sendsize*debug -
/usr/local/libexec/sendsize: version 2.4.1p1
calculating for amname '/etc', dirname '/etc'
sendsize: getting size via dump for /etc level 0
sendsize: running "/sbin/dump 0sf 1048576 - /etc"
running
Date: Fri, 2 Feb 2001 11:51:37 -0800 (PST)
From: smallA [EMAIL PROTECTED]
/usr/local/libexec/sendsize: version 2.4.1p1
calculating for amname '/etc', dirname '/etc'
sendsize: getting size via dump for /etc level 0
sendsize: running "/sbin/dump 0sf 1048576 - /etc"
running
Now that I finally have my rebuilt Amanda server working again, there is
one item that I'd like to check in on.
When it backs up the PC shares on our Win2K, WinNT and Win95 boxes, I get
this:
FAILURE AND STRANGE DUMP SUMMARY:
amanda file://xxx/PAP2 lev 0 STRANGE
amanda file
On Tue, 23 Jan 2001, Gerald T. Freymann wrote:
FAILURE AND STRANGE DUMP SUMMARY:
amanda file://xxx/PAP2 lev 0 STRANGE
And then what follows is a line by line blow of each and every file that
got backed up.
How do you make Amanda think these PC shares are no longer "St
You didn't say what versions of amanda and samba you're using. I
used to see this with old versions when I had samba configured with
too high a logging level.
I'm using Amanda 2.4.1p1 and Samba 2.0.7
P.S. You have a very catchy name. Well to me anyhow, since I
have an uncle named Jerry
Gerald T. Freymann [EMAIL PROTECTED] wrote:
I'm using Amanda 2.4.1p1 and Samba 2.0.7
You should apply the patch
http://www.amanda.org/patches/2.4.1p1/samba2-2418.diff
or upgrade to amanda-2.4.2
HTH, Lipo
--
Roland E. Lipovits
Vienna, Austria
There was a huge amount of output - so I will only forward you part
of the dump summary from the Amanda Mail Report -
FAILURE AND STRANGE DUMP SUMMARY:
admin1.cor sda10 lev 1 FAILED [/sbin/dump returned 3]
STATISTICS:
Total Full Daily
Denise Ives [EMAIL PROTECTED] writes:
There was a huge amount of output - so I will only forward you part
of the dump summary from the Amanda Mail Report -
? DUMP: More than 32 block read errors from 134577504
? DUMP: This is an unrecoverable error.
? DUMP: fopen on /dev/tty fails:
At 04:50 PM 1/11/01 +0100, Jens Bech Madsen wrote:
Denise Ives [EMAIL PROTECTED] writes:
There was a huge amount of output - so I will only forward you part
of the dump summary from the Amanda Mail Report -
? DUMP: More than 32 block read errors from 134577504
? DUMP: This is an
76 matches
Mail list logo
