1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
Return-Path: <obnam-support-bounces@obnam.org>
X-Original-To: distix@pieni.net
Delivered-To: distix@pieni.net
Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221])
by pieni.net (Postfix) with ESMTPS id 1D87A41176
for <distix@pieni.net>; Wed, 26 Jul 2017 08:04:51 +0000 (UTC)
Received: from platypus.pepperfish.net (unknown [10.112.101.20])
by yaffle.pepperfish.net (Postfix) with ESMTP id A669C418B0;
Wed, 26 Jul 2017 09:04:50 +0100 (BST)
Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1daHJK-0006ls-Kc; Wed, 26 Jul 2017 09:04:50 +0100
Received: from [10.112.101.21] (helo=mx3.pepperfish.net)
by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
id 1daHJJ-0006lg-I9
for <obnam-support@obnam.org>; Wed, 26 Jul 2017 09:04:49 +0100
Received: from mail-yw0-f172.google.com ([209.85.161.172])
by mx3.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
(Exim 4.89) (envelope-from <mhossbach@gmail.com>) id 1daHJH-0000mx-Po
for obnam-support@obnam.org; Wed, 26 Jul 2017 09:04:49 +0100
Received: by mail-yw0-f172.google.com with SMTP id x125so82820301ywa.0
for <obnam-support@obnam.org>; Wed, 26 Jul 2017 01:04:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=KrUim48ic8A9iKSQQtyVwIbAsEQfPPdJS48kLdhHWMg=;
b=kdD4HaJXsoBok4gEmoy+I5BlKxLHHCZ3vlhUD8Ru+YMnehGqV5YrlJz39ChF8mwOGu
s2vF5qWtosnXkfVpofYcz91+wvGTjHg9w5hA0umFHPy3ubMEhNiELSZyCcb7Gn1rLUMx
a7DnwWZDQc8yORY7zOUGWq78GDYQTIawtUpEk8VQPYykUcZsIEklSkmzMyD/7viylPdk
h5JLJjSR2YbjMqO1w9PyTiDUXOAXbShCLhAKcjOPq/OdmxYgThBhp/vAq9E7s8w8dUb3
TbIgyDk/KnotesofJ/yNlpzDoldyt19ZTiYAN833KBJcJqTx3i7B88JI8nyJRprw9ByM
iI8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=KrUim48ic8A9iKSQQtyVwIbAsEQfPPdJS48kLdhHWMg=;
b=p+j4ELSktgagTtiFLQLX9p7l5fBmnD3+hMQGzHksX11wzJSq2KKyRZx7m5H1IH2CFO
jkj5E6qc4PJIKXq7lxrueq+BFH+VNXnol+DStXGYL3pfRDKnckPE324tizmiTNUWvY+J
dEUaBSSy6Y9ysbM/GGlXu62GexDIjApBnv8bNf2twmYS+XS5BNkT6I3K2tHBClAYkjV+
nbPM2Drn4DIlIQfxZ3eRw71qc3Jo40rDRI/9wzAZpX95eQUSSGWLsONeD3XtSGNjGcx8
0YwevPKjwsx27b6MkdhVkYHzEP3Drn9i6oYZ+OF/JSlaLoFQCwCrCQ3KwVRvUOK5rOah
m0BA==
X-Gm-Message-State: AIVw111gIKYwP9efpmYUm0azrbarfBayunZr1EP/zO3+ECD6sZui8j8p
EiiTH5toKPEKxG6d8lO6NeNXzwhjuR367lk=
X-Received: by 10.129.51.67 with SMTP id z64mr94876ywz.370.1501056276265; Wed,
26 Jul 2017 01:04:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.233.4 with HTTP; Wed, 26 Jul 2017 01:04:35 -0700 (PDT)
From: =?UTF-8?Q?Martin_Ho=C3=9Fbach?= <mhossbach@gmail.com>
Date: Wed, 26 Jul 2017 10:04:35 +0200
Message-ID: <CAPSx4k5WLXBe53WvhUc_3wUMnqbp4BYWZABqNCjyXAo68kO4VA@mail.gmail.com>
To: obnam-support <obnam-support@obnam.org>
Content-Type: text/plain; charset="UTF-8"
X-Pepperfish-Transaction: 8a24-0830-8a08-6047
X-Spam-Score: 2.2
X-Spam-Score-int: 22
X-Spam-Bar: ++
X-Scanned-By: pepperfish.net, Wed, 26 Jul 2017 09:04:49 +0100
X-Spam-Report: Content analysis details: (2.2 points)
pts rule name description
---- ---------------------- --------------------------------------------------
0.5 PPF_RECEIVED_HTTP Received header mentions http
1.0 PPF_FROM_CONTAINS_MAIL The From header contains 'mail'
1.2 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mhossbach[at]gmail.com)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3)
[209.85.161.172 listed in wl.mailspike.net]
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no
trust [209.85.161.172 listed in list.dnswl.org]
1.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source
[209.85.161.172 listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
X-ACL-Warn: message may be spam
X-Scan-Signature: 36255da145478f39910021db1d993052
Subject: GPG failing, Obnam killed
X-BeenThere: obnam-support@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Obnam backup software discussion <obnam-support-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
<mailto:obnam-support-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org>
List-Post: <mailto:obnam-support@obnam.org>
List-Help: <mailto:obnam-support-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
<mailto:obnam-support-request@obnam.org?subject=subscribe>
Sender: obnam-support-bounces@obnam.org
Errors-To: obnam-support-bounces@obnam.org
I keep running into weird behavior of obnam. I have a suspicion as to
the cause, but I still have to ascertain that. For now, I'll describe
what is happening, describe my suspicion and hopefully somebody else
has seen that as well.
Two things keep happening:
* From time to time, without any obvious regularity, obnam simply
shuts down. Output is "terminated", nothing else. I'm not sure in what
state that leaves the repository, though.
* From time to time, the backup is interrupted, and obnam complains
that it GPG failed, because gpg-agent wasn't there.
At first, I thought this was caused by low memory, or a full /tmp,
since I run obnam on an odroid XU4. However, the pattern I start to
see, and which seems to be confirmed by my log files is that this
happens when obnam is running while I logout on that system (from ssh,
by the way). I strongly suspect that this is caused by $CURSEWORD
systemd and its $OTHER_CURSEWORD maintainer, who seems to find it ok
to change default behaviour. $THIRD_CURSEWORD.
Sorry about that.
A few months ago, the systemd default behavior was changed to kill all
remaining processes by a user once that user logs off. Which,
obviously, could mean that a running obnam or gpg-agent would be
killed as well. Apparently, setting KillUserProcesses=no in
/etc/systemd/logind.conf is supposed to change this behaviour of
systemd to the way unix systems have behaved in decades. I still need
to wait for a lengthy backup to finish before I can logout of that
system, and check if that actually solved the matter.
Martin
_______________________________________________
obnam-support mailing list
obnam-support@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
|
