OI connector does not successfully restart

book

Article ID: 197193

calendar_today

Updated On:

Products

DX Operational Intelligence

Issue/Introduction

We observed items missing from Operational intelligence in the WSS tenant. We believed this could be due to the data not being moved properly by the OI connector to OI. We attempted to restart the OI connector with the command sudo service caperfcenter_oi restart . When the OI service attempted to restart we see this error.
Job for caperfcenter_oiconnector.service failed because the control process exited with error code. See "systemctl status caperfcenter_oiconnector.service" and "journalctl -xe" for details.


We don't see obvious errors in the OIConnector.log but in wrapper-20200812.log we see the following error

INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64/jre/bin/java
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  | Launching a JVM...
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  | Java Command Line:
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[0] : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64/jre/bin/java
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[1] : -XX:MaxMetaspaceSize=128m
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[2] : -Dorg.apache.jasper.compiler.disablejsr199=true
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[3] : -Xms1024m
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[4] : -Xmx8192m
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[5] : -Djava.library.path=../lib
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[6] : -classpath
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[7] : ../lib/wrapper.jar:/opt/CA//OIConnector/oinet-connector.jar
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[8] : -Dwrapper.key=po8-P_jNDHMp0GVhiUDpT7xl_o47Vwu1
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[9] : -Dwrapper.port=32000
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[10] : -Dwrapper.jvm.port.min=31000
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[11] : -Dwrapper.jvm.port.max=31999
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[12] : -Dwrapper.disable_console_input=TRUE
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[13] : -Dwrapper.pid=8156
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[14] : -Dwrapper.version=3.5.27-pro
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[15] : -Dwrapper.native_library=wrapper
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[16] : -Dwrapper.arch=x86
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[17] : -Dwrapper.service=TRUE
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[18] : -Dwrapper.cpu.timeout=10
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[19] : -Dwrapper.jvmid=5
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[20] : -Dwrapper.lang.domain=wrapper
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[21] : -Dwrapper.lang.folder=../lang
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[22] : org.tanukisoftware.wrapper.WrapperSimpleApp
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[23] : com.ca.im.oinet.connector.AXAIntegrationMain
INFO   | jvm 5    | 2020/08/12 18:05:09 | wrapper  |   Command[24] : -XX:-HeapDumpOnOutOfMemoryError
ADVICE | wrapper  | 2020/08/12 18:05:09 |
ADVICE | wrapper  | 2020/08/12 18:05:09 | ------------------------------------------------------------------------
ADVICE | wrapper  | 2020/08/12 18:05:09 | Advice:
ADVICE | wrapper  | 2020/08/12 18:05:09 | Usually when the Wrapper fails to start the JVM process, it is because
ADVICE | wrapper  | 2020/08/12 18:05:09 | of a problem with the value of the configured Java command.  Currently:
ADVICE | wrapper  | 2020/08/12 18:05:09 | wrapper.java.command=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64/jre/bin/java
ADVICE | wrapper  | 2020/08/12 18:05:09 | Please make sure that the PATH or any other referenced environment
ADVICE | wrapper  | 2020/08/12 18:05:09 | variables are correctly defined for the current environment.
ADVICE | wrapper  | 2020/08/12 18:05:09 | ------------------------------------------------------------------------
ADVICE | wrapper  | 2020/08/12 18:05:09 |
FATAL  | wrapper  | 2020/08/12 18:05:10 | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2020/08/12 18:05:10 |   There may be a configuration problem: please check the logs.

This was all working properly before we upgraded the NetOps environment to 20.2. We attempted exporting /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64/jre to $JAVA_HOME

Environment

Release : 1.3

Component : CA DOI OI CONNECTOR

Resolution

The Java version was updated on the OI connector. Once the connector was restarted the wrapper.conf file was pointing to the improper location for $JAVA_HOME. Updated the config file with the proper path for the new jdk version and it was able to start correctly.