Bug 490783
| Summary: | Disabling Satellite results in incessant cronjob mailings re: "SatCluster.ini" | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Corey Welton <cwelton> |
| Component: | Server | Assignee: | Tomas Lestach <tlestach> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jeff Browning <jbrownin> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 530 | CC: | bperkins, cperry, jsefler |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | sat530 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-09-10 18:49:13 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: | 463877 | ||
|
Description
Corey Welton
2009-03-18 00:56:22 UTC
Well, I *think* that the problem is caused by several recent changes of mine. To be precise with commits: 6288db727ebc4460d2628d060b6d4c8f7fbf42a6 e9b92eaeed70090cec629d8570c1aab19053ab71 Only two days ago I find that some Scout initalization/configuratio is done in code/src/com/redhat/rhn/domain/monitoring/satcluster/SatCluster.java as well. And those two probably collides. So I will had to revert one or other (java or perl) code and revisit both affected bugs. And note that BZ 490235 is probably related as well. Note to myself: After the steps to reproduce I have there: # cat /etc/nocpulse/SatCluster.ini [garbage] So it is not empty. The same content is after and before stop. I'm not able to reproduce it. Can you try it again and give better pointer how to reproduce it? Be sure you have monitoring (and perhaps monitoring scout) enabled. I did so, and repro'd with latest build [root@rlx-0-12 ~]# ls -alF /etc/nocpulse/SatCluster.ini; /usr/sbin/rhn-satellite stop ; ls -alF /etc/nocpulse/SatCluster.ini -rw-r--r-- 1 root root 102 Apr 6 21:20 /etc/nocpulse/SatCluster.ini Shutting down rhn-satellite... Stopping RHN Taskomatic... Stopped RHN Taskomatic. Stopping cobbler daemon: [ OK ] Stopping rhn-search... Stopped rhn-search. Stopping MonitoringScout ... Stopping Dispatcher ... [ OK ] Stopping Dequeuer ... [ OK ] Stopping SputLite ... [ OK ] Stopping NPBootstrap ... [ OK ] Stopping InstallSoftwareConfig ... [ OK ] [ OK ] Stopping Monitoring ... Stopping TSDBLocalQueue ... [ OK ] Stopping AckProcessor ... [ OK ] Stopping Notifier ... [ OK ] Stopping NotifLauncher ... [ OK ] Stopping NotifEscalator ... [ OK ] Stopping GenerateNotifConfig ... [ OK ] [ FAIL ] [ OK ] Stopping httpd: [ OK ] Shutting down osa-dispatcher: [ OK ] Shutting down Jabber router: [FAILED] Done. ls: /etc/nocpulse/SatCluster.ini: No such file or directory Meant to include this - I agree, "SatCluster.ini" does not appear to disappear IF user has not enabled monitoring. I managed to reproduce the problem on an older Satellite 5.3 (compose from March). But the problem doesn't show up on newer versions. I checked: Satellite-5.3.0-RHEL5-re20090414.0 Satellite-5.3.0-RHEL5-re20090422.0 where I didn't see the described misbehaviour. Reproduced this using Satellite-5.3.0-RHEL5-re20090612.0-i386-embedded-oracle.iso Disabling the Sat caused the repeating Cron job as described above. I reproduced described behaviour. Config file /etc/nocpulse/SatCluster.ini gets deleted, when shutting down MonitoringScout (or the whole satellite). Even if monitor-queue creates the config file before using it (when it doesn't exist), it has not the rights to create it when running from cron as nocpulse user. Fix: When the config file was not created, it won't be used. Missing config file does not harm the functionality of monitor-queue. Commit:e525be888ea322e4c503bf99db59f2986ffe4765 Available in composes since Satellite-5.3.0-RHELx-re20090625.0 Verified. No cron emails after shutting down satellite this time. Re-verified build 7/24 Steps described in the problem description did not produce any emails. Trying to force a re-create of the original error (Failed to open /etc/nocpulse/SatCluster.ini: No such file or directory ....), I deleted /etc/nocpulse/SatCluster.ini and manually executed /usr/bin/monitor-queue to see if it would throw the "Fail to open" error. It did not throw the error and therefore did not send any email. In fact, it re-created the file /etc/nocpulse/SatCluster.ini with one line of contents: [garbage] moving to RELEASE_PENDING An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html |