Cerberus behavior when unable to open a file handle to local file?

Phil Grant

• July 28, 2020 18:16

What is the behavior of Cerberus in the case of a missing/inaccessible file share?

Context:

Connection Failure to SMB share mapping.

Symptoms showing up like the following example in the server.1.log:

File open Command received for "*" requesting Write,Create, Trunc

Unable to Open File Handle to local file "*": The network path was not found.  

Does Cerberus store the files in a cache, or does it just return an error to the SFTP client, etc.? 

If it performs an error return to the client requesting, if we can see how the error returned is formatted, we can add an error handling filter.

Is there a way to have a  local cache or secondary files share (failover?) in this case? 

0

• 

  Ian Butteriss

  Product Support

  • July 28, 2020 19:51

  Does Cerberus store the files in a cache, or does it just return an error to the SFTP client, etc.? 

  > Cerberus does not store files in a cache and just returns the error.

   

  If it performs an error return to the client requesting, if we can see how the error returned is formatted, we can add an error handling filter.

  > You can see the error formats in the Cerberus log file(s) at C:\ProgramData\Cerberus LLC\Cerberus FTP Server\log (or whatever drive letter you have the Cerberus application installed on.

   

  Is there a way to have a  local cache or secondary files share (failover?) in this case? 

  > No, Cerberus does not have the ability to add a local cache or secondary file share.

   

  0

Please sign in to leave a comment.