[ 
https://issues.apache.org/jira/browse/NIFI-7243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100737#comment-17100737
 ] 

Raúl commented on NIFI-7243:
----------------------------

Hello [~thenatog] , these are the details:

 

1. It occurs in both cases. Although we need it to work at least with user and 
password
3. Java version 1.8.0_231 - 1.8.0_242
4. This happens both in docker containers, and without containers
2. ssh-ed25519 256 jjdVyZB9rF5V0gJl05eDRjDP0AW4fDCcqcOvj443Css=
...
debug1: Local version string SSH-2.0-OpenSSH_8.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2
debug1: match: OpenSSH_7.2 pat 
OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7*
 compat 0x04000002
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 10.251.XX.XXX:22 as 'ftpvgp'
...
debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:CjwqePFt0gPKgFsm7ODNRejWDAumiJ+AZTWqXtoLKBc
debug3: load_hostkeys: loaded 1 keys from 10.251.XX.XXX
debug3: order_hostkeyalgs: prefer hostkeyalgs: 
[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: 
curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
debug2: host key algorithms: 
[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,[email protected],rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: 
[email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: 
[email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: 
[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: 
[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
...

 

debug3: record_hostkey: found key type ECDSA in file 
/home/67751248/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys from 10.251.XX.XXX
debug1: Host '10.251.XX.XXX' is known and matches the ECDSA host key.
debug1: Found key in /home/67751248/.ssh/known_hosts:2
...
Authenticated to 10.251.XX.XXX ([10.251.XX.XXX]:22).

 


And

 

File transfer protocol = SFTP-3
Cryptographic protocol = SSH-2
SSH implementation = OpenSSH_7.2
Encryption algorithm = aes
Compression = No
------------------------------------------------------------
Server key footprints
SHA-256 = ssh-ed25519 256 jjdVyZB9rF5V0gJl05eDRjDP0AW4fDCcqcOvj443Css=
MD5 = ssh-ed25519 256 64:a4:d5:ca:a5:c1:08:24:3e:3c:79:fb:ec:3a:77:73

 

 

 

Thank you so much for caring about this.

 

> SFTP Processors - Exhausted available authentication methods
> ------------------------------------------------------------
>
>                 Key: NIFI-7243
>                 URL: https://issues.apache.org/jira/browse/NIFI-7243
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.10.0, 1.11.0, 1.11.1, 1.11.3
>         Environment: PRO
>            Reporter: Raúl
>            Assignee: Nathan Gough
>            Priority: Critical
>              Labels: SFTP, listsftp
>
> In version 1.8 this works correctly. In superiors no.
>  
> Any of the processors: ListSFTP, FetchSFTP, GetSFTP, PutSFTP when connecting 
> to an sftp shows the error:
> 2020-03-10 15:12:51,596 ERROR [Timer-Driven Process Thread-3] 
> o.a.nifi.processors.standard.ListSFTP 
> ListSFTP[id=af72555e-0170-1000-c80d-7e992c9de544] Failed to perform listing 
> on remote host due to Exhausted available authentication methods: 
> net.schmizz.sshj.userauth.UserAuthException: Exhausted available 
> authentication methods
> net.schmizz.sshj.userauth.UserAuthException: Exhausted available 
> authentication methods
>  at net.schmizz.sshj.SSHClient.auth(SSHClient.java:230)
>  
> These tests that I commented have been made from nifi, both in windows and 
> linux environment and fails in both.
>    1 - Strict Host Key Checking: false
>    2 - Strict Host Key Checking: true
>         Host Key File: C:\Users\usuario\.ssh\known_hosts --> (ssh-rsa, 
> ssh-dss and ecdsa-sha2-nistp256)
>  
> From the machines, both in windows and in linux, if an sftp is made from the 
> command line it connects without problems. But with Nifi he fails to connect.
>  
> Any idea about how can I resolve this error? 
>  
> Thank you in advance,
> -------------------------------------------- log 
> -------------------------------------------------
> 2020-03-10 15:12:51,596 ERROR [Timer-Driven Process Thread-3] 
> o.a.nifi.processors.standard.ListSFTP 
> ListSFTP[id=af72555e-0170-1000-c80d-7e992c9de544] Failed to perform listing 
> on remote host due to Exhausted available authentication methods: 
> net.schmizz.sshj.userauth.UserAuthException: Exhausted available 
> authentication methods2020-03-10 15:12:51,596 ERROR [Timer-Driven Process 
> Thread-3] o.a.nifi.processors.standard.ListSFTP 
> ListSFTP[id=af72555e-0170-1000-c80d-7e992c9de544] Failed to perform listing 
> on remote host due to Exhausted available authentication methods: 
> net.schmizz.sshj.userauth.UserAuthException: Exhausted available 
> authentication methodsnet.schmizz.sshj.userauth.UserAuthException: Exhausted 
> available authentication methods at 
> net.schmizz.sshj.SSHClient.auth(SSHClient.java:230) at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getSFTPClient(SFTPTransfer.java:606)
>  at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getListing(SFTPTransfer.java:233)
>  at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getListing(SFTPTransfer.java:196)
>  at 
> org.apache.nifi.processors.standard.ListFileTransfer.performListing(ListFileTransfer.java:106)
>  at 
> org.apache.nifi.processors.standard.ListSFTP.performListing(ListSFTP.java:146)
>  at 
> org.apache.nifi.processor.util.list.AbstractListProcessor.listByTrackingTimestamps(AbstractListProcessor.java:472)
>  at 
> org.apache.nifi.processor.util.list.AbstractListProcessor.onTrigger(AbstractListProcessor.java:414)
>  at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1176)
>  at 
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:213)
>  at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
>  at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110) at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at 
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)2020-03-10 15:12:51,601 DEBUG 
> [Timer-Driven Process Thread-3] o.a.nifi.processors.standard.ListSFTP 
> ListSFTP[id=af72555e-0170-1000-c80d-7e992c9de544] has chosen to yield its 
> resources; will not be scheduled to run again for 1000 milliseconds2020-03-10 
> 15:12:51,603 TRACE [Timer-Driven Process Thread-3] 
> o.a.n.c.r.StandardProcessSession StandardProcessSession[id=0] checkpointed, 
> but no events were performed by this ProcessSession



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to