Does the amcheck.XXX.debug or amcheck-device.XXX.debug file have
anything useful in it?
-Sandro
-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On
Behalf Of Chris Nighswonger
Sent: Wednesday, July 27, 2016 12:20 PM
To: amanda
What did you change, “about a month ago” ?
I have TCP problems when a node is DOWN, wherein amchecking it will cause
problems
with several other nodes (due to TCP timeout values) BUT your nodes are up.
“Broken pipe” plus no logs on the client sounds like the system level
(outside of ama
No takers?
Additionally, on the failing client side an amcheck log is created
*only* if amcheck is run against that client. When amcheck is run
against the entire job (all clients) no amcheck log is created on the
clients that fail.
On Tue, Jul 26, 2016 at 9:09 AM, Chris Nighswonger
wrote:
> t
I tried modifying the taperscan algorithm. That didn't work.
I tried creating a second vtape library, with 7 slots, to test
the use case where there were two changers with different numbers of slots. In
a chg-rait setup with two chg-disk changers, the slots woul
