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.
Let's start with.
1. The contents of /etc/PCP/pmlogger ... tarball would be best
2. Output from $ sudo systemctl status pmlogger
3. Output from $ sudo systemctl status pmlogger_check
4. The contents of /var/log/pcp/pmlogger/pmlogger_daily.log* (maybe 1 or
2 files)
5. The contents of /etc/cron.d/pcp* (maybe 0, 1 or more files)
Also, was this a fresh install of pcp-5.1.1 or did you upgrade (and if
upgrade, do you know what the previous pcp version was)?
Fell free to respond to me directly if you don't want to spam the PCP
list and Debian bug tracking system.
