Please try the following patch. It will not fix anything, but will log
the exit code of all the processes driver starts, in particular, the
messed up dumpers. Actually, it will only log them if they indicate some
kind of failure, but I'd be surprised if they are going away cleanly.
The
-
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 14, 2001 10:57 AM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need help figuring out why these don't complete
... that tells me that it is not partition dependent at least. ...
Agreed. Not sure if that's good
... that tells me that it is not partition dependent at least. ...
Agreed. Not sure if that's good or bad :-).
I am not getting any core files ...
OK.
Please try the following patch. It will not fix anything, but will log
the exit code of all the processes driver starts, in particular, the
Patch Server and Clients, or just the Server?
The patch goes against driver, which is just the server side.
The lines I was referring to were these and they start at line 888:
driver: dumping ns3-backnet.inherent.com:/var directly to tape
driver: no idle dumpers for
figuring out why these don't complete
index tee cannot write [Broken pipe]
...
Where does the tee come into play so I can tell what application failed?
...
The tee is caused by having indexing turned on. The dumper terminated
for some reason and there was nothing on the other end of that file
index tee cannot write [Broken pipe]
...
Where does the tee come into play so I can tell what application failed? ...
The tee is caused by having indexing turned on. The dumper terminated
for some reason and there was nothing on the other end of that file
descriptor to write to any more, which
:16 PM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need help figuring out why these don't complete
index tee cannot write [Broken pipe]
...
Where does the tee come into play so I can tell what application failed?
...
The tee is caused by having indexing turned on. The dumper terminated
... I'll go fight the amandad busy and dumper died messages later, but why
am I getting all the dump to tape failed ...
You'll need to fight the dumper died messages first. They triggered
the dump to tape failed.
The place to start is the amdump.1 file (or whichever one matches
this run).
You
I have not reset the chunksize from it's default so it is still at whatever
the default is. I'll explicitly set it to 1Gb and try again. ...
The default is already 1 GByte, so that's not it (and you don't need
to change it). And I can see in the log you sent that it's still using
that value.
. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 3:16 PM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need help figuring out why these don't complete
I have not reset the chunksize from it's default so it is still at whatever
the default is. I'll explicitly set
Attached is the Amanda report from the backup that I just completed, which
should have been a Full Backup forced by a dumpcycle of 0 and runspercycle
of 1. I'll go fight the amandad busy and dumper died messages later, but why
am I getting all the dump to tape failed which pair up with the No
11 matches
Mail list logo
