Attempted cron spam from ubuntu-repository-cache-sync

Bug #1554894 reported by Paul Gear
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Repository Cache Charm
Fix Released
Undecided
Unassigned
ubuntu-repository-cache (Juju Charms Collection)
Fix Released
Undecided
Unassigned

Bug Description

The ubuntu-repository-cache-sync job is producing emails from its regular cron runs. These aren't going anywhere because something (possibly a bug in another charm) has caused the system not to create /etc/aliases.db, meaning that postfix is unable to deliver local mail. If it were, this would be accumulating in /var/mail/www-sync.

If aliases.db is created, the contents of the emails can be seen (with most header noise removed):

From: <email address hidden> (Cron Daemon)
To: <email address hidden>
Subject: Cron <www-sync@juju-UUID-machine-1> juju-run ubuntu-repository-cache/0 /var/lib/juju/agents/unit-ubuntu-repository-cache-0/charm/hooks/ubuntu-repository-cache-sync
Date: Mon, 7 Mar 2016 23:08:33 +0000 (UTC)

Site archive_ubuntu_com already enabled
 * Reloading web server apache2
 *
start: Job is already running: squid-deb-proxy

Tags: canonical-is
Revision history for this message
Haw Loeung (hloeung) wrote :

For our other environments, we use basenode which sets up postfix as well as calls 'newaliases' to create /etc/aliases.

Paul Gear (paulgear)
tags: added: canonical-is
Revision history for this message
Haw Loeung (hloeung) wrote :

https://code.launchpad.net/~hloeung/ubuntu-repository-cache/system-mail-admin/+merge/427338 adds the ability to set an email address for such emails to be sent to.

We're also not reloading apache2 as often with various recent changes such as updating the charm to use the Reactive framework. I'm also not seeing as much cron spam from the various units deployed in the field.

As such, I'm marking this bug as resolved.

Changed in ubuntu-repository-cache:
status: New → Fix Released
Changed in ubuntu-repository-cache (Juju Charms Collection):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.