CA Workload Automation Agent 11.3.6 File watcher gives error 'Scan failed' and 'specified network is no longer available'

[Legacy User]

 CA Workload Automation Agent 11.3.6 File watcher gives error 'Scan failed' and 'specified network is no longer available'. We are using NAS share path. Sometimes it works and most of the times it throws this error.

 

Logs:

FileMonPlugin.FileMon Requests Processor 610.CybFileMonHandler.processCriticalError[:277] -
cybermation.library.services.queuerequests.CybRequestHandlingException: Scan Failed

t cybermation.plugins.filemon.handler.treescan.CybTreeScannerPolling.scanAllFilesTry(CybTreeScannerPolling.java:418)
at cybermation.plugins.filemon.handler.treescan.CybTreeScannerPolling.scanAllFiles(CybTreeScannerPolling.java:307)
at cybermation.plugins.filemon.handler.CybFileMonHandlerGroup.execute(CybFileMonHandlerGroup.java:228)
at cybermation.library.services.queuerequests.CybQueueableRequestScatterGatherProcessor.run(CybQueueableRequestScatterGatherProcessor.java:209)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: The specified network name is no longer available
at java.io.WinNTFileSystem.canonicalize0(Unknown Source)
at java.io.WinNTFileSystem.canonicalize(WinNTFileSystem.java:428)
at java.io.File.getCanonicalPath(File.java:618)
at cybermation.plugins.filemon.handler.treescan.CybTreeScannerPolling.splitPath(CybTreeScannerPolling.java:233)
at cybermation.plugins.filemon.handler.treescan.CybTreeScannerPolling.setupScan(CybTreeScannerPolling.java:264)
at cybermation.plugins.filemon.handler.treescan.CybTreeScannerPolling.scanAllFilesTry(CybTreeScannerPolling.java:381)
at cybermation.plugins.filemon.handler.treescan.CybTreeScannerPolling.scanAllFiles(CybTreeScannerPolling.java:307)
at cybermation.plugins.filemon.handler.CybFileMonHandlerGroup.execute(CybFileMonHandlerGroup.java:228)
at cybermation.library.services.queuerequests.CybQueueableRequestScatterGatherProcessor.run(CybQueueableRequestScatterGatherProcessor.java:209)

[Jonathan Calloway]

First, is the NAS being update /  rebooted or made unavailable in some other way while the file watcher is running.  Obviously if there is maintenance or if the NAS goes off-line for any reason the file watcher will fail with this error.

 

We had a similar issue with this not too long ago.  We opened a ticket to support and Kiki Pham (gotta give credit where credit is due) made the following suggestion:

 

By default, the Agent marks the filetrigger as failed (Scan Failed) if the directory is not available to the file after 10 seconds.

 

Adding the options to increase the number of retry should help eliminate/alleviate your "Scan Failed" issue.   Also, I suggest that you use these options only on agents that are having this problem, and not all agents.

 

Again, these are the options that need to be added to the agentparm.txt file:

. filemonplugin.scan.retries=xx (default is 1) . filemonplugin.scan.retries.sleep=yyyyy (10,000 milliseconds or 10 seconds is the default)

 

filemonplugin.scan.retries represents the number of retry filemonplugin.scan.retries.sleep represents the sleep interval between retry

 

1. If the file trigger is not able to reach the directory it will go into retry mode, and will fail after xx minutes. The next file trigger scan will wait for the last one to complete. They will single-thread through (by design).  If there are many file triggers, some could end up waiting a long time even if they are searching for a local file that exists.

 

2. If someone changes the password for the userid in ESP, and in the NAS, the file triggers do not get passed the new password. The first file trigger fails, and retries for xx minutes. The next file trigger scan waits in single file for the first one to exhaust the xx minutes of retry. If there are many file triggers on the agent, the retries for all of them will take a long time.  Once the file trigger fails (after xx minutes of retries), the next file trigger will get the new password and will be successful.

 

Hope this is helpful!

Jonathan Calloway

[Legacy User]

Hi

What Jonathan reported is also documented in note: TEC1745961

 

Regards

Jean Paul

[Jonathan Calloway]

I think it should be noted that this fix is not platform dependent.  For us, it resolved an issue on Windows, the article that JeanPaul cited was for Linux, I *think* we've used this in AIX to resolve an issue as well. 

[Legacy User]

That's right Jonathan

The System Agent is a java based engine and all these options are the same among the different platforms

Regards

Jean Paul

[Legacy User]

Thanks All for your replies. I will test this out in Janurary and let you know if this resolve our issues.