(FATAL driver reading result from taper:
Connection reset by peer) should be solved first. But i am not quite
sure where to look. What do i need to check?
What daemon is not running and therefore resetting it by peer?
Do you need more infos?
Thanks, Mario
disk localhost:md1.
STATS driver startup time 0.067
FATAL driver reading result from taper: Connection reset by peer
FAIL planner localhost md1 20060807 0 [dump larger than tape, 30864297
KB, but cannot incremental dump new disk]
FATAL planner cannot fit anything on tape, bailing out
20060807
WARNING planner tapecycle (8) = runspercycle (28)
INFO planner Adding new disk localhost:md1.
STATS driver startup time 0.067
FATAL driver reading result from taper: Connection reset by peer
FAIL planner localhost md1 20060807 0 [dump larger than tape, 30864297
KB, but cannot incremental dump
) = runspercycle (28)
INFO planner Adding new disk localhost:md1.
STATS driver startup time 0.067
FATAL driver reading result from taper: Connection reset by peer
FAIL planner localhost md1 20060807 0 [dump larger than tape, 30864297
KB, but cannot incremental dump new disk]
FATAL planner cannot fit
On Mon, 7 Aug 2006, mario wrote:
the ubuntu package cdrw-taper caused this problem, afer removing it
everything seems to go fine (it came with a weird/broken perl script). I
have some other sort of problem now, which i will post in a new mail.
If it behaves like plain Debian, make sure user
