[Bug 1642402] Re: [ubuntu 16.10] mdmonitor.service does not use syslog or environment file

[Paul White]

** Package changed: ubuntu => mdadm (Ubuntu)

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

Title:
  [ubuntu 16.10] mdmonitor.service does not use syslog or environment
  file

Status in mdadm:
  New
Status in mdadm package in Ubuntu:
  New

Bug description:
  Previously, the standard place to configure mdadm monitoring behavior
  has been /etc/default/mdadm, where DAEMON_OPTIONS and so forth can be
  set. By default these options include "--syslog", and often people add
  a "--test" option there so that they get a test notification when the
  monitoring daemon restarts.

  Currently, the mdmonitor.service unit does not load /etc/default/mdadm
  or provide any other mechanism for customization:

  > cat /lib/systemd/system/mdmonitor.service
  # [...snip...]

  [Unit]
  Description=MD array monitor
  DefaultDependencies=no

  [Service]
  ExecStart=/sbin/mdadm --monitor --scan

  Also, as you can see the monitor no longer defaults to using --syslog;
  I don't know if that was intended as part of the change to systemd or
  was an accident. In any case, it appears that the monitoring results
  aren't logged to any system log.

  Moreover, there's no ability for the user to further customize the
  mdadm arguments.

  Should "EnvironmentFile=-/etc/default/mdadm" be added to the service
  description and DAEMON_OPTIONS passed along to mdadm? Should some
  other option be used for configuration? Currently there's a lot of
  advice on the internet about using /etc/default/mdadm to configure
  monitoring, but that doing any of that now seems to be a no-op.

  Versions: 
  I'm using a fully updated kubuntu 16.10 install.

  mdadm --version
  mdadm - v3.4 - 28th January 2016

  uname -provism
  Linux 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/mdadm/+bug/1642402/+subscriptions