Wikis - Page

Knowledge Doc: NNMi have not started after RHEL package update

2 Likes

After updating packages on RHEL, NNMi have never started and nnmtrapreceiver_err.log are generated.

Environment

Network Node Manager i (NNMi) 24.2
Red Hat Enterprise Linux (RHEL) 8.6

Situation

NNMi requires Java Development Kit (JDK) 1.8.x be available on the system and JDK can choose NNMi-bundled or Already-installed.
If Already-installed JDK was used in NNMi and JDK package was updated, NNMi have never started after JDK updates and nnmtrapreceiver_err.log is generated in /opt/OV/log/nnm/.

nnmtrapreceiver_err.log contains:

--------------------------------------------------------------------------------
yyyy-mm-dd hh:mm:ss
Due to an internal error nnmtrapreceiver has exited.  This file was
left as an aid in debugging the problem.  Save this file
and the /var/opt/OV/tmp/core file.
Current working directory was "/var/opt/OV/tmp".

If the problem persists, customers with HP support contracts
can call their nearest HP Response Center for support at:
		North/South America:
		  North American Response Center:  1-800-633-3600
		Europe/Africa:
		  European Customer Response Center: +32 2 778 3800 (Belgium)
											 +31 20 547 9666 (Netherlands)
		Asia/Pacific:
		  Australian Response Center:   BH 131147  AH 0014 800 125 541


Error logging is affected by the OVNOSTACKTRACE (don't create log) and
OVSPINONCRASH (spin process on error) environment variables.

Program name         = nnmtrapreceiver
Process id           = 4422
Crash Cause          = signal: SIGSEGV (11)
Crash Time           = yyyy-mm-dd hh:mm:ss
Operating System     = unknown
Version              = Micro Focus Software Mar 20 2024
Username             = root

nnmtrapreceiver started on Linux btpgcsvm46742 4.18.0-372.119.1.el8_6.x86_64  #1 SMP Tue Aug 18 14:50:17 EDT 2020 x86_64 at yyyy-mm-dd hh:mm:ss  Command: /opt/OV/bin//nnmtrapreceiver -start


4 Processors
2002242 Pages of physical memory
1259966 Pages of available physical memory
4096 Byte page size

Running on <host> Linux 4.18.0-372.119.1.el8_6.x86_64 #1 SMP ...
Locale: ja_JP.UTF-8

Maximum size of process's heap: 18014398509481984 KBytes
Maximum size of process's stack: 8192 KBytes

Exiting
...
--------------------------------------------------------------------------------

For cause and resolution please refer to the complete knowledge article

Labels:

Support Tips/Knowledge Docs
Comment List
  • Hello,

    I have also experienced the non-starting NNMi in my AF cluster after one of the latest RHEL package updates but it seemed that it had nothing to do with a missing com.hp.ov.nms.jdk parameter. I have this one added with the correct path to JDK binaries.

    In my case the only solution/workaround was to downgrade OpenJDK package from the latast one "java-1.8.0-openjdk-devel-1:1.8.0.422.b05-2.el8.x86_64" to the one released before it: "java-1.8.0-openjdk-devel-1:1.8.0.412.b08-2.el8.x86_64".

    Does anyone faced a similar issue?

Related
Recommended