[jira] [Commented] (NIFI-871) Site-to-Site does not report the actual hostname that it was trying to connect to when it fails to connect
[ https://issues.apache.org/jira/browse/NIFI-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003088#comment-16003088 ] Mark Payne commented on NIFI-871: - [~trixpan] - no, this does not appear to be resolved. I just tested against master. To recreate, create a standalone NiFi instance and in conf/nifi.properties set the "nifi.remote.input.host" property to "otherhost" and set the "nifi.remote.input.port" property to whatever port you'd like. Then start NiFi and create a RemoteProcessGroup that points to http://localhost:8080/nifi (or whatever your URL is). It will establish the connection and discover input ports correctly. However, when you attempt to push the data, it will error with the following message: {code} 2017-05-09 13:12:53,523 ERROR [Timer-Driven Process Thread-3] o.a.nifi.remote.StandardRemoteGroupPort RemoteGroupPort[name=in,targets=http://localhost:8080/nifi] failed to communicate with http://localhost:8080/nifi due to java.net.UnknownHostException {code} This is incorrect because it appears that localhost is the Unknown Host. In reality, it was attempting to communicate with 'otherhost' and that is the unknown host. > Site-to-Site does not report the actual hostname that it was trying to > connect to when it fails to connect > -- > > Key: NIFI-871 > URL: https://issues.apache.org/jira/browse/NIFI-871 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Andre F de Miranda > > In testing the patch provided for NIFI-868, I set the nifi properties to > advertise the hostname as "otherhost". Site-to-Site, of course, failed to > connect, but rather indicating that it could not connect to otherhost, it > simply indicated that it was the RemoteProcessGroup connected to > http://localhost:8080/nifi. This is misleading because it leads the user to > believe that the Remote Process Group is having trouble connecting to > localhost, when in reality it is attempting to connect to "otherhost". We > should indicate which host we are connecting to when providing an error like > this. > 2015-08-19 13:03:46,083 WARN [Timer-Driven Process Thread-10] > o.a.n.c.t.ContinuallyRunConnectableTask > RemoteGroupPort[name=in,target=http://localhost:8080/nifi] Administratively > Pausing for 10 seconds due to processing failure: java.lang.RuntimeException: > java.nio.channels.UnresolvedAddressException > java.lang.RuntimeException: java.nio.channels.UnresolvedAddressException > at > org.apache.nifi.controller.AbstractPort.onTrigger(AbstractPort.java:234) > ~[nifi-framework-core-api-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:80) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:40) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:119) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_51] > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [na:1.8.0_51] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > [na:1.8.0_51] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > [na:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51] > Caused by: java.nio.channels.UnresolvedAddressException: null > at sun.nio.ch.Net.checkAddress(Net.java:123) ~[na:1.8.0_51] > at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622) > ~[na:1.8.0_51] > at java.nio.channels.SocketChannel.open(SocketChannel.java:189) > ~[na:1.8.0_51] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:708) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:682) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at >
[jira] [Commented] (NIFI-871) Site-to-Site does not report the actual hostname that it was trying to connect to when it fails to connect
[ https://issues.apache.org/jira/browse/NIFI-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999704#comment-15999704 ] Andre F de Miranda commented on NIFI-871: - [~markap14] Ping? > Site-to-Site does not report the actual hostname that it was trying to > connect to when it fails to connect > -- > > Key: NIFI-871 > URL: https://issues.apache.org/jira/browse/NIFI-871 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Andre F de Miranda > > In testing the patch provided for NIFI-868, I set the nifi properties to > advertise the hostname as "otherhost". Site-to-Site, of course, failed to > connect, but rather indicating that it could not connect to otherhost, it > simply indicated that it was the RemoteProcessGroup connected to > http://localhost:8080/nifi. This is misleading because it leads the user to > believe that the Remote Process Group is having trouble connecting to > localhost, when in reality it is attempting to connect to "otherhost". We > should indicate which host we are connecting to when providing an error like > this. > 2015-08-19 13:03:46,083 WARN [Timer-Driven Process Thread-10] > o.a.n.c.t.ContinuallyRunConnectableTask > RemoteGroupPort[name=in,target=http://localhost:8080/nifi] Administratively > Pausing for 10 seconds due to processing failure: java.lang.RuntimeException: > java.nio.channels.UnresolvedAddressException > java.lang.RuntimeException: java.nio.channels.UnresolvedAddressException > at > org.apache.nifi.controller.AbstractPort.onTrigger(AbstractPort.java:234) > ~[nifi-framework-core-api-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:80) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:40) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:119) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_51] > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [na:1.8.0_51] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > [na:1.8.0_51] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > [na:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51] > Caused by: java.nio.channels.UnresolvedAddressException: null > at sun.nio.ch.Net.checkAddress(Net.java:123) ~[na:1.8.0_51] > at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622) > ~[na:1.8.0_51] > at java.nio.channels.SocketChannel.open(SocketChannel.java:189) > ~[na:1.8.0_51] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:708) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:682) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.getEndpointConnection(EndpointConnectionPool.java:300) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.client.socket.SocketClient.createTransaction(SocketClient.java:129) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.StandardRemoteGroupPort.onTrigger(StandardRemoteGroupPort.java:167) > ~[nifi-site-to-site-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.AbstractPort.onTrigger(AbstractPort.java:227) > ~[nifi-framework-core-api-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > ... 10 common frames omitted -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-871) Site-to-Site does not report the actual hostname that it was trying to connect to when it fails to connect
[ https://issues.apache.org/jira/browse/NIFI-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15941734#comment-15941734 ] Andre F de Miranda commented on NIFI-871: - [~markap14] I suspect this bug has been fixed? Logs: {code:title=non-resolving hostname|borderStyle=solid} 2017-03-26 01:07:37,458 WARN [Remote Process Group 05cb1c85-015b-1000-546b-caeee934f106: http://creepy.lab.fucs.org:5/ Thread-1] o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from http://creepy.lab.fucs.org:5/nifi-api due to java.net.UnknownHostException: creepy.lab.fucs.org: Name or service not known {code} {code:title=Connection timed-out|borderStyle=solid} 2017-03-26 01:12:13,927 WARN [Remote Process Group 05ceed19-015b-1000-c59a-bd1e5 0ecc2d0: http://192.168.1.203:58889 Thread-1] o.a.n.r.util.SiteToSiteRestApiClie nt Failed to get controller from http://192.168.1.203:58889/nifi-api due to org. apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.203:58889 [/192.1 68.1.203] failed: connect timed out 2017-03-26 01:12:13,928 WARN [Remote Process Group 05ceed19-015b-1000-c59a-bd1e5 0ecc2d0: http://192.168.1.203:58889 Thread-1] o.a.n.remote.StandardRemoteProcess Group Unable to connect to RemoteProcessGroup[http://192.168.1.203:58889] due to org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.203:58889 [/ 192.168.1.203] failed: connect timed out 2017-03-26 01:12:19,194 WARN [Timer-Driven Process Thread-8] o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from http://192.168.1.203:58889/nifi-api due to org.apache.http.conn.ConnectTimeoutException: Connect to 192.168.1.203:58889 [/192.168.1.203] failed: connect timed out 2017-03-26 01:12:19,194 WARN [Timer-Driven Process Thread-8] o.apache.nifi.controller.FlowController Unable to communicate with remote instance RemoteProcessGroup[http://192.168.1.203:58889] due to org.apache.nifi.controller.exception.CommunicationsException: Unable to communicate with Remote NiFi at URI http://192.168.1.203:58889 due to: Connect to 192.168.1.203:58889 [/192.168.1.203] failed: connect timed out {code} {code:title=connection refused|borderStyle=solid} 2017-03-26 01:14:47,248 WARN [Remote Process Group 05d1b944-015b-1000-a1f9-8b2e244c6c2b: http://192.168.1.254:58889/ Thread-1] o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from http://192.168.1.254:58889/nifi-api due to org.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.254:58889 [/192.168.1.254] failed: Connection refused (Connection refused) 2017-03-26 01:14:47,248 WARN [Remote Process Group 05d1b944-015b-1000-a1f9-8b2e244c6c2b: http://192.168.1.254:58889/ Thread-1] o.a.n.remote.StandardRemoteProcessGroup Unable to connect to RemoteProcessGroup[http://192.168.1.254:58889/] due to org.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.254:58889 [/192.168.1.254] failed: Connection refused (Connection refused) 2017-03-26 01:14:49,262 WARN [Timer-Driven Process Thread-3] o.a.n.r.util.SiteToSiteRestApiClient Failed to get controller from http://192.168.1.254:58889/nifi-api due to org.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.254:58889 [/192.168.1.254] failed: Connection refused (Connection refused) 2017-03-26 01:14:49,262 WARN [Timer-Driven Process Thread-3] o.apache.nifi.controller.FlowController Unable to communicate with remote instance RemoteProcessGroup[http://192.168.1.254:58889/] due to org.apache.nifi.controller.exception.CommunicationsException: Unable to communicate with Remote NiFi at URI http://192.168.1.254:58889/ due to: Connect to 192.168.1.254:58889 [/192.168.1.254] failed: Connection refused (Connection refused) {code} > Site-to-Site does not report the actual hostname that it was trying to > connect to when it fails to connect > -- > > Key: NIFI-871 > URL: https://issues.apache.org/jira/browse/NIFI-871 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Andre F de Miranda > > In testing the patch provided for NIFI-868, I set the nifi properties to > advertise the hostname as "otherhost". Site-to-Site, of course, failed to > connect, but rather indicating that it could not connect to otherhost, it > simply indicated that it was the RemoteProcessGroup connected to > http://localhost:8080/nifi. This is misleading because it leads the user to > believe that the Remote Process Group is having trouble connecting to > localhost, when in reality it is attempting to connect to "otherhost". We > should indicate which host we are connecting to when providing an error like > this. > 2015-08-19 13:03:46,083 WARN [Timer-Driven Process Thread-10] >