Bug#894125: amanda-server: error=write error to: Broken pipe

2018-03-28 Thread Jose M Calhariz
Hi,

This error was one shot or happen every day?

Have you look into the amanda logs files on server?

Have you look into the amanda logs files of the failing clients?

Kind regards
Jose M Calhariz



Bug#894125: amanda-server: error=write error to: Broken pipe

2018-03-27 Thread Jose M Calhariz
Please send the logs to my email address. I will look into this night.

Kind regards
Jose M Calhariz


On March 27, 2018 9:39:35 AM GMT+01:00, "Tobias Köck"  
wrote:
>Hi Jose,
>
>it happens every time after I rebooted the system yesterday. I haven't 
>updated amanda-server so far.
>
>I have looked in into the server logs (see output). I haven't yet
>looked 
>into the failing clients.
>
>I can send you the logs to your personal email if it would help.
>
>Greetings
>Tobias
>On 27.03.2018 08:32, Jose M Calhariz wrote:
>> Hi,
>>
>> This error was one shot or happen every day?
>>
>> Have you look into the amanda logs files on server?
>>
>> Have you look into the amanda logs files of the failing clients?
>>
>> Kind regards
>> Jose M Calhariz
>>
>>
>>
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#894125: amanda-server: error=write error to: Broken pipe

2018-03-27 Thread Tobias Köck

Hi Jose,

it happens every time after I rebooted the system yesterday. I haven't 
updated amanda-server so far.


I have looked in into the server logs (see output). I haven't yet looked 
into the failing clients.


I can send you the logs to your personal email if it would help.

Greetings
Tobias
On 27.03.2018 08:32, Jose M Calhariz wrote:

Hi,

This error was one shot or happen every day?

Have you look into the amanda logs files on server?

Have you look into the amanda logs files of the failing clients?

Kind regards
Jose M Calhariz








Bug#894125: amanda-server: error=write error to: Broken pipe

2018-03-26 Thread tkoeck
Package: amanda-server
Version: 1:3.3.9-5
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
After an update and a reboot from Debian 9 I get a lot of errors for
some servers.

I haven't changed anything on the configuration.

---
amstatus a2g-2

Using /var/lib/amanda/a2g-4/log/amdump
>From Mon Mar 26 13:13:36 CEST 2018

artifactory.somecompany.org:/data
0   2148065k finished (14:13:43)
artifactory.somecompany.org:/etc
0   542k finished (13:45:59)
cdbslave.blubb.de:/etc
0  9377k finished (13:44:40)
cdbslave.blubb.de:/sbin
0  3780k finished (13:45:19)
cdbslave.blubb.de:/var
0 75688k finished (13:46:28)
ci.blubb.de:/etc
0  9840k finished (13:45:34)
ci.blubb.de:/home
0277519k finished (13:48:52)
ci.blubb.de:/ontram_files
022k finished (13:44:04)
ci.blubb.de:/root
0   3603743k finished (14:05:28)
ci.blubb.de:/u1
0  10474660k finished (15:24:25)
ci.blubb.de:/usr
0   2835474k finished (14:18:17)
ci.blubb.de:/var
0   2033373k finished (13:53:11)
ci.somecompany.org:/etc
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/home
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/registry
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/root
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/u1
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/usr/local/sbin
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/var/lib/docker
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/var/lib/jenkins
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
ci.somecompany.org:/var/lib/mysql/backup
0 failed: planner: [Request to ci.somecompany.org failed: error sending
REQ: write error to: Broken pipe]
connect.blubb.de:/etc
0 failed: planner: [Request to connect.blubb.de failed: error sending
REQ: write error to: Broken pipe]
connect.blubb.de:/home
0 failed: planner: [Request to connect.blubb.de failed: error sending
REQ: write error to: Broken pipe]
connect.blubb.de:/root
0 failed: planner: [Request to connect.blubb.de failed: error sending
REQ: write error to: Broken pipe]

---
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018: thd-0x562a6f59b400:
planner: security_stream_seterr(0x562a701d33b0, write error to: Broken
pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_stream_seterr(0x562a701c2480,
write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_stream_seterr(0x562a70211fe0,
write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_stream_seterr(0x562a701ba420,
write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_stream_seterr(0x562a701ca620,
write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_stream_seterr(0x562a70266330,
write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_seterror(handle=0x562a7025dd50,
driver=0x7f135849da00 (BSDTCP) error=write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_seterror(handle=0x562a7025dd50,
driver=0x7f135849da00 (BSDTCP) error=error sending REQ: write error to:
Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_stream_seterr(0x562a70266330,
write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_stream_seterr(0x562a70141330,
write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_seterror(handle=0x562a702627b0,
driver=0x7f135849da00 (BSDTCP) error=write error to: Broken pipe)
planner.20180326121505.debug:Mon Mar 26 12:17:15 2018:
thd-0x562a6f59b400: planner: security_seterror(handle=0x562a702627b0,
driver=0x7f135849da00 (BSDTCP) error=error sending REQ: write error
---

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)