Directory Monitor Hang

Hi

AETLE v6.3.2.13 Windows Server 2012 R2

I have no forensics on this that I can offer. But I noticed that files were not being picked up from a monitored directory on a DFS UNC Path. The Services were at a running Status and enabled in the AETLE Node list.

The process has been successfully picking up files for weeks.Server did not undergo any type of Update or Patching.

When discovered I stopped he both the Agent and the Monitor. When the Monitor service was stopped a Windows System Event was generated. My belief is that the process was hung and then when a stop trigger was fired Windows forced a tear down of the process resulting in the System Event Message of

There are no other events that I can find in the previous 24 hours that indicate a root cause.

Perhaps "DFS UNC Path" was unavailable at some stage in the past?

We will run some tests and try to reproduce the problem in our office

Thanks. Possible but it was available immediately I noticed files hsd not been picked up and when I moved them and brought them back which should have triggered the event - it didn't respond. It was like it was still processing an earlier event but had hung.

I understand this would be using the windows API but there was nothing in any event logs I could find

In the same folder where software is installed can you see directory monitor log file?
If so is there any error messages?

I am getting

01/08/2018 13:39:16 The specified network name is no longer available
01/08/2018 13:39:16 An unexpected network error occurred

Hi Bruce.

Just an update for you: We have spent a lot of time testing Directory Monitor, rebooting servers and disconnecting network cables.
As a result Directory Monitor become much more stable and even more it is able to recover after losing connections to network shares.
Once share becomes available it starts monitoring it for changes automatically.

I hope you will find it useful

Thanks. I will take a look. We seem to get the issue on an infrequent and irregular basis and nothing to monitor for except for the age of the files in pickup folders.

We were letting the dust settle on some of the SQL server issues before applying any further updates.

That seems to be the case now so we will take a look

Cheers