Bug 1131022
| Summary: | pmlogger service not starting when not chkconfig'ed on | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marko Myllynen <myllynen> | |
| Component: | pcp | Assignee: | Nathan Scott <nathans> | |
| Status: | CLOSED ERRATA | QA Contact: | Miloš Prchlík <mprchlik> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.6 | CC: | brolley, mbenitez, mcermak, mprchlik | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | pcp-3.10.3-1.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the PCP pmlogger daemon start script started the daemon only if the pmlogger service was enabled by the "chkconfig on" command. Consequently, the daemon silently failed to start when the service was disabled. With this update, additional diagnostics have been added to the start script. Now, when attempting to start the pmlogger daemon with the pmlogger service disabled, the user is properly informed and given instructions on how to eliminate the problem.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1186012 (view as bug list) | Environment: | ||
| Last Closed: | 2015-07-22 06:24:27 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1185755, 1186012 | |||
|
Description
Marko Myllynen
2014-08-18 11:57:50 UTC
I agree we should definitely allow this - I think the current behaviour is a remnant from other operating systems (IRIX). There's code there to issue a diagnostic but its either not being activated (pmie case) or not all there (in the pmlogger case) - both should be fixed up. Tagging this for 6.7 and will fix upstream soon - thanks Marko. There's some concern / on-going discussion upstream about the consequences of starting pmloggers that are not being properly tracked (in terms of not having logs rotated, compressed, and so on) and things like cronjobs and helper scripts being closely reliant on chkconfig state to know whether they should operate. I'll keep on working on it (we have a separate bug open as a systemd-variant of this BZ), but there's no short-term easy solution.
Since some deadlines are close for RHEL6.7 and I think we should definitely do something to help the major problem here (i.e., the service silently failing to start) - so I've tackled the diagnostics/reporting side of the problem in the interim, as follows:
# /sbin/chkconfig pmlogger off
# service pmlogger start
/etc/rc.d/init.d/pmlogger: Warning: Performance Co-Pilot archive logger(s) are disabled.
To enable pmlogger, run the following as root:
# /sbin/chkconfig pmlogger on
# /sbin/chkconfig pmlogger on
# service pmlogger start
Starting pmlogger ...
#
So, the punter no longer has to spend ages trying to figure out why the start script didn't do anything. I'll track the remainder of the problem under the Fedora BZ, and a future rebase for RHEL will pick up other work done there to further improve the situation, as soon as it becomes available.
Verified for build pcp-3.10.3-3.el6. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1300.html |