Why do I get JFS Index failures after upgrading to RQM 4.0.3?
Paul Spalitta (81●4●30●37)
| asked Jun 16 '13, 6:56 p.m.
retagged Jun 18 '13, 10:08 a.m. by Amy Laird (165●1●4)
I have upgraded from RQM 3.0.1 to RQM 4.0.3 XX 3 times now (RQM 4.0.3 M4, RQM 4.0.3 RC1 and RQM 4.0.3) and every time I get a failure in the JTS server diagnostics for the JFS Index. I run the prescribed "repotools-jts -reindex" command but it never clears out the issue. The issue seems to clear-out over night after the upgrade (the JFS Index diagnostic stops failing).
Why is this issue occuring?
Is there something else I can do, besides running "repotools-jts -reindex", to clear the issue?
Here is the JTS Server Diagnostics, JFS Index Error Message:
Here is what I get when trying to access https://[JTSServer]/qm/web/console:
|
One answer
|
Well, I figured-out the answer on this final upgrade. After upgrading each time, I also encountered NTP time sync issues in JTS and QM, in addition to the JFS Index issue. I cleared-out those time sync issues in JTS and QM before running the "repotools-jts -reindex" command. What I did not realize (in the prior upgrades) is that CCM (which is installed in our environment but is not being used) was also getting time sync issues. After clearing the time sync issue in CCM, the JFS Index error cleared.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.