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 connection failed, at least before the estimate was finished. Also note the third line: "Successfully retried". Check out what happens after that, as it may have gone on to successfully backup cpu.ind.com:/var/lib/mysql Rob -- Rob Echlin Software Development Environment Prime Espial IPTV rechlin -at- espial.com Phone: +1 613-230-4770 ext 1150 www.espial.com -------- Espial Group Inc. Confidential -------- Important Notice: This communication is intended to be received only by the individual or entity to whom or to which it is addressed and may contain information that is privileged, confidential and/or subject to copyright. Any unauthorized use, copying, review or disclosure of this communication is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender by reply email. Thank you for your cooperation. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of fedora Sent: Monday, June 18, 2007 12:23 AM To: amanda-users@amanda.org Subject: Re: FAILURE AND STRANGE DUMP SUMMARY 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: > > /-- 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 > | gtar: ./mysql.sock: socket ignored > ? gtar: ./mysql/general_log.CSV: file changed as we read it > | Total bytes written: 562432000 (537MiB, 7.7MiB/s) > sendbackup: size 549250 > sendbackup: end > > > NOTES: > planner: Full dump of ind.ayo.com:/var/lib/mysql promoted from 5 days > ahead. > taper: tape DailySet1-04 kb 2727712 fm 10 [OK] > > DUMP SUMMARY: > DUMPER STATS TAPER > STATS > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS > KB/s > -------------------------- ------------------------------------- > ------------- > ind.ayo -/lib/mysql 0 549250 30176 5.5 1:10 429.8 0:00 > 154753.5 > > Nothing errors in debug files. Can u guys tell me how come Amanda still > complaining failed and strange whereas dump summary looks OK even I can > recover the backup files. > > Any ideas guys?? > > > I got new problem: These dumps were to tape DailySet1-13. The next tape Amanda expects to use is: DailySet1-14. 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 can anyone explain to me? -- View this message in context: http://www.nabble.com/FAILURE-AND-STRANGE-DUMP-SUMMARY-tf3788077.html#a1 1169793 Sent from the Amanda - Users mailing list archive at Nabble.com.
