[Pkg-monitoring-maintainers] Bug#790951: restarts gmond at bad time during dist-upgrade (was: Re: Bug#802499: testing plugin packages during upgrades)

[Andreas Beckmann]

[ moving discussion to #790951 ]

On 2015-10-20 20:36, Daniel Pocock wrote:
> During an upgrade from wheezy to jessie, I saw it happen with
> ganglia-monitor and ganglia-modules-linux

> The details are explained in
> https://bugs.debian.org/791403

Do you have an upgrade log? I cannot reproduce this in piuparts,
always g-m is configured first, and g-m-l afterwards:

That's from piuparts test wheezy2jessie, amd64, --install-recommends.
The test got rerun yesterday :-), but the March logfile without
--install-recommends shows the same. I can provide the full logfiles if
needed.

The first command output is from
  apt-get install ganglia-modules-linux
in wheezy, the second from
  apt-get distupgrade
to jessie.
No services get started due to policy-rc.d, but you see what was attempted:

$ grep -C3 'Setting up ganglia'
wheezy2jessie-rcmd/main/pass/ganglia-modules-linux_1.3.6-1.log
  Setting up libapr1 (1.4.6-3+deb7u1) ...
  Setting up libpython2.7 (2.7.3-6+deb7u2) ...
  Setting up libganglia1 (3.3.8-1+nmu1) ...
  Setting up ganglia-monitor (3.3.8-1+nmu1) ...
  Adding system user: ganglia.
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up ganglia-modules-linux (1.3.4-6) ...
  invoke-rc.d: policy-rc.d denied execution of restart.
0m43.6s DEBUG: Command ok: ['chroot', '/tmp/piupartss/tmpfbZyHc',
'apt-get', '-y', 'install', 'ganglia-modules-linux']
0m43.6s INFO: Running scripts post_install
--
  Setting up ucf (3.0030) ...
  Setting up xz-utils (5.1.1alpha+20120614-2+b3) ...
  Setting up libganglia1 (3.6.0-6) ...
  Setting up ganglia-monitor (3.6.0-6) ...
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libpam-cap:amd64 (1:2.24-8) ...
  Setting up psmisc (22.21-2) ...
  Setting up ganglia-modules-linux (1.3.6-1) ...
  invoke-rc.d: policy-rc.d denied execution of restart.
  Processing triggers for libc-bin (2.19-18+deb8u1) ...
  Processing triggers for systemd (215-17+deb8u2) ...

So maybe another failure happened during your upgrade?
Or maybe I need a bigger system (more packages) to upgrade ...


Andreas