[Bug 1583537] [NEW] systemd shutdown writes non-error message to stderr - causes email to be sent despite 'MailOnlyOnError'

[Graham Clinch]

Public bug reported:

Calling unattended-upgrade from cron with an Unattended-Upgrade
::Automatic-Reboot-Time of "+5".  This causes unattended-upgrades to
run:

'/sbin/shutdown -r +5'

Systemd's shutdown writes an acknowledgement message to stderr:

Shutdown scheduled for Wed 2016-05-18 04:37:49 BST, use 'shutdown -c' to
cancel.

Which cron picks up and emails - but I don't really want to know.

Is there any scope for unattended-upgrades to gobble shutdown's stderr
message?

Or, perhaps this should be logged against systemd, since the shutdown
message isn't really an obvious candidate for stderr?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu May 19 11:14:14 2016
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to unattended-upgrades in Ubuntu.
https://bugs.launchpad.net/bugs/1583537

Title:
  systemd shutdown writes non-error message to stderr - causes email to
  be sent despite 'MailOnlyOnError'

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Calling unattended-upgrade from cron with an Unattended-Upgrade
  ::Automatic-Reboot-Time of "+5".  This causes unattended-upgrades to
  run:

  '/sbin/shutdown -r +5'

  Systemd's shutdown writes an acknowledgement message to stderr:

  Shutdown scheduled for Wed 2016-05-18 04:37:49 BST, use 'shutdown -c'
  to cancel.

  Which cron picks up and emails - but I don't really want to know.

  Is there any scope for unattended-upgrades to gobble shutdown's stderr
  message?

  Or, perhaps this should be logged against systemd, since the shutdown
  message isn't really an obvious candidate for stderr?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 11:14:14 2016
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1583537/+subscriptions