LMS 4.2.5 DCRServer stuck in state: Waiting to initialize
One of my Customer has a LMS 4.2.5 server. The server has been installed some years ago. It has been worked fine until now.
The Customer wanted to use User Tracking quick report but he got the error message: "Application error".
I have done the following troubleshooting steps:
I have checked the processes and realized that DCRServer has been stucked in state: Waiting to initialize. And, of course there were some processes in Never started state.
As this is an old story, so I have double checked the following files:
/opt/CSCOpx/MDC/tomcat/shared/lib/ctm_config.txt /opt/CSCOpx/MDC/tomcat/webapps/cwhp/WEB-INF/lib/ctm_config.txt /opt/CSCOpx/MDC/tomcat/lib/ctm_config.txt but they had proper content.
I have checked /opt/CSCOpx/lib/classpath/md.properties as well. It is also OK.
On the server the hostname did not changed.
On the server there is a corporate certificate installed and it is still valid.
I have tried to restart the server but no luck.
I have enabled debugging in NMSROOT\lib\classpath\com\cisco\nm\dcr\log4j-dcr.properties file.
Restarted daemon manager.
During starting processes I have realized that DCRServer has beed started correctly, but after a while, when around diskWacher process starts then the state of DCRServer changed to Waiting to initialize.
In dcr.log file I can see the following ERROR message:
[ Thu Nov 08 23:26:02 CET 2018 ] [main] ERROR CTM.client - ERR_IN_WRITING_REQUEST, BEFORE_INVOC, Error in writing the request, Binary mode java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl) [ Thu Nov 08 23:26:12 CET 2018 ] [main] DEBUG CTM.client - RPC, EncodingStyle = CTMConstants.CTM_BINARY [ Thu Nov 08 23:26:12 CET 2018 ] [main] DEBUG CTM.common - classLocation is: jar:file:/opt/CSCOpx/MDC/tomcat/webapps/cwhp/WEB-INF/lib/ctm.jar!/com/cisco/nm/xms/ctm/common/CTMConfig.class [ Thu Nov 08 23:26:12 CET 2018 ] [main] ERROR CTM.client - ERR_IN_WRITING_REQUEST, BEFORE_INVOC, Error in writing the request, Binary mode java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl) [ Thu Nov 08 23:26:23 CET 2018 ] [main] DEBUG CTM.client - RPC, EncodingStyle = CTMConstants.CTM_BINARY [ Thu Nov 08 23:26:23 CET 2018 ] [main] DEBUG CTM.common - classLocation is: jar:file:/opt/CSCOpx/MDC/tomcat/webapps/cwhp/WEB-INF/lib/ctm.jar!/com/cisco/nm/xms/ctm/common/CTMConfig.class
The above error message is repeating.
I'm at this point now. What should I check further?
Could you please help me troubleshooting this issue?
To optimize the database description (DBD) packet exchange between two OSPF neighbors, use the compatible rfc5243 in router configuration mode or address family configuration mode for OSPFv3 AF. To disable RFC5243 optimization, use the no form of this com...
We said always that OSPF is a link-state routing protocol.For most engineer stuying CCNA or CCNP, OSPF is misunsdertanding.In reality, OSPF is a link-state routing protocol only within an area (intra-area); but almost a distance-vector routing protocol be...
A brief difference between ISIS and OSPF link state protocolsISIS and OSPF belongs to the same routing protocol family Link State, but if you study the two routing protocols, you will find several differences, in this article you will get the answer about...
The OSPF Type-2 LSA is one of the misunderstanding LSA among all the popular LSAs in OSPF , most people learns that this kind of LSA (Type-2) is generated by DR the Designated Router in a broadcast segment, for example when two or more than two routers ar...
Table of Contents
RADIUS has been the de-facto protocol for Remote Access Authentication for decades. RADIUS/UDP as defined by RFC 2865 has traditionally used MD5 for authentication and integrity. Unfortunately, successful attacks ...