In the past, I've seen this occur because the semaphore limit is set too low -- particularly if you have something intensive like Oracle DB on the same machine.
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.
(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.)
Are you seeing any ndtrack processes still running after this logging? If you are seeing processes running, that suggests they are hanging; if you don't see processes running that suggests they are crashing (terminating).
(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.)
I have the same issue, but with a Linux machine, still the same error Obtaining semaphore lock (to ensure only one instance is running)..., and I tried to uninstall/install, check locks, kill the process, etc, still the same output, it's hanging there and no inventory is generated, also we have file scanning activated on linux systems.
If the last line of logging output says "Obtaining semaphore lock", that generally indicates there is already some other ndtrack process running.
In you're case, the process ID 21761 is waiting for another ndtrack process to end. If you wait for the original process to end (or kill it) then your process 21761 will then be able to proceed with its work.
(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.)
