2018-01-12 02:45 AM
Hello,
Somebody has positive experience of collecting files through SFTP Agent from remote server? I have Windows cluster and I want to collect files from another server through windows share. I create share on Windows claster and use config like:
file0=\\XXX\Log\ERRORLOG
file0.interval=60
file0.enabled=true
file0.has_header=false
file0.ftp=1.1.1.1,sftp,sftp,public_key,/var/netwitness/logcollector/upload/mssql/1
file0.compression=false
As result I receive corrupted files.
I use latest version of SFTP Agent for Netwitness 11.
UPD: We have been discovered that the problem is related to encoding of the file. Our file has UCS-2 encoding. And how we discovered the problem is related to any encoding if is not ANSI.
2018-01-12 07:25 AM
Alexey
You are using the wring directory. You should be using:
file0.ftp=1.1.1.1,sftp,sftp,public_key,/upload/mssql/1
Not
file0.ftp=1.1.1.1,sftp,sftp,public_key,/var/netwitness/logcollector/upload/mssql/1
The sftp user gets dropped in half through the path.
Also are the logs in clear text before being sftp'd?
Thanks
Dave
2018-01-12 08:01 AM
Dave,
The directory is correct. I use Netwitness 11 and it is work for other SFTP Agents.
The problem on the SFTP Agent side (before transfer the file to Netwitness). The file reading not correct due to encoding of the file (not ANSI).
2018-01-12 06:54 PM
The challenge is that if you are unable to read the files (clear text) then the file reader normally can’t either.
At least this has always been my experience
What kinds of logs are you trying to send exactly?
Dave
2018-01-15 02:48 AM
This is ERRORLOG file from Microsoft SQL Server. This is link to this file: ERRORLOG