Bug 498211
| Summary: | Monitoring Not Functional: Missing Stderr.pm and malformed header errors in error_log | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Devan Goodwin <dgoodwin> | ||||
| Component: | Monitoring | Assignee: | Miroslav Suchý <msuchy> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Sklenar <psklenar> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 530 | CC: | cperry, psklenar, whayutin | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | Fixed in the 5.4.0 Release - GA'd 2010-10-27 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-10-28 15:01:36 UTC | Type: | --- | ||||
| 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: | 608752 | ||||||
| Attachments: |
|
||||||
|
Description
Devan Goodwin
2009-04-29 13:27:45 UTC
Did some more investigation and it looks like part of the problems above (the error HTML using rhn-satellite) was related to bug #492150. Upgrading to eventReceivers-2.20.12-1.noarch.rpm manually corrected this problem, the errors listed above are still appearing in error_log, but Scout Config Push completes, and rhn-satellite status does not dump HTML anymore. rhn-satellite restart shows the following: Starting MonitoringScout ... [ FAIL ] This should wanted behaviour when MonitoringScout is not enabled. (It is your situation?) I understand that if it is not enabled it should not write anything (neither OK nor FAIL), but is hard to implement now, since it is currently not made as true service (but one script which start bunch of other scripts which should be standalone services). I'm reluctant to fix this in 530 since it will break a lot of monitoring code. Since the first item is fixed, is it ok for you to close this bug as NOTABUG or DUPLICATE? Monitoring scout is definitely enabled, but I'm still seeing that FAIL when starting the service. Monitoring in general is acting very weird for me, I don't know if it's related. I think I have it working (maybe), some probes are checking in at least (others aren't). Something feels unhealthy but to be honest the errors reported above have stopped, I don't know why. :( I guess that means the only thing left for this ticket is why MonitoringScout shows as FAIL when starting? related or same bug? https://bugzilla.redhat.com/show_bug.cgi?id=498062 the above bug actually breaks monitoring.. so I dont think we can push these off to another release I think different bugs, I wasn't getting that error from NPBootstrap, just the monitoring FAIL above it. Fixed some time ago with commit 2a9119bb5558f6baf8eac173dc5d26b757a73ddd Created attachment 448740 [details]
monitoring works
it works for me,
tried Satellite-5.4.0-RHEL5-re20100910.2
--
verified
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release. RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332 RHEA-2010:0803 - RHN Tools enhancement update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333 RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334 RHEA-2010:0800 - RHN Satellite Server 5.4.0 https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335 Docs are available: http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html Regards, Clifford |