That's a good question. Only various routine updates as far as I know.
Strangely enough, the clients failing amcheck seemed to have backed up
ok last evening....
Here is the amcheck output from before the amdump run:
Amanda Tape Server Host Check
-----------------------------
Holding disk /storage/campus: 912248832 kB disk space available, using
912248832 kB
Searching for label 'campus-NGH861L4':found in slot 9: volume 'campus-NGH861L4'
Will write to volume 'campus-NGH861L4' in slot 9.
NOTE: skipping tape-writable test
Server check took 158.373 seconds
Amanda Backup Client Hosts Check
--------------------------------
WARNING: scriptor: selfcheck request failed: error sending REQ: write
error to: Broken pipe
WARNING: masada: selfcheck request failed: error sending REQ: write
error to: Broken pipe
Yet amreport says:
masada /etc/dansguardian 1 180
7 3.9 0:00 122.6 0:05 1.4
masada /etc/network 0 50
7 14.0 0:00 286.7 0:04 1.8
masada /etc/squid3 1 10
1 10.0 0:00 24.6 0:05 0.0
masada /home/backups/database/postgresql 1 20
1 5.0 0:00 24.7 0:06 0.0
scriptor /etc/amanda 0 40
4 10.0 0:00 29.2 0:05 0.8
scriptor /var/backups 1 5670
5069 89.4 0:01 5896.7 0:05 1013.8
Go figure... I think I'm going crazy(er)...
Yet amreport also says stuff like:
NOTES:
planner: scriptor /etc/amanda 20160727221502 0 "Request to scriptor
failed: error sending REQ: write error to: Broken
pipe, using server estimate"
planner: scriptor /var/backups 20160727221502 0 "Request to scriptor
failed: error sending REQ: write error to: Broke
n pipe, using server estimate"
On Wed, Jul 27, 2016 at 3:02 PM, Debra S Baddorf <[email protected]> wrote:
> 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 amanda?)
> TCP is having troubles; the client is never getting an amanda started at
> all.
> But I can’t think why that would happen.
>
> Deb Baddorf
>
>
>> On Jul 27, 2016, at 1:20 PM, Chris Nighswonger
>> <[email protected]> wrote:
>>
>> 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
>> <[email protected]> wrote:
>>> tcpdump shows that there is no (zero) data flow between the server and
>>> failed clients when running amcheck on multiple clients at once. Data
>>> does flow when checking a single client.
>>>
>>> This only started about a month ago. Maybe this is a bug?
>>>
>>> On Mon, Jul 25, 2016 at 4:16 PM, Chris Nighswonger
>>> <[email protected]> wrote:
>>>> Here is some snips of output illustrating the problem:
>>>>
>>>>
>>>> backup@scriptor: amcheck -c campus scriptor
>>>>
>>>> Amanda Backup Client Hosts Check
>>>> --------------------------------
>>>> Client check: 1 host checked in 2.372 seconds. 0 problems found.
>>>>
>>>> (brought to you by Amanda 3.3.6)
>>>> backup@scriptor: amcheck -c campus masada
>>>>
>>>> Amanda Backup Client Hosts Check
>>>> --------------------------------
>>>> Client check: 1 host checked in 2.074 seconds. 0 problems found.
>>>>
>>>> (brought to you by Amanda 3.3.6)
>>>> backup@scriptor: amcheck -c campus
>>>>
>>>> Amanda Backup Client Hosts Check
>>>> --------------------------------
>>>> WARNING: scriptor: selfcheck request failed: error sending REQ: write
>>>> error to: Broken pipe
>>>> WARNING: masada: selfcheck request failed: error sending REQ: write
>>>> error to: Broken pipe
>>>>
>>>>
>>>> Server version is 3.3.6
>>>> Client version on scriptor is 3.3.6 and on masada is 3.3.3
>>>>
>>>> When the backup runs over night, the same error appears on these clients.
>>>>
>>>> Any thoughts on what might be going on here?
>>>>
>>>> Kind regards,
>>>> Chris
>
