[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tarsnap fails with broken pipe in systemd timer unit

To: Simon Levermann <simon@slevermann.de>
Subject: Re: Tarsnap fails with broken pipe in systemd timer unit
From: Andrea Biscuola <a@abiscuola.com>
Date: Tue, 08 Oct 2019 19:14:42 +0200
Cc: tarsnap-users@tarsnap.com
In-reply-to: <3f1b0831-e015-6044-4a21-56696b41be3e@slevermann.de>
References: <3f1b0831-e015-6044-4a21-56696b41be3e@slevermann.de>
Reply-to: a@abiscuola.com

Hi Simon

On October 8, 2019 6:53:29 PM GMT+02:00, Simon Levermann <simon@slevermann.de> wrote:
>
>Okt 08 18:45:27 slevermann.de tarsnap.sh[17247]: tarsnap: fprintf:
>Broken pipe
>Okt 08 18:45:27 slevermann.de tarsnap.sh[17247]: tarsnap: Error listing
>archives

It seems it can't write to a socket or a particular file descriptor? Doesn't systemd put some limits on what a service can do?

Couldn't it be something related to SELinux or similar?

Andrea

Follow-Ups:
- Re: Tarsnap fails with broken pipe in systemd timer unit
  - From: Simon Levermann <simon@slevermann.de>

References:
- Tarsnap fails with broken pipe in systemd timer unit
  - From: Simon Levermann <simon@slevermann.de>

Prev by Date: Tarsnap fails with broken pipe in systemd timer unit
Next by Date: Re: Tarsnap fails with broken pipe in systemd timer unit
Previous by thread: Tarsnap fails with broken pipe in systemd timer unit
Next by thread: Re: Tarsnap fails with broken pipe in systemd timer unit
Index(es):
- Date
- Thread