nnmaction Exit on signal 17

  • Document ID:KM03692141
  • Creation Date:17-Aug-2020
  • Modified Date:30-Apr-2021
    • Micro Focus Products:
      network node manager 10.20

Summary

Following are some steps that could be applied to a Windows installed NNMi in case nnmaction fails to start. /ovstatus object manager name: OVsPMD state: RUNNING PID: 21137 last message: - exit status: - object manager name: nnmaction state: NOT_RUNNING PID: - last message: Exit on signal 17 exit status: Exit(1)

Error

ovstatus will print:

object manager name: OVsPMD

state: RUNNING

PID: 21137

last message: -

exit status: -

object manager name: nnmaction

state: NOT_RUNNING

PID: -

last message: Exit on signal 17

exit status: Exit(1)


Cause



 

Fix

1. Stop NNMi services: ovstop -c
 
Navigate to the <NnmDataDir>/tmp and check if there are not any leftover (or hidden) actionServer.port or actionServer.port.lock files. If there are any, please delete them.
 
2. Then open cmd as an administrator and run the following command:
 
cacls "%NnmDataDir%\tmp" /T /E /G "NT Authority\Local Service:F"
 
If for some reasons the above command does not work, then please try running it with lowercase parameters:
 
cacls "%NnmDataDir%\tmp" /t /e /g "NT Authority\Local Service:F"
 
3. After executing the above, please try starting the NNMi services: ovstart -v
 
If you notice however that the actionSrver.port file is still not being created by the ovjboss service, try creating it manually having the content of the port on which
the action server is listening: 8989.