Description of problem:
The pmlogger service doesn't really start unless it is also enabled.
Steps to Reproduce:
1. Disable pmlogger
# systemctl disable pmlogger
2. Start it
# systemctl start pmlogger
The service announces itself as active:
# systemctl status pmlogger
● pmlogger.service - Performance Metrics Archive Logger
Loaded: loaded (/usr/lib/systemd/system/pmlogger.service; disabled)
Active: active (exited) since Mon 2015-01-26 10:33:46 EET; 1s ago
Process: 3719 ExecStart=/usr/share/pcp/lib/pmlogger start (code=exited, status=0/SUCCESS)
Main PID: 3719 (code=exited, status=0/SUCCESS)
But there aren't any pmlogger processes:
# pgrep pmlogger
(It is normal that "/usr/share/pcp/lib/pmlogger start" exits.)
pmlogger should be running after starting the service.
Enabling pmlogger with "systemctl enable pmlogger" will allow it to start. I think the /usr/share/pcp/lib/pmlogger script actually checks whether pmlogger is enabled (via chkconfig which redirects to systemctl is-enabled) and does nothing if it isn't.
This was frustrating to figure out.
Just FYI - this is a duplicate of 1131022, from RHEL6 - I'll not mark it as such though since thats a different product & I think might muck up your issue tracking here?
See commen #c2 there in particular.
> this is a duplicate of bug 1131022
> I'll not mark it as such though since thats a different product & I think might muck up your issue tracking here?
I don't know how we track bugs here that affect multiple products. If it's ok with you, I'd prefer to leave this open here until we can forget about from a Cockpit perspective.
I'll add a dependency.
> If it's ok with you, I'd prefer to leave this open here
No problem at all - I expect to tackle this one in the short term, and will add a note to both bugs when done.
Note that the behavior with "systemctl" is worse than with "service": At least "service pmlogger status" tells you that it isn't running, while "systemctl status pmlogger" will incorrectly state that pmlogger is active.
pcp-3.10.4-1.fc22 has been submitted as an update for Fedora 22.
pcp-3.10.4-1.fc21 has been submitted as an update for Fedora 21.
pcp-3.10.4-1.fc20 has been submitted as an update for Fedora 20.
pcp-3.10.4-1.el5 has been submitted as an update for Fedora EPEL 5.
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing pcp-3.10.4-1.el5'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
pcp-3.10.4-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.10.4-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.10.4-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.10.4-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.