Related Tips & Info
Wikis - Page

ovjboss is NOT_RUNNING Exit(127) after upgrade to 2019.05 bridge release

Danail Delsizov
3 Likes

Symptoms

 

At some systems, migrating NNMi from 10.20 to 2019.05 can leave the jboss service and nnmaction Unstartable with Exit (127).

During the upgrade the following can be observed during post-install config and in nnm-install-config.log.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!  Start all processes
!!  Start all processes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Sunday, May 10, 2020 11:28:16 AM AST - INFO: The execution directory = /opt/OV/bin
Sunday, May 10, 2020 11:28:16 AM AST - INFO: Waiting (up to 14400 seconds) for process to terminate
Sunday, May 10, 2020 11:28:18 AM AST - INFO: stdout>  Name                   PID  State          Last Message(s) 
Sunday, May 10, 2020 11:28:18 AM AST - INFO: stdout>  nnmtrapreceivermd    22315  RUNNING        Initialization complete. Trap Receiver is running.  
Sunday, May 10, 2020 11:28:20 AM AST - INFO: stdout>  nmsdbmgr             22314  RUNNING        Initialization complete. 
Sunday, May 10, 2020 11:28:20 AM AST - INFO: stderr>  ovjboss                  -  NOT_RUNNING    - Exit(127)
Sunday, May 10, 2020 11:28:20 AM AST - INFO: stderr>  nnmaction                -  UNSTARTABLE    - 
Sunday, May 10, 2020 11:28:20 AM AST - INFO: stdout> ovspmd: Attempt to start NNMi services is complete.
Sunday, May 10, 2020 11:28:20 AM AST - INFO: Finished running: /opt/OV/lbin/nnm-java-cmd.ovpl RC:0 numStdout:279 numStderr:102 at Sun May 10 11:28:20 AST 2020
 
Sunday, May 10, 2020 11:28:20 AM AST - INFO: 
start stderr (102 bytes)
Sunday, May 10, 2020 11:28:20 AM AST - INFO:  ovjboss                  -  NOT_RUNNING    - Exit(127)
 nnmaction                -  UNSTARTABLE    - 
Sunday, May 10, 2020 11:28:20 AM AST - INFO: end stderr
 
 
If observed, do not rollback the install, click Ok and complete the installation with errors.

 

Diagnosis

 

This is observed, because of the migration from HPSW JDK to OpenJDK zulu.

During the upgrade, the JDK used by NNMi is switched from hpws jdk to zulu or external JDK provided.

This process, can sometimes leave a dependecy for critical jboss library orphaned on OS level:

Running command - ldd /opt/OV/bin/ovjboss will provide the below output:
 
linux-vdso.so.1 =>  (0x00007fff151a5000)
libovsnmp.so.2 => /opt/OV/lib64/libovsnmp.so.2 (0x00007f91b8d7e000)
libntl.so.2 => /opt/OV/lib64/libntl.so.2 (0x00007f91b8b70000)
libnmsutil.so.2 => /opt/OV/lib64/libnmsutil.so.2 (0x00007f91b8906000)
libov.so.2 => /opt/OV/lib64/libov.so.2 (0x00007f91b85c0000)
libjvm.so => not found
libstdc .so.6 => /lib64/libstdc .so.6 (0x00007f91b82a4000)
libm.so.6 => /lib64/libm.so.6 (0x00007f91b7fa2000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f91b7d8b000)
libc.so.6 => /lib64/libc.so.6 (0x00007f91b79c8000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f91b77c4000)
/lib64/ld-linux-x86-64.so.2 (0x00005643152dd000)
 
The libjvm.so library is essential for the ovjboss JVM to start.
 
On fresh installs, the same output from ldd can be seen, and should not be a cause of alarm, but on upgraded systems this orphaned library is the cause of Exit 127

 

Solution

 

In order to fix this, you will need to manually define the libjvm.so dependecy.

If bundled, zulu JDK is used, the command is: 

 

ln -s /opt/OV/nonOV/jdk/zulu/zulu8.30.0.1-jdk8.0.172-linux_x64/jre/lib/amd64/server/libjvm.so /lib64/libjvm.so

 

That should define the dependency as expected and will allow NNMi to startup properly. 

Once that is done, re-run the ./setup.bin file and DO NOT use install parameters from older installation and DO NOT force re-install of components.

When asked, use the Continue installation option, and make sure that post-install is completed succesfully.

Labels:

How To-Best Practice
Other
Support Tips/Knowledge Docs
Support Tip
Comment List
Related
Recommended

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.