John, the errors I showed were from adding a -v to the /bin/sh and doing sudo spamassissin. RW, thanks for looking up the cURL error. I was so focused on googling, I failed to RTM. I don’t know why, but I have something to focus my investigation on.
> On May 14, 2016, at 4:18 AM, RW <rwmailli...@googlemail.com> wrote: > > On Fri, 13 May 2016 14:57:02 -0700 > Bill Keenan wrote: > >> Googling this turns up some speculation…are the 4 curls failing >> because of a mirror problem? Shame on me for not watching…I do not >> know when this error started to occur. If there is a fix, where is it >> documented? >> >> Bill >> >> SpamAssassin version 3.4.1 >> running on Perl version 5.20.2 >> >> # Update >> umask 022 >> env -i LANG="$LANG" PATH="$PATH" start-stop-daemon \ >> --chuid debian-spamd:debian-spamd --start \ >> --exec /usr/bin/sa-update -- -v \ >> --gpghomedir /var/lib/spamassassin/sa-update-keys 2>&1 >> Update available for channel updates.spamassassin.org: 1742071 -> >> 1743481 http: (curl) GET http://sa-update.secnap.net/1743481.tar.gz, >> FAILED, status: exit 23 http: (curl) GET >> http://www.sa-update.pccc.com/1743481.tar.gz, FAILED, status: exit 23 >> http: (curl) GET http://sa-update.space-pro.be/1743481.tar.gz, >> FAILED, status: exit 23 http: (curl) GET >> http://sa-update.dnswl.org/1743481.tar.gz, FAILED, status: exit 23 >> channel: could not find working mirror, channel failed Update failed, >> exiting with code 4 >> > > From the curl man page: > > 23 Write error. Curl couldn't write data to a local filesystem or > similar.
