little question
Hi,
When running amdump, it does nothing after completing the sendsize.
It is still running, but not consuming cpu nor disk nor net.
How may I find out what's going on?
on /usr/local/var/amanda/config/{amdump,log} I just can't find
any useful information.
Thank you very much,
Gonzalo Arana
[Fwd: little question]
Alexandre Oliva wrote:
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
It says 'waiting for dump' on all hosts/directories.
All of them? What is the reason it claims for being idle?
Where may I see a reason? on the amstatus output?
It began to work right now (?)
I still have the logs of the freezed runs of amdump.
Where may I look for?
Also, please note the last line of my signature.
ups! Sory!
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: [Fwd: little question]
Alexandre Oliva wrote:
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
Where may I see a reason? on the amstatus output?
Yep. At the end of the report, it was why each dumper is idle; before
that, it prints the main reason why the whole process is idle, if it
is.
Sorry, but I can't see any info:
amstatus config --file /usr/local/var/amanda/config/amdump.2
Usign ...
hostn:/dir1 0 160k wait for dumping
hostn:/dir2 0 20150k wait for dumping
SUMMARY part real estimated
size size
partition : 191
estimated : 191 11697412k
failed : 0 0k ( 0.00%)
wait for dumping: 191 11697412k (100.00%)
dumping to tape : 0 0k ( 0.00%)
dumping : 00k0k ( 0.00%) ( 0.00%)
dumped : 00k0k ( 0.00%) ( 0.00%)
wait for writing: 00k0k ( 0.00%) ( 0.00%)
writing to tape : 00k0k ( 0.00%) ( 0.00%)
failed to tape : 00k0k ( 0.00%) ( 0.00%)
taped : 00k0k ( 0.00%) ( 0.00%)
all dumpers active
taper idle
and thats it.
It did keep as this for 20 minutes and I got tired of waiting.
I cancelled that backup.
Sorry again!!
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: [Fwd: little question]
Alexandre Oliva wrote:
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
dumping to tape : 0 0k ( 0.00%)
dumping : 00k0k ( 0.00%) ( 0.00%)
all dumpers active
Hmm... This is very odd. What is `inparallel' set to, in amanda.conf?
8
and thats it.
I assumed you had 2.4.2.
You are absolutely right.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: YAAQ (Yet another amanda question)
"John R. Jackson" wrote: Load tape DEIMOS02 now Continue? [Y/n]: timeout waiting for amrestore increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow amrecover: error reading tape: Success extract_list - child returned non-zero status: 1 Continue? [Y/n]: On the /tmp/amanda/amidxtaped.debug I get: ... amrestore: 57: skipping deimos.sinectis.com.ar._websp_a.20001107.0 amrestore: 58: restoring deimos.sinectis.com.ar._websp_m.20001107.0 Error 32 (Broken pipe) offset 0+32768, wrote 0 amrestore: pipe reader has quit in middle of file. amrestore: skipping ahead to start of next file, please wait... amidxtaped: amrestore terminated normally with status: 2 Rewinding tape: done amidxtaped: pid 20634 finish time Fri Nov 10 09:43:24 2000 My question is: What pipe got broken? ... Amrecover has a network connection (pipe) to amidxtaped to read the image amrestore is getting from tape. When amrecover got tired of waiting, it closed down its end which propogated back to amrestore as a broken pipe. How do I solve this? ... Did it take a long time between answering "yes" (hitting CR) to the "Continue?" message and seeing the error? Like 30 minutes? It took a while, but I think it was by far less than 30 minutes (it took about 5 minutes). My first suggestion would be that you find out what file on the tape you need to access. That can be done with "amadmin config find ..." or (I think) the "history" command in amrecover or by amtoc, etc. Then, when amrecover asks you to load a tape, not only should you put the tape in the drive but go ahead and "mt fsf nn" it to the proper file. That will probably significantly speed up restores and might get past the timeout problem. OK, I will try this. Thank you very much, Gonzalo Arana John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Gonzalo Arana
