Jean-Louis,

The amdump just finished and because amanda ran out of tapes
(runtapes=10) it completed badly leaving stuff in the holdding
disk. I'm flushing it at the moment but I noticed that when amanda
gave up it left a lot of gnutar lying around, with amandad as parent.
I had to manually kill them. Looks like signals are not doing ok.
I've attached one example of a DLE's sendbackup and runtar debug file.
It's not the first time I notice that when a DLE fails to make it
to tape successfully processes are left running...

* Jean-Louis Martineau <martineau AT zmanda DOT com> [20061122 09:32]:
> Could you post amandad.<timestamp>.debug file from yorick?
> 
> Jean-Francois Malouin wrote:
> >On a server running irix-6.5 and amanda 2.5.1p2
> >planner debug shows:
> >
> >security_getdriver(name=bsdtcp) returns 4075aa8
> >security_handleinit(handle=1001d4a8, driver=4075aa8 (BSDTCP))
> >security_streaminit(stream=1005e538, driver=4075aa8 (BSDTCP))
> >security_close(handle=1001cfe0, driver=4075aa8 (BSDTCP))
> >security_stream_close(10053a80)
> >security_stream_seterr(1005e538, SOCKET_EOF)
> >security_seterror(handle=1001d4a8, driver=4075aa8 (BSDTCP) error=EOF
> >on read from yorick)
> >security_close(handle=1001d4a8, driver=4075aa8 (BSDTCP))
> >security_stream_close(1005e538)
> >
> >and the amanda report shows things like:
> >
> >  yorick  DATA_sub101   lev 0  FAILED [hmm, disk was stranded on waitq]
> >  planner: ERROR Request to yorick failed: EOF on read from yorick
> >
> >and the backup fails. The funny thing is that I have 2 other configurations
> >running 2.5.1p2 in parallel that doesn't exhibit this behaviour.
> >Any clues?
> >jf
> >  

-- 
<° ><

runtar.20061123080413.debug
Description: Text document

sendbackup.20061123080320.debug
Description: Text document