Kevin A. McGrail schrieb am 10.01.2018 um 15:09:
>
> Anyone having issues with Sha1 failures on their machines on sa-updates?
>
> Anyone familiar with sa-update.cron so we can try and get more data
on this bug below?
I'm using sa-update.cron from CentoOS 7. Here it failed once on
09-Jan-2018 04:49:40.
This cron script collects information about configured update channels
and builds a command line for sa-update:
sa-update --channel chan1 --channel chan2 --channel chanN --gpgkey
keyid1 --gpgkey keyid2 --gpgkey keyidN
Here, the script failed once with:
From: "(Cron Daemon)" <r...@wombaz.de>
To: r...@wombaz.de
Subject: Cron <root@mail> /usr/share/spamassassin/sa-update.cron 2>&1 |
tee -a /var/log/sa-update.log
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
Precedence: bulk
X-Cron-Env: <XDG_SESSION_ID=717247>
X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/0>
X-Cron-Env: <LANG=en_US.UTF-8>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20180109034940.15650a0...@mail.wombaz.de>
Date: Tue, 9 Jan 2018 04:49:40 +0100 (CET)
gpg: process '/usr/bin/gpg' finished: exit 1
error: GPG validation failed!
The update downloaded successfully, but the GPG signature verification
failed.
channel: GPG validation failed, channel failed
09-Jan-2018 04:49:40: SpamAssassin: Update available, but download or
extract failed
Corresponding /var/log/sa-update.log:
01-Jan-2018 04:55:06: SpamAssassin: Update processed successfully
02-Jan-2018 05:02:10: SpamAssassin: Update processed successfully
03-Jan-2018 05:41:49: SpamAssassin: Update processed successfully
04-Jan-2018 05:19:14: SpamAssassin: Update processed successfully
05-Jan-2018 05:35:52: SpamAssassin: Update processed successfully
06-Jan-2018 06:05:34: SpamAssassin: Update processed successfully
07-Jan-2018 04:22:39: SpamAssassin: Update processed successfully
08-Jan-2018 05:35:54: SpamAssassin: Update processed successfully
gpg: process '/usr/bin/gpg' finished: exit 1
error: GPG validation failed!
The update downloaded successfully, but the GPG signature verification
failed.
channel: GPG validation failed, channel failed
09-Jan-2018 04:49:40: SpamAssassin: Update available, but download or
extract failed
10-Jan-2018 05:59:12: SpamAssassin: Update processed successfully
The above return code is the return code from sa-update.
I have 3 channels configured. The error probably occurred with the
spamassassin channel, because it is the only one that has current file
dates in the *.cf files. The others are from last year.
As far as I see it, the update package on 09-Jan-2018 was defective
(incomplete?) or had no or invalid gpg signature.
Didn't happen again since. If the files are unchanged on the server
since then, may be they were in the process of being uploaded by the
backend while already downloaded by clients, so sa-update got an
incomplete file but download returned success.
Alex
