Re: FAILURE AND STRANGE DUMP SUMMARY:

2005-09-29 Thread Jon LaBadie
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

Re: FAILURE AND STRANGE DUMP SUMMARY:

2005-09-29 Thread Chuck Amadi Systems Administrator
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

Re: FAILURE AND STRANGE DUMP SUMMARY:

2005-09-29 Thread Gene Heskett
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

Re: FAILURE AND STRANGE DUMP SUMMARY:

2002-01-28 Thread John R. Jackson
>... 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 f

Re: FAILURE AND STRANGE DUMP SUMMARY:

2002-01-29 Thread Sascha Wuestemann
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 th

Re: FAILURE AND STRANGE DUMP SUMMARY:

2002-01-29 Thread John R. Jackson
>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 th

Re: FAILURE AND STRANGE DUMP SUMMARY:

2002-01-30 Thread Sascha Wuestemann
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 me

Re: Failure and Strange Dump Summary

2002-05-03 Thread Joshua Baker-LePain
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

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-07 Thread fedora
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

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-07 Thread Olivier Nicole
> 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

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-08 Thread fedora
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. Olivier Nicole wro

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-08 Thread Marc Muehlfeld
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. Plea

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-08 Thread Olivier Nicole
> 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

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-08 Thread Bruce Thompson
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 Amanda

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-08 Thread Linda Pahdoco
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 w

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-08 Thread Marc Muehlfeld
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 advice

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-08 Thread Dustin J. Mitchell
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

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-11 Thread fedora
Almost files which is the extension ./databasename/*.MYI changed not only ./mysql/general_log.CSV Olivier Nicole 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 >

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-11 Thread Linda Pahdoco
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 clear

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-17 Thread fedora
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:

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-17 Thread Olivier Nicole
> 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

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-17 Thread Marc Muehlfeld
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 estimat

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-18 Thread fedora
Thanks Marc. Marc Muehlfeld wrote: > > 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 heade

RE: FAILURE AND STRANGE DUMP SUMMARY

2007-06-18 Thread Robert Echlin
--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

Re: FAILURE AND STRANGE DUMP SUMMARY

2007-06-19 Thread Paul Bijnens
> > -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 wrot

RE: failure and strange dump summary

2004-10-28 Thread Brian Tima
Check 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 Freita

RE: failure and strange dump summary

2004-10-28 Thread Brian Tima
--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 messing with AMAND

RE: failure and strange dump summary

2004-10-28 Thread Frank Smith
[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 n

Re: FAILURE AND STRANGE DUMP SUMMARY

2001-01-23 Thread Mitch Collinsworth
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 "Strange

Re: FAILURE AND STRANGE DUMP SUMMARY

2001-01-23 Thread Gerald T. Freymann
> 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 J

Re: FAILURE AND STRANGE DUMP SUMMARY

2001-01-23 Thread Roland E. Lipovits
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

RE: FAILURE AND STRANGE DUMP SUMMARY

2001-01-23 Thread Chris Herrmann
orked out - if you do suss it then please let me know! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mitch Collinsworth Sent: Wednesday, 24 January 2001 02:14 To: Gerald T. Freymann Cc: [EMAIL PROTECTED] Subject: Re: FAILURE AND STRANGE DUMP SUMMARY O

Re: Failure and strange dump summary

2001-02-20 Thread Alexandre Oliva
On Feb 20, 2001, "FFx" <[EMAIL PROTECTED]> wrote: > ? gtar: ./dev/log: socket ignored Are you sure the client is running Amanda 2.4.2? The patch that ignored this message went in on May 28 last year. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Develop

Re: Failure and strange dump summary

2001-02-20 Thread FFx
my exact version is : amanda 2.4.2-19991216-beta1 - Original Message - From: "Alexandre Oliva" <[EMAIL PROTECTED]> To: "FFx" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 20, 2001 11:23 AM Subject: Re: Failure and strange

Re: Failure and strange dump summary

2001-02-20 Thread Alexandre Oliva
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, redhat

Re: Failure and strange dump summary

2001-02-20 Thread José Carreiro
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 patc

Re: Failure and strange dump summary

2001-02-20 Thread John R. Jackson
>when i run the "new" amcheck utility "/usr/local/sbin/amcheck " i got >the error: > >/usr/local/etc/amanda//amanda.conf", line 85: configuration keyword >expected >"/usr/local/etc/amanda//amanda.conf", line 85: end of line expected >"/usr/local/etc/amanda//amanda.conf", line 88: configuration ke

Re: FAILURE AND STRANGE DUMP SUMMARY:

2001-07-30 Thread John R. Jackson
>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.

Re: FAILURE AND STRANGE DUMP SUMMARY:

2001-08-02 Thread John R. Jackson
>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"

Re: FAILURE AND STRANGE DUMP SUMMARY:

2001-08-04 Thread BRINER Cedric
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" a

RE: failure and strange dump summary -- disk offline

2004-10-29 Thread Brian Tima
--- -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'

Re: failure and strange dump summary -- disk offline

2004-10-29 Thread Stefan G. Weichinger
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 m

Re: failure and strange dump summary -- disk offline

2004-10-29 Thread Paul Bijnens
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). Do a grep of /dev/sda3 or the mountpoint for gnuta

Re: failure and strange dump summary -- disk offline

2004-10-29 Thread Paul Bijnens
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

RE: failure and strange dump summary -- disk offline

2004-10-29 Thread Brian Tima
Original Message- From: [EMAIL 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 fil

RE: failure and strange dump summary -- disk offline

2004-10-29 Thread Frank Smith
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 a