nnmaction exits on signal 17

  • KM03749964
  • 21-Oct-2020
  • 21-Oct-2020

This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.


nnmaction exits with signal 17 on Windows OS.


nnmaction state: NOT_RUNNING

PID: - last message: Exit on signal 17

exit status: Exit(1)


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 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.