09-05-2018 05:23 PM - edited 09-05-2018 05:24 PM
NSO process spawning on Centos takes a lot of time and the process of detecting how the startup coming along is difficult. Is there a way to understand nso process on centos.
1) Ports binding to be freed
2) Also the error status have to monitored from system journal
even after doing a systemctl daemon-reload
For example see the error below
Restarting ncs (via systemctl): Job for ncs.service failed because the control process exited with error code. See "systemctl status ncs.service" and "journalctl -xe" for details.
Solved! Go to Solution.