Red Hat Bugzilla – Bug 1375415
pmlogger_check failed due to /etc/pcp/pmlogger/control.d/local.rpmsave
Last modified: 2016-10-25 20:58:09 EDT
Description of problem: "pmlogger_check failed" messages in syslog because there are multiple primary logger control files in /etc/pcp/pmlogger/control.d. Presumably the .rpmsave version was left over after an upgrade because it had been modified (I appended -t 30s some time in the past). These files probably should be marked %config(noreplace) in the spec I guess, but after an upgrade we'd end up with local.rpmnew, which would have the same problem. Version-Release number of selected component (if applicable): 3.11.5-1 (not yet released) $ grep LOCALHOSTNAME /etc/pcp/pmlogger/control.d/* /etc/pcp/pmlogger/control.d/local:LOCALHOSTNAME y n PCP_LOG_DIR/pmlogger/LOCALHOSTNAME -r -T24h10m -c config.default /etc/pcp/pmlogger/control.d/local.rpmsave:LOCALHOSTNAME y n PCP_LOG_DIR/pmlogger/LOCALHOSTNAME -r -T24h10m -c config.default -t 30s
$ cat /var/log/pcp/pmlogger/pmlogger_check.log Restarting primary pmlogger for host "local:" ... process exited! pmlogger_check: Error: failed to restart pmlogger Current pmlogger processes: UID PID PPID C STIME TTY TIME CMD Contents of pmlogger output file "pmlogger.log" ... Log for pmlogger on kilcunda started Tue Sep 13 13:55:05 2016 ... trimmed ... Log finished Tue Sep 13 13:55:05 2016 pmlogger_check: [/etc/pcp/pmlogger/control.d/local.rpmsave:3] Error: Cannot start more than one pmlogger instance for archive directory "/var/log/pcp/pmlogger/kilcunda" ... logging for host "local:" unchanged
Yeah, I think this is mainly just something that has to be watched for during an RPM upgrade ... but, perhaps we could also ignore any files suffixed with .rpmsave or .rpmnew in that subdirectory? cheers.
Ignore them, but also warn. We could also have a %postin script that checks and warns too.
fixed in upstream commit ba1355032bfdc91bfabc39d3a2255015fa92ccb9
pcp-3.11.5-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d14b648a5
pcp-3.11.5-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca5c041e73
pcp-3.11.5-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b32e6fdc78
pcp-3.11.5-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-63742f1d5b
pcp-3.11.5-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.5-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.5-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.5-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.