Hi everybody, can you help me?
I was running amanda with no problem but suddenly one day i run amadmin
to find a file and it shown me :
2001-05-31 hermes hda1 0 Cinta3 0 [out of tape]
2001-05-31 hermes hda1 0 --- 0 FAILED (driver) [dump to
tape failed]
2001-05-31 hermes
Hi,
I'm trying to resolve a problem with amanda, but I don't know why.
Every time I run amdump I receive a report like this:
These dumps were to tape Diaria-001.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
volinux.ay /home/sanzm lev 0
9231.637 wrwait 1358.730 filemark
3.380}]
FAIL driver tincan /home/tincan/user 0 [dump to tape failed]
t of tape]
> 2001-05-31 hermes hda1 0 --- 0 FAILED (driver) [dump to
> tape failed]
> 2001-05-31 hermes hda1 0 --- 0 FAILED (dumper) ["data
> write: Broken pipe"]
>
> but i could restore files, the backup was corrcet.
>
> Since that day 'amadm
>2001-05-31 hermes hda1 0 Cinta3 0 [out of tape]
>2001-05-31 hermes hda1 0 --- 0 FAILED (driver) [dump to
>tape failed]
>2001-05-31 hermes hda1 0 --- 0 FAILED (dumper) ["data
>write: Broken pipe"]
Are you sure your files are not kept
I though the same thing, but the files are not on the holding disk.
So that i don't understand that error.
Vicent.
Olivier Nicole escribió:
> >2001-05-31 hermes hda1 0 Cinta3 0 [out of tape]
> >2001-05-31 hermes hda1 0 --- 0 FAILED (driver) [dump
On Jun 5, 2001, Olivier Nicole <[EMAIL PROTECTED]> wrote:
>> 2001-05-31 hermes hda1 0 Cinta3 0 [out of tape]
>> 2001-05-31 hermes hda1 0 --- 0 FAILED (driver) [dump to
>> tape failed]
>> 2001-05-31 hermes hda1 0 --- 0 FAILED (d
I though the same thing, but the files are not on the holding disk.
So that i don't understand that error.
Vicent.
Olivier Nicole escribió:
> >2001-05-31 hermes hda1 0 Cinta3 0 [out of tape]
> >2001-05-31 hermes hda1 0 --- 0 FAILED (driver) [dump
On Tue, 28 Aug 2001, wanadoo wrote:
> driver: result time 3.503 from dumper0: FAILED 01-2 [taper port
> open: Resource temporarily
> unavailable]
> driver: result time 123.497 from taper: TAPE-ERROR 00-1 [port
> connect timeout]
It sounds like another process already has the port that
On Thu, 30 Aug 2001, wanadoo wrote:
> Mitch Collinsworth ha escrito:
>
> > On Tue, 28 Aug 2001, wanadoo wrote:
> >
> > > driver: result time 3.503 from dumper0: FAILED 01-2 [taper port
> > > open: Resource temporarily
> > > unavailable]
> > > driver: result time 123.497 from taper: TAPE-ERR
Mitch Collinsworth ha escrito:
> On Tue, 28 Aug 2001, wanadoo wrote:
>
> > driver: result time 3.503 from dumper0: FAILED 01-2 [taper port
> > open: Resource temporarily
> > unavailable]
> > driver: result time 123.497 from taper: TAPE-ERROR 00-1 [port
> > connect timeout]
>
> It sounds
mp to tape failed]
mail03 /home lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:09
Run Time (hrs:min) 0:51
Dump Time (hrs:min)0:37 0:37
On Tue April 8 2003 14:03, a blob of green gelatin wrote:
>On Tue, 8 Apr 2003, Gene Heskett wrote:
>> >taper: stream_accept: timeout after 120 seconds
>> >dumper: stream_client: connect to 127.0.0.1.32810 failed:
>> > Connection timed out
>>
>> Are you useing localhost as the client address? Pleas
On Tue, Dec 30, 2003 at 11:04:29AM -0500, John Dalbec wrote:
> I can't find anything in /tmp/amanda or /var/log/messages. Am I just not
> looking in the right places?
> Thanks,
> John
You are not using any holding disk, is that intentional?
Do you mean your /tmp/amanda was empty?
Were you look
Jon LaBadie wrote:
On Tue, Dec 30, 2003 at 11:04:29AM -0500, John Dalbec wrote:
I can't find anything in /tmp/amanda or /var/log/messages. Am I just not
looking in the right places?
Thanks,
John
You are not using any holding disk, is that intentional?
I have two holding disks specified in m
On Tue, Dec 30, 2003 at 02:50:57PM -0500, John Dalbec wrote:
>
>
> Jon LaBadie wrote:
>
> >On Tue, Dec 30, 2003 at 11:04:29AM -0500, John Dalbec wrote:
> >
> >>I can't find anything in /tmp/amanda or /var/log/messages. Am I just not
> >>looking in the right places?
> >>Thanks,
> >>John
> >
> >
l03 /var/spool/mail lev 0 FAILED [dump to tape failed]
> mail03 /home lev 0 FAILED [dump to tape failed]
Did you try amstatus? It should give the reason. Also look into
the amdump.X and log file for that backup near the end, maybe there
is diagnostic information neither amreport nor ams
ot looking in the right places?
> ...
> These dumps were to tape WeeklySet116.
> The next tape Amanda expects to use is: WeeklySet117.
>
> FAILURE AND STRANGE DUMP SUMMARY:
> mail03 /var/spool/mail lev 0 FAILED [dump to tape failed]
> mail03 /home lev 0 FAILE
John Dalbec wrote:
Georg Rehfeld wrote:
> FAILURE AND STRANGE DUMP SUMMARY:
> mail03 /var/spool/mail lev 0 FAILED [dump to tape failed]
> mail03 /home lev 0 FAILED [dump to tape failed]
Did you try amstatus? It should give the reason. Also look into
the amdump.X and log
Georg Rehfeld wrote:
John Dalbec wrote:
Georg Rehfeld wrote:
> FAILURE AND STRANGE DUMP SUMMARY:
> mail03 /var/spool/mail lev 0 FAILED [dump to tape failed]
> mail03 /home lev 0 FAILED [dump to tape failed]
Did you try amstatus? It should give the reason. Also look
John Dalbec said:
>> So the dumper immediately reports 'connection refused' when
>> attempting
>> to connect to the taper process. Wrong permissions?
>
> Wrong permissions on what? It's a TCP connection over the loopback.
> What
> permissions could possibly affect that?
> John
Perhaps a dumb qu
Hi Kurt, John and all others,
Kurt Yoder wrote:
John Dalbec said:
So the dumper immediately reports 'connection refused' when
attempting
to connect to the taper process. Wrong permissions?
Wrong permissions on what? It's a TCP connection over the loopback.
What
permissions could possibly affect
Georg Rehfeld wrote:
Hi Kurt, John and all others,
Kurt Yoder wrote:
John Dalbec said:
So the dumper immediately reports 'connection refused' when
attempting
to connect to the taper process. Wrong permissions?
Wrong permissions on what? It's a TCP connection over the loopback.
What
permiss
On Mon, Jan 05, 2004 at 02:31:18PM -0500, John Dalbec wrote:
> It just occurred to me that maybe this is a side effect of /etc/hosts cache
> poisoning (courtesy of Red Hat Linux 7.3 NSCD). We've been getting e-mail
> from a netblock in Vietnam that reverse-resolves to "localhost". NSCD
> cache
Jean-Louis Martineau wrote:
On Mon, Jan 05, 2004 at 02:31:18PM -0500, John Dalbec wrote:
It just occurred to me that maybe this is a side effect of /etc/hosts cache
poisoning (courtesy of Red Hat Linux 7.3 NSCD). We've been getting e-mail
from a netblock in Vietnam that reverse-resolves to "
On Mon, Jan 05, 2004 at 03:00:34PM -0500, John Dalbec wrote:
>
>
> >>Would upgrading to the current version change this?
> >
> >
> >No, it's a problem with your system configuration, not an amanda bug.
>
> Well, I turned off /etc/hosts caching so that should fix the system problem.
> What would
Jon LaBadie wrote:
On Mon, Jan 05, 2004 at 03:00:34PM -0500, John Dalbec wrote:
Would upgrading to the current version change this?
No, it's a problem with your system configuration, not an amanda bug.
Well, I turned off /etc/hosts caching so that should fix the system problem.
What would I
Hi John and all,
John Dalbec wrote:
Jean-Louis Martineau wrote:
On Mon, Jan 05, 2004 at 02:31:18PM -0500, John Dalbec wrote:
It just occurred to me that maybe this is a side effect of /etc/hosts
cache poisoning (courtesy of Red Hat Linux 7.3 NSCD). We've been
getting e-mail from a netblock
mailreport afterwards tells me the following:
NOTES:
driver: mobilkom md0 3 [dump to tape failed, will try again
disk.Run amflush to flush them to tape.The next tape Amanda expects to
use is: backup010.FAILURE AND STRANGE DUMP SUMMARY:
awe /home lev 0 FAILED
[out of tape] awe /home lev
0 FAILED [dump to tape failed]
awe /home lev 0 FAILED ["data write:
Broken pipe"]
On Fri, Jul 25, 2003 at 02:29:46PM +0200, Andreas Ntaflos wrote:
> Anyone have an idea? The logs (amdump.*, log.date.*) don't give much
> more information apart from telling me that the `dump to drive failed'
> and it `will try again'. Not of much help. Any pointers where I should
> have a look?
L
apetype.
If so, either increase your tape length (since you're really writing
to a file instead of to a tape) or increase runtapes to write to
multiple 'tapes'.
> awe/home lev 0 FAILED [dump to tape failed]
I'm guessing you're not using a holding disk. Whil
aper awe /home 20040828 0 [out of tape]
ERROR taper no-tape [[writing file: short write]]
FAIL driver awe /home 20040828 0 [dump to tape failed]
FAIL dumper awe /home 20040828 0 ["data write: Broken pipe"]
sendbackup: start [awe:/home level 0]
sendbackup: info BACKUP=/bin/t
184160 22300 12.1 1:19 282.1 1:19 282.0
> ***
>
> >From the end of my amanda log:
> ***
> INFO taper tape backup09 kb 2188064 fm 30 writing file: short write
> FAIL taper awe /home 20040828 0 [out of tape]
> ERROR taper no-tape [[writing file: short write]]
> FAI
> awe -/lib/mysql 0 184160 22300 12.1 1:19 282.1 1:19 282.0
> ***
>
> From the end of my amanda log:
> ***
> INFO taper tape backup09 kb 2188064 fm 30 writing file: short write
Looks like it died around 2 GB.
> FAIL taper awe /home 20040828 0 [out of tape]
> ERROR t
quot;Frank Smith" <[EMAIL PROTECTED]>
To: "Reidar Nordin" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, August 30, 2004 2:33 AM
Subject: Re: [out of tape] [dump to tape failed] ["data write: Broken pipe"]
> --On Sunday, August 29, 200
Jennifer Luisi schrieb:
> /export/amanda/vtapes/tape1/slots:
> total 44
> lrwxrwxrwx 1 amanda disk 39 Nov 26 13:53 data ->
> /export/amanda/vtapes/tape1/slots/slot4
> -rw--- 1 amanda disk 11 Nov 26 13:53 info
> drwxr-xr-x 2 amanda disk 4096 Nov 26 12:38 slot1
[...]
You seem to have mi
The amanda log file
> shows:
>
> SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0 kps
> 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
> INFO driver [hostname] /export/backup 0 [dump to tape failed, will try
> again]
>
> I've goo
a log file
shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0
kps 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO driver [hostname] /export/backup 0 [dump to tape failed, will try
again]
What's the dumper result for the disk?
Jean-Louis
the dumper result for the disk?
Jean-Louis
Where can I find the dumper result? Since the backup just seems to
hang with the "dump to tape failed" errors, I haven't actually been
letting it complete. I've given it up to an hour or so and then
killed it.
The email repo
g.
When I run amcheck, everything seems fine. Then, when I run amdump,
nothing ever gets written to disk (virtual tape). The amanda log file
shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0
kps 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO
Jennifer Luisi schrieb:
> I think I'm getting closer to the problem. There seems to be a
> connection issue between my server and client. If anyone has any input,
> I'd appreciate it. I've got iptables on my client set up to accept port
> 10080 connections from my server, and it's obviously talk
When I run amcheck, everything seems fine. Then, when I run amdump,
nothing ever gets written to disk (virtual tape). The amanda log
file shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0
kps 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO dri
Jennifer Luisi schrieb:
> Okay, I figured out what my silly little problem was. Apparently, you
> need to turn on amanda on your server before anything will work.
An interesting observation:
software has to be started to work
;)
> It's
> interesting that there isn't a useful error to point ou
Hi again
I was getting the following this error - server / lev 0 FAILED [dump to
tape failed] I assume tar is not working.
I am using this version of tar.
server:/etc/postfix # /bin/tar --version
tar (GNU tar) 1.13.25
cd /var/lib/amanda/DailySet1
ls -lt > less amdump
(output)
dri
Hello, Chuck,
on 23.06.2005, 11:41 you wrote to amanda-users@amanda.org:
> I was getting the following this error - server / lev 0 FAILED [dump to
> tape failed] I assume tar is not working.
> I am using this version of tar.
> server:/etc/postfix # /bin/tar --version
> tar (G
Thanks I am using the link to digest the rest
Cheers
On Thu, 2005-06-23 at 12:04 +0200, [EMAIL PROTECTED] wrote:
> Hello, Chuck,
>
> on 23.06.2005, 11:41 you wrote to amanda-users@amanda.org:
>
> > I was getting the following this error - server / lev 0 FAILED [dump to
> I was getting the following this error - server / lev 0 FAILED [dump to
> > tape failed] I assume tar is not working.
>
> > I am using this version of tar.
>
> > server:/etc/postfix # /bin/tar --version
> > tar (GNU tar) 1.13.25
>
> Ok.
>
> tar wor
[EMAIL PROTECTED] wrote:
/-- server / lev 0 FAILED [/bin/tar returned 2]
sendbackup: start [greenbottle.smtl.co.uk:/ level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./med
Hi Paul
I run the comand here is the output.
server:/etc/amanda/DailySet1 # tar -cf - --sparse --one-file-sys --tot
--dir /media . | cat >/dev/null
tar: ./cdrom: Cannot savedir: No medium found
tar: ./floppy: Cannot savedir: No medium found
Total bytes written: 10240 (10kB, 74kB/s)
tar: Error ex
Hi
I am using SuSE SLES 9,version Amanda 2.4.2 and /etc/fstab.
Very weired I just mounted a floppy and cdrom with no problems
So it is working.
Cheers
On Thu, 2005-06-23 at 13:03 +0200, Paul Bijnens wrote:
> [EMAIL PROTECTED] wrote:
> >
> >>/-- server / lev 0 FAILED [/bin/tar returned 2]
> >>
Chuck Amadi Systems Administrator wrote:
My fstab is as follows but when using Yast and floppy I have had no
issues.
/dev/cdrom /media/cdrom subfs
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppysubfs
fs=floppyfss,procuid,nodev
Hi
Great News
I have included the ./media or be it ./media/cdrom and ./media/floppy I
will use the simpler format and run the amdump.
Cheers
Chuck
On Thu, 2005-06-23 at 14:52 +0200, Paul Bijnens wrote:
> Chuck Amadi Systems Administrator wrote:
> > My fstab is as follows but when using Yast
On Thu, Jun 23, 2005 at 01:03:13PM +0200, Paul Bijnens wrote:
>
> >>? gtar: ./media/cdrom: Cannot savedir: No medium found
> [...]
> >>| gtar: ./var/spool/postfix/public/showq: socket ignored
> >
>
> Note that the error is not in the sockets (those lines are marked
> with a pipe-symbol as "normal"
Hi PB
I reverted back to ./var, ./tmp as you So suggested and added ./media to
the exclude list.
I run amdump and It looks like it's working accordingly as per the Dump
Summary.
Here's my output Sorry for the constant mails I now have a better
understanding on whats going on and by next week wil
On Thu, Jun 23, 2005 at 04:39:02PM +0100, Chuck Amadi Systems Administrator
wrote:
> Hi PB
>
> I reverted back to ./var, ./tmp as you So suggested and added ./media to
> the exclude list.
>
> I run amdump and It looks like it's working accordingly as per the Dump
> Summary.
Starting to look goo
Hi Thanks for the advise
I will monitor as suggested but worth the voyager.
Cheers All
On Thu, 2005-06-23 at 12:01 -0400, Jon LaBadie wrote:
> ./var/tmp
> ./var/spool/postfix
> ./var/spool/cups
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Labor
--On Thursday, June 23, 2005 09:31:25 -0400 Jon LaBadie <[EMAIL PROTECTED]>
wrote:
> On Thu, Jun 23, 2005 at 01:03:13PM +0200, Paul Bijnens wrote:
>>
>> >> ? gtar: ./media/cdrom: Cannot savedir: No medium found
>> [...]
>> >>| gtar: ./var/spool/postfix/public/showq: socket ignored
>> >
>>
>> N
--On Thursday, June 23, 2005 12:01:05 -0400 Jon LaBadie <[EMAIL PROTECTED]>
wrote:
> On Thu, Jun 23, 2005 at 04:39:02PM +0100, Chuck Amadi Systems Administrator
> wrote:
>> Hi PB
>>
>> I reverted back to ./var, ./tmp as you So suggested and added ./media to
>> the exclude list.
>>
>> I run amd
Hello, Chuck,
on 23.06.2005, 12:35 you wrote to amanda-users@amanda.org:
> # Thus use exclusions for all those sockets? This would remove all
> # those nasty ignore-errors and No media found in the Report.
> ./dev
> ./tmp
> ./var
> ./media/cdrom
> ./media/floppy
> I assume the last five entries
60 matches
Mail list logo
