You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Aaron Schultz (Jira)" <ji...@apache.org> on 2022/10/26 14:07:00 UTC
[jira] [Created] (NIFI-10702) GetSMBFile fails with Different server found for same hostname
Aaron Schultz created NIFI-10702:
------------------------------------
Summary: GetSMBFile fails with Different server found for same hostname
Key: NIFI-10702
URL: https://issues.apache.org/jira/browse/NIFI-10702
Project: Apache NiFi
Issue Type: Bug
Components: Core UI
Affects Versions: 1.18.0
Environment: RedHat 6 using openjdk 11 2018-09-25
OpenJDK Runtime Environment 18.9 (build 11+28)
OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)
Reporter: Aaron Schultz
After almost exactly 1 week of running 1.18.0, previously configured GetSMBFile processes are reporting that they cannot retrieve files due to "Different server found for same hostname" error. This happened on more than 1 of my GetSMBFile connectors. There does not appear to be a way to force it to "forget" the server; restarting the processor did not fix it. A full NiFi restart does resolve the issue.
Dump information:
{quote}2022-10-26 08:46:51,188 INFO [Timer-Driven Process Thread-55] c.hierynomus.smbj.connection.Connection Closed connection to server-probe.bbr.sa.dir.bunge.com
2022-10-26 08:46:51,188 INFO [Packet Reader for server-probe.bbr.sa.dir.bunge.com] c.h.s.t.tcp.direct.DirectTcpPacketReader Thread[Packet Reader for server-probe.bbr.sa.dir.bunge.com,5,main] stopped.
2022-10-26 08:46:51,188 ERROR [Timer-Driven Process Thread-55] o.apache.nifi.processors.smb.GetSmbFile GetSmbFile[id=d212416c-9cb0-1f8e-cf35-c4cdfe011e42] Could not establish smb connection because of error co
m.hierynomus.protocol.transport.TransportException: Different server found for same hostname 'server-probe.bbr.sa.dir.bunge.com', disconnecting...
com.hierynomus.protocol.transport.TransportException: Different server found for same hostname 'server-probe.bbr.sa.dir.bunge.com', disconnecting...
at com.hierynomus.smbj.connection.SMBProtocolNegotiator.initializeOrValidateServerDetails(SMBProtocolNegotiator.java:232)
at com.hierynomus.smbj.connection.SMBProtocolNegotiator.negotiateDialect(SMBProtocolNegotiator.java:83)
at com.hierynomus.smbj.connection.Connection.connect(Connection.java:141)
at com.hierynomus.smbj.SMBClient.getEstablishedOrConnect(SMBClient.java:96)
at com.hierynomus.smbj.SMBClient.connect(SMBClient.java:71)
at org.apache.nifi.processors.smb.GetSmbFile.onTrigger(GetSmbFile.java:390)
at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:246)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:102)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
{quote}
A possible answer was found here: https://github.com/hierynomus/smbj/issues/672
--
This message was sent by Atlassian Jira
(v8.20.10#820010)