Thanks Mark,

In fact i’m using expression language, I will upgrade to 1.4.

Carlos

From: Mark Payne [mailto:[email protected]]
Sent: sexta-feira, 20 de outubro de 2017 14:52
To: [email protected]
Subject: Re: FetchSftp with user/password dont move the file

Carlos,

Are you using the Expression Language in your configuration of FetchSFTP? There 
was an issue [1] that
caused the processor not to behavior properly when using Expression Language. I 
have seen two different
problems occur because of the issue. The first one is the "Auth cancel" error 
that you're showing here. The
other issue that I've seen occur is when the Completion Strategy is set to 
Move, it will sometimes
indicate a FileNotFoundException even after it has pulled the data.

Fortunately, though, this issue was address in NiFi 1.4.0, so if this is the 
issue you're hitting you should be
good to go on the newest version of NiFi.

Thanks
-Mark

[1] https://issues.apache.org/jira/browse/NIFI-3281

On Oct 20, 2017, at 6:07 AM, Carlos Manuel Fernandes (DSI) 
<[email protected]<mailto:[email protected]>> wrote:


Hi,

I configured a fetchSftp   with username/password  (no  privatekey for 
certificate)  and the processor is able to fetch the file but gives an error 
when try to move the file.
Apparently to move the file the processor try use authentication with 
certificate, not user/pwd. I’m using NIFI 1.30.

This is the warning:

WARN [Timer-Driven Process Thread-2] o.a.nifi.processors.standard.FetchSFTP 
FetchSFTP[id=1dce6844-015d-1000-9ddf-513c44ecb93f] Successfully fetched the 
content for 
StandardFlowFileRecord[uuid=bd37a9c5-7345-4305-9044-befd2e025b0a,claim=StandardContentClaim
 [resourceClaim=StandardResourceClaim[id=1508492612055-61, container=default, 
section=61], offset=4282, length=25699415],offset=0,name=xxx.xxx,size=25699415] 
from host:22/batch/cdirect/in/xxx.xxx but failed to rename the remote file due 
to java.io.IOException: Failed to obtain connection to remote host due to 
com.jcraft.jsch.JSchException: Auth cancel:

tks

Carlos

Reply via email to