On Wed, Jun 17, 2020 at 9:52 PM Ken McDonell <k...@kenj.id.au> wrote: > On 17 June 2020 8:45:12 pm Sam Morris <s...@robots.org.uk> wrote: > > > Package: pcp > > Version: 5.1.1-1 > > Severity: normal > > > > $ systemctl status cron > > ● cron.service - Regular background program processing daemon > > Loaded: loaded (/lib/systemd/system/cron.service; enabled; vendor > > preset: > > enabled) > > Active: active (running) since Wed 2020-06-17 09:03:18 BST; 2min 5s ago > > Docs: man:cron(8) > > Main PID: 3499535 (cron) > > IP: 0B in, 0B out > > Tasks: 49 (limit: 38380) > > Memory: 2.4G > > CPU: 728ms > > CGroup: /system.slice/cron.service > > ├─2725001 /usr/bin/pmie -b -F -P -l > > /var/log/pcp/pmie/fragarach.domain.example/pmie.log -c > > config.default > > ├─3241662 /usr/lib/pcp/bin/pmlogger -N -P -r -T24h10m -c > > config.default -v > > 100mb -m pmlogger_check %Y%m%d.%H.%M > > ... > > Hi Sam, > > Do you expect all these pmloggers to be running? > > We're going to need some help to debug this one. >
I found some clues. Firstly, and most obviously I guess - we should not even be installing these cron jobs - this task is managed by our systemd timers now. Digging into that aspect, it seems the PCP configure script has now started disabling systemd (!) on Debian for reasons I don't follow. Here's a relevant build log: https://buildd.debian.org/status/fetch.php?pkg=pcp&arch=amd64&ver=5.1.1-1&stamp=1590715276&raw=0 This is the relevant PCP configure.ac snippet: dnl Check for systemd services enable_systemd=false AC_MSG_CHECKING([if systemd should be used]) AS_IF([test "x$do_systemd" != "xno"], [ enable_systemd=true PKG_CHECK_VAR([SYSTEMD_SYSTEMUNITDIR], [systemd], [systemdsystemunitdir], [pcp_systemdunit_dir=$SYSTEMD_SYSTEMUNITDIR], [enable_systemd=false]) so, we are (all of a sudden?) taking the enable_systemd=false path and looks like it's all downhill from there. cheers. -- Nathan
