[Bug 1473070] [NEW] sa-update fails to run

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Robie Basak (racb):

Ubuntu 14.04.2 LTS

Spamassassin 3.4.0-1ubuntu2.1

What should happen: 
 sa-update should run on the daily cron job without error

What does happen:
sa-update fails with error:
could not find working mirror, channel failed

The problem is related to perl's wonky threading.  The fork call in sa-
update that utilizes curl/wget/fetch to retrieve data results in the
child process immediately dying from a SIGPIPE signal.

Adding the following at line 132 fixes the problem:

$SIG{PIPE} = 'IGNORE';

I can't vouch for whether that is the RIGHT thing to do, but it seems ok
in context and does allow sa-update to run.

I will attach before and after logs running sa-update as configured by
the package's daily cron task.  (note that between the two runs I also
updated the gpg key).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: spamassassin 3.4.0-1ubuntu2.1 [modified: usr/bin/sa-update]
ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Jul  9 09:05:05 2015
InstallationDate: Installed on 2013-07-19 (720 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: spamassassin
UpgradeStatus: Upgraded to trusty on 2014-08-16 (326 days ago)
modified.conffile..etc.default.spamassassin: [modified]
modified.conffile..etc.spamassassin.local.cf: [modified]
mtime.conffile..etc.default.spamassassin: 2013-10-29T10:31:09.601296
mtime.conffile..etc.spamassassin.local.cf: 2014-08-16T10:23:56.796611

** Affects: spamassassin (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug trusty
-- 
sa-update fails to run
https://bugs.launchpad.net/bugs/1473070
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report.