Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    18
  • Subscribers subscribers
    17
  • Views views
    879
  • Users 0 members are here
Related
Options

NNMi classic 24.2 install fails on RedHat 7 with imbedded postgres DB

iamnoone

Thanks in advance..

The install fails to create the postgres DB.  I think its related to encryption algo.

I am trying the silent install with the ovparams file in /tmp with "nnm.install.hwSupportsRNG=false"

to turn of FIPS but I am not convinced it is working.

Question:  Is there a way to confirm the install is not using FIPS or any other thoughts?

  • 0

    I have the same problem on Oracle Linux 9.4. My searches led me to the insufficient entropy problem.
    NNMi failures in FIPS mode due to entropy insufficiency - Network Node Manager i (microfocus.com)

    As of now, I am also looking for a solution. Dear support service we need help in solving this problem.

    nnmaction                -  NOT_RUNNING    Exit on signal 17 Exit(1)

  • 0   in reply to 

    Hello Oleksandr,

    maybe the nnmaction error is not related to entropy as there is a hotfix available, which solved my problem with "exit 17": After upgrading to NNMi 24.2, nnmaction is not running (microfocus.com)

    HTH and best regards

    Allessandro


    Allessandro Soloperto
    ITC GmbH - Senior Consultant
    If this answered your question, please mark it as "Suggest as Answer" or "Verify as Answer".
    If you found this response useful, please give it a "Like".

  • 0 in reply to   

    I have another error in log. But i contact with support. thank you.

    Jun 26, 2024 11:44:34.797 AM [ThreadID:1] CONFIG: null init: Logging Handler initialized to log to file pattern: "/var/opt/OV/log/nnm/public/incidentActions.%g.%u.log" up to a limit of 5 files of 0.1 MB each. Append to log until full:"false".
    Jun 26, 2024 11:44:34.805 AM [ThreadID:1] FINE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer: Entering createActionServer()
    Jun 26, 2024 11:44:35.029 AM [ThreadID:1] SEVERE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer: Failed to get port number from /var/opt/OV/nmsas/public/actionServer.port due to java.io.FileNotFoundException. Port lock file not found : java.io.FileNotFoundException: Port lock file not found
    at com.hp.ov.nms.events.action.server.ActionServer.createActionServer(ActionServer.java:221)
    at com.hp.ov.nms.events.action.server.ActionServer.main(ActionServer.java:342)

    Jun 26, 2024 11:44:35.030 AM [ThreadID:1] INFO: com.hp.ov.nms.events.action.log.ActionLogger : Will try to read /var/opt/OV/nmsas/public/actionServer.port file again after 45 seconds
    Jun 26, 2024 11:45:20.031 AM [ThreadID:1] SEVERE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer: Failed to get port number from /var/opt/OV/nmsas/public/actionServer.port due to java.io.FileNotFoundException. Port lock file not found : java.io.FileNotFoundException: Port lock file not found
    at com.hp.ov.nms.events.action.server.ActionServer.createActionServer(ActionServer.java:221)
    at com.hp.ov.nms.events.action.server.ActionServer.main(ActionServer.java:342)

    Jun 26, 2024 11:45:20.031 AM [ThreadID:1] INFO: com.hp.ov.nms.events.action.log.ActionLogger : Will try to read /var/opt/OV/nmsas/public/actionServer.port file again after 45 seconds
    Jun 26, 2024 11:46:05.032 AM [ThreadID:1] SEVERE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer: Failed to get port number from /var/opt/OV/nmsas/public/actionServer.port due to java.io.FileNotFoundException. Port lock file not found : java.io.FileNotFoundException: Port lock file not found
    at com.hp.ov.nms.events.action.server.ActionServer.createActionServer(ActionServer.java:221)
    at com.hp.ov.nms.events.action.server.ActionServer.main(ActionServer.java:342)

    Jun 26, 2024 11:46:05.032 AM [ThreadID:1] INFO: com.hp.ov.nms.events.action.log.ActionLogger : Will try to read /var/opt/OV/nmsas/public/actionServer.port file again after 45 seconds
    Jun 26, 2024 11:46:50.033 AM [ThreadID:1] SEVERE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer: Failed to get port number from /var/opt/OV/nmsas/public/actionServer.port due to java.io.FileNotFoundException. Port lock file not found : java.io.FileNotFoundException: Port lock file not found
    at com.hp.ov.nms.events.action.server.ActionServer.createActionServer(ActionServer.java:221)
    at com.hp.ov.nms.events.action.server.ActionServer.main(ActionServer.java:342)

    Jun 26, 2024 11:46:50.034 AM [ThreadID:1] INFO: com.hp.ov.nms.events.action.log.ActionLogger : Will try to read /var/opt/OV/nmsas/public/actionServer.port file again after 45 seconds
    Jun 26, 2024 11:47:35.035 AM [ThreadID:1] SEVERE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer: Failed to get port number from /var/opt/OV/nmsas/public/actionServer.port due to java.io.FileNotFoundException. Port lock file not found : java.io.FileNotFoundException: Port lock file not found
    at com.hp.ov.nms.events.action.server.ActionServer.createActionServer(ActionServer.java:221)
    at com.hp.ov.nms.events.action.server.ActionServer.main(ActionServer.java:342)

    Jun 26, 2024 11:47:35.035 AM [ThreadID:1] INFO: com.hp.ov.nms.events.action.log.ActionLogger : Will try to read /var/opt/OV/nmsas/public/actionServer.port file again after 45 seconds
    Jun 26, 2024 11:48:20.035 AM [ThreadID:1] FINE: com.hp.ov.nms.events.action.log.ActionLogger createActionServer: Exiting createActionServer()
    Jun 26, 2024 11:48:20.036 AM [ThreadID:1] SEVERE: com.hp.ov.nms.events.action.log.ActionLogger : Failed to initalize the action server

  • 0   in reply to 

    I think, that there are other knowledge base articles about that.


    Allessandro Soloperto
    ITC GmbH - Senior Consultant
    If this answered your question, please mark it as "Suggest as Answer" or "Verify as Answer".
    If you found this response useful, please give it a "Like".

  • 0 in reply to 

    There used to be an issue with folder permissions with public folder could you check if that's the case. I don't have the KB doc handy but there are number of KB docs about the public folder issue. Process cannot write the lock/pid file in that folder and due to that other process cannot find this file and fails.

  • 0 in reply to 

    I found this article about temp and public folders. But I have no problem with that. I have a clean system and freshly installed nnmi. Currently, I have created a case, I am waiting for a response. If there is something interesting, I will share.

  • 0 in reply to 

    I this is the issue I mentioned may be of use.

    Issue with nnmaction not running NNMi 10.00/0.1/0.2 – Foulk Consulting Help Center

  • 0 in reply to 

    I saw this article, this is a not my variant. But thank you :)

  • 0 in reply to 

    my issue seems to be with the creation of the embeded postgres db.  I get 

    object manager name: nmsdbmgr
    state: NOT_RUNNING
    PID: -
    last message: -
    exit status: Exited on signal 6, core dumped.

    -----------------------------------------------------------------------------------------

    the initdb.log shows

    fips.c(145): OpenSSL internal error, assertion failed: FATAL FIPS SELFTEST FAILURE
    Aborted (core dumped)

    -------------------------------------------------------------------------------------------------------

    running a silent install without fips does the same thing... but it looks like the ovinstallparams file gets overwritten in tmp

    setting the flag back to TRUE.

  • 0 in reply to 

    Can you provide exact  OS version and other configuration(memory and number of CPU)

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.