If you see an "ERROR: Could not obtain semaphore lock" message in the logging, then the article that @jevans has referenced may be applicable.
However if the last line of logging you see is "Obtaining semaphore lock" like shown above, that often indicates that there is another ndtrack process running - the problem is likely with the earlier process rather than the process that generates the logging you're looking at. You will need to go back through the tracker.log file to find details of what that earlier process is doing.
If the system is in a messy state with multiple ndtrack processes running, it may be easier to simply kill them all and then manually run ndtrack again. You can then look at what logging it generates, and observe whether that process hangs (stops generating new logging) at some point.
For example:
$ killall ndtrack
$ timeout 10m /var/opt/managesoft/bin/ndtrack -t Machine
$ tail /var/opt/managesoft/log/tracker.log
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
