cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ndtrack stuck in File tracking exclude step

Hi

Any one has faced this issue. Ndtrack gets stuck in this stage. We are suing latest agent 19 version.

 

[Tue 14 Mar 2023 12:01:15 PM UTC (G, 0)] {5787} Started tracking files
[Tue 14 Mar 2023 12:01:15 PM UTC (G, 0)] {5787} File tracking looking for files in directories '/opt/oracle/product;/var/opt/oracle/oratab'
[Tue 14 Mar 2023 12:01:15 PM UTC (G, 0)] {5787} File tracking looking for files not in directories '/var/tmp/fmw'
[Tue 14 Mar 2023 12:01:15 PM UTC (G, 0)] {5787} File tracking looking for files with extensions 'sys;sys2;swtag;cmptag;lax;swidtag;sig'
[Tue 14 Mar 2023 12:01:15 PM UTC (G, 0)] {5787} File tracking will include file content with extensions 'swidtag'
[Tue 14 Mar 2023 12:01:15 PM UTC (G, 0)] {5787} File tracking will include file content for directories '/opt/oracle/product;/var/opt/oracle/oratab'
[Tue 14 Mar 2023 12:01:15 PM UTC (G, 0)] {5787} File tracking will exclude file content for directories '/var/tmp/fmw'

(1) Solution
ChrisG
By Community Manager Community Manager
Community Manager

An ndtrack process may hang after this point in the logging if there are problems with the configuration of a filesystem mount point that result in "stat" system calls hanging.

You can check for issues of this nature by executing the following commands as root, and ensuring the "stat" commands do not hang:

cut -d' ' -f2 /etc/mtab /proc/self/mounts | uniq | xargs stat

cut -d' ' -f1 /etc/mtab /proc/self/mounts | grep -E '^/' | uniq | xargs stat

 

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

View solution in original post

(2) Replies

Team, 

 

please let us know incase anyone has faced this issue

ChrisG
By Community Manager Community Manager
Community Manager

An ndtrack process may hang after this point in the logging if there are problems with the configuration of a filesystem mount point that result in "stat" system calls hanging.

You can check for issues of this nature by executing the following commands as root, and ensuring the "stat" commands do not hang:

cut -d' ' -f2 /etc/mtab /proc/self/mounts | uniq | xargs stat

cut -d' ' -f1 /etc/mtab /proc/self/mounts | grep -E '^/' | uniq | xargs stat

 

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