Red Hat Bugzilla – Bug 476851
[ 976930 ] Monitoring failure on Satellite with external db (where db name != db instance name)
Last modified: 2009-12-07 07:02:38 EST
+++ This bug was initially created as a clone of Bug #226915 +++
Escalated to Bugzilla from IssueTracker
--- Additional comment from email@example.com on 2007-02-01 19:33:40 EDT ---
Customer is running 4.1 satellite and I believe enountered this bug (or a similar bug):
They are using an external database and after installation, their DB name and password were swapped only in thier cluster.ini file.
After correcting the swapped username/password the error still persists. I've had the customer try to run the enable monitoring script from the rhn-upgrade package, but this didn't help.
I've attached a satellite-debug, a sysreport, the output from starting monitoring, as well as the latest monitoring logs.
Commited as 1cc24e3f4081c37f5625279b02ab4c902436e3c2
Spacewalk 0.5 released.
This problem happen to not be fixed.
Java code rewrite the value set by installer.
Fixed in spacewalk git in commits:
commit 372587c40d5935948aa3632ddd0beec068244ee2 as well
Drop unneeded synonyms during schema upgrade.
spacewalk.git master: cf64dd8d756aa1797618eb6f2c7cd8dade60d96f
Spacewalk 0.7 released.