RRC Server "Appears" Offline
After upgrading to version 4.0, we noticed a strange indication. We can go successfully to any instance of the deployment:
- https://server1:9443/jts
- https://server2:9443/rm
- https://server3:9443/ccm
- https://server4:9443/qm
However from each of these instances (in the web browser), including from the RM instance itself, when you click the drop down next to the "Home" button to try to navigate to various projects, the RM instance would appear offline with a message: "This server is offline or unreachable".
Any advice on what may have went wrong and how to troubleshoot and fix this issue?
Accepted answer
Another approach you could try is checking if the server/conf/friendsconfig.rdf file is correct. See: https://jazz.net/forum/questions/80867/why-does-lifecycle-project-administration-hang-after-upgrading-a-clm-301-repository-to-clm-40
Comments
Yes, we can reach the server directly. I will put the suspicious log entry after this.
Here is what we see in the log that will provide some clue.
java.lang.NullPointerException at com.ibm.rdm.fronting.server.services.discovery.internal.DiscoveryServiceInternal.buildHomeMenuDocument(DiscoveryServiceInternal.java:387) ... 2012-07-09 16:28:02,932 [http-bio-9443-exec-27] ERROR ibm.rdm.fronting.server.headers.services.LinkTypes - CRRRS4120I << HTTP/1.1 500 Internal Error 2012-07-09 16:28:02,933 [http-bio-9443-exec-27] ERROR ibm.rdm.fronting.server.headers.services.LinkTypes - CRRRS4120I << [Request >>] GET https://server2:9443/rm/discovery/home-menu HTTP/1.1
Hi Ketut,
I would 1. Check if the friends and registration information is correct. Especially check the friendsconfig.rdf file for suspicious entries. 2. Create a PMR with support if you have support or a work item if not. Please feel free to subscribe me if you create a work item.
HI Ralph,
Thanks for the help and advise. We found the problem and fixed it.
We checked the friends, fronting, and registration information on RRC. We found that there is setting for RDMWebAppFoundationProjectDashboard that is not defined.
We found that it's not defined after comparing it with the manual upgrade guide at https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_upgrading_40.html.
When we made our upgrade, we had used the automatic upgrade script, but somehow it seems the automatic upgrade script does not defined this particular value.
Hi Ketut, thanks for sharing!
One other answer
In an experimental upgrade I saw an effect like this, but it disappeared. Not sure why, maybe after a reboot.
Have you checked the application diagnostics and the registered applications? Are there any indications in the logs? Could there be a certificate issue between the servers?
If you can't get an answer soon. I would consider to call support.