Known Issue: Inventory gathering may hang on Unix-like operating systems if executable bit is set on a non executable file named "java" (IOJ-2072459)
Known Issue: Inventory gathering may hang on Unix-like operating systems if executable bit is set on a non executable file named "java" (IOJ-2072459)
Summary
Inventory gathering ndtrack processes on Unix-like operating systems may hang while attempting to gather Java version details if a file named "java" that is not executable is found on the filesystem.
Symptoms
When this issue occurs, output in the tracker.log file from the ndtrack process will stop after logging that looks like either of the following:
[Wed 05 Jan 2022 10:05:28 AM -03 (G, 0)] {17500} The file '/usr/java/jre7/bin/java' has been detected as a possible package registry
[...]
[Wed 05 Jan 2022 10:05:41 AM -03 (G, 0)] {17500} IBM MQ inventory was unsuccessful either because it is not installed or there was an error.
Or:
[Wed 05 Jan 2022 10:05:28 AM -03 (G, 0)] {17500} The file '/usr/java/jre7/bin/java' has been detected as a possible package registry
[...]
[Wed 05 Jan 2022 10:05:41 AM -03 (G, 0)] {17500} Java product: "Java(TM) SE Runtime Environment", full version: "8.1.037", publisher: "", install location: "/usr/java/jre8/bin".
Cause
This issue is caused by a failure by the ndtrack process to handle files name "java" on the filesystem that cannot be executed.
In particular, log message(s) in the tracker.log file stating:
The file '<path>/java' has been detected as a possible package registry
will identify a <path> that does not appear in a subsequent log message:
Java project: <details...>
One of the java files thus identified will be triggering this issue.
Workaround
The inventory agent can be configured to avoid attempting to gather Java version details (and therefore avoid this issue) by setting the tracker component's PerformJavaScan preference to false.
This issue will also not occur if file scanning of directories that contain a problematic java executable is not performed. For example, this could be achieved by configuring the tracker component's ExcludeDirectory preference.
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.
@Ronny_OO7 - the specific bug in the code that was root cause of this known issue is not present in the 17.0.1 agent. Is it possible that the issue you are seeing is the known (but currently unfixed) issue linked from the "Additional information" section of this article?
It is also possible there is another (unknown) issue with similar symptoms - the symptoms described in this article could potentially have other root causes. If you are encountering symptoms like described with the 2021 R1 (17.0.1) agent that aren't otherwise explained then I'd suggest raising a case with Flexera Support so that they can be investigated.
