Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

SFTP CLI works but PutSFTP fails

avatar
Contributor

We have VM server on which we have NiFi installed within the container.

When we try to connect using sftp command from within the docker it connects fine.

docker exec -it nifi bash

However when we try from NiFi PutSFTP processor, it fails with below error

Routing to failure since unable to transfer FlowFile[filename=TGT_TEST28042026.csv] to remote host sftp.AAAAA.com:
net. schmizz. sshj. transport. TransportException: Connection reset
- Caused by: java.net.SocketException: Connection

How and where do I get more details logs ?

Also, is sftp command and NiFi PutSFTP works differently ?

This is similar to my previous  post

https://community.cloudera.com/t5/Support-Questions/SFTP-CLI-works-but-PutSFTP-fails/td-p/413903

But this time vendor has whitelisted the IP and we are able to connect from within docker on which Nifi is running.

Thanks

Gautam P

2 REPLIES 2

avatar
Master Collaborator

Hello @nisaar, 

sftp CLI and PutSFTP can internally work differently. 

Have you check nifi-app.log from the NiFi nodes to review the error? 
If so, can you share here the message to take a look. 


Regards,
Andrés Fallas
--
Was your question answered? Please take some time to click on "Accept as Solution" below this post.
If you find a reply useful, say thanks by clicking on the thumbs-up button.

avatar
Master Mentor

@nisaar 

I agree with @vafs  that sharing the completed ERROR and stack trace is always gong to be most helpful in your community questions. 

Those full stack traces will have classes like "net.schmizz.sshj.transport" that you could try putting in to DEBUG within the NiFi logback to see what additional logging that class (not a NiFi library, but used by NiFi) may provide. 

Matt