Hi, Ok, so I have now connected my (old NCM) server to the cluster, but now I am getting reports in the other server logs that can’t connect due to SSL handshake exception…
2016-10-19 14:57:02,363 WARN [NiFi Site-to-Site Connection Pool Maintenance] o.apache.nifi.remote.client.PeerSelector org.apache.nifi.remote.client.PeerSelector@590db21a Unable to refresh Remote Group's peers due to Remote host closed connection during handshake 2016-10-19 14:57:02,379 WARN [NiFi Site-to-Site Connection Pool Maintenance] o.apache.nifi.remote.client.PeerSelector org.apache.nifi.remote.client.PeerSelector@4db0b1a7 Unable to refresh Remote Group's peers due to Remote host closed connection during handshake 2016-10-19 14:57:02,379 WARN [NiFi Site-to-Site Connection Pool Maintenance] o.apache.nifi.remote.client.PeerSelector org.apache.nifi.remote.client.PeerSelector@52ab2525 Unable to refresh Remote Group's peers due to Remote host closed connection during handshake etc.etc.etc…. Prior to upgrade all servers ‘talked’ to each other no problem. This would suggest a problem with certs, but can’t see why this would be introduced as an issue with the upgrade. For what its worth, I have followed the wiki article from way back about separating off new installs from a common root of directories (for repositories etc.). Any other suggestions?? Thanks Conrad From: Bryan Bende <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, 19 October 2016 at 14:16 To: "[email protected]" <[email protected]> Subject: Re: Upgrade 0.6.1 to 1.0.0 problems with Remote Process Groups Regarding the error about the uninheritable flow caused by the "proposed authorizations do not match current authorizations"... that basically means that the node trying to connect has a different set of authorizations (users/groups/policies) from what the other nodes in the cluster have. This most likely means that something in the authorizers.xml on the new node is different from the authorizers.xml on the other nodes, and thus generated different users/groups/policies on that node during start up. The process to add a new node to an existing cluster would be the following... - From the UI, add a user for the DN of the new node - Go to the new node and configure authorizers.xml so that it does not have an initial admin, legacy file, or node identities, by having none of this it will inherit everything from the cluster - Start the new node Since you already attempted to start this node, you will want to stop it and delete users.xml and authorizations.xml before attempting the above process. Sorry if the documentation is not clear on this. On Wed, Oct 19, 2016 at 9:12 AM, Joe Witt <[email protected]<mailto:[email protected]>> wrote: Conrad, For s2s now you can just point at any of the nodes in the cluster. Have you tried changing the URL or removing and adding new RPG entries? Thanks Joe On Wed, Oct 19, 2016 at 8:38 AM, Conrad Crampton <[email protected]<mailto:[email protected]>> wrote: > Hi, > > I have finally taken the plunge to upgrade my cluster from 0.6.1 to 1.0.0. > > 6 nodes with a NCM. > > With the removal of NCM in 1.0.0 I believe I now have an issue where none of > my Remote Process Groups work as they previously did because they were > configured to connect to the NCM (as the RPG url) which now doesn’t exist. > > I have tried converting my NCM to a node but whilst I can get it running > (sort of) when I try and connect to the cluster I get something like this in > my logs… > > > > 2016-10-19 13:14:44,109 ERROR [main] o.a.nifi.controller.StandardFlowService > Failed to load flow from cluster due to: > org.apache.nifi.controller.UninheritableFlowException: Failed to connect > node to cluster because local flow is different than cluster flow. > > org.apache.nifi.controller.UninheritableFlowException: Failed to connect > node to cluster because local flow is different than cluster flow. > > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:879) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:493) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.web.server.JettyServer.start(JettyServer.java:746) > [nifi-jetty-1.0.0.jar:1.0.0] > > at org.apache.nifi.NiFi.<init>(NiFi.java:152) > [nifi-runtime-1.0.0.jar:1.0.0] > > at org.apache.nifi.NiFi.main(NiFi.java:243) > [nifi-runtime-1.0.0.jar:1.0.0] > > Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed > Authorizer is not inheritable by the flow controller because of Authorizer > differences: Proposed Authorizations do not match current Authorizations > > at > org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:252) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1435) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:83) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:671) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:857) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > ... 4 common frames omitted > > 2016-10-19 13:14:44,414 ERROR [main] o.a.n.c.c.node.NodeClusterCoordinator > Event Reported for ncm-cm1.mis-cds.local:9090 -- Node disconnected from > cluster due to org.apache.nifi.controller.UninheritableFlowException: Failed > to connect node to cluster because local flow is different than cluster > flow. > > 2016-10-19 13:14:44,420 ERROR [Shutdown Cluster Coordinator] > org.apache.nifi.NiFi An Unknown Error Occurred in Thread Thread[Shutdown > Cluster Coordinator,5,main]: java.lang.NullPointerException > > 2016-10-19 13:14:44,423 ERROR [Shutdown Cluster Coordinator] > org.apache.nifi.NiFi > > java.lang.NullPointerException: null > > at > java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011) > ~[na:1.8.0_51] > > at > java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006) > ~[na:1.8.0_51] > > at > org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.updateNodeStatus(NodeClusterCoordinator.java:570) > ~[nifi-framework-cluster-1.0.0.jar:1.0.0] > > at > org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.shutdown(NodeClusterCoordinator.java:119) > ~[nifi-framework-cluster-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService$1.run(StandardFlowService.java:330) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_51] > > 2016-10-19 13:14:44,448 WARN [main] o.a.n.c.l.e.CuratorLeaderElectionManager > Failed to close Leader Selector for Cluster Coordinator > > java.lang.IllegalStateException: Already closed or has not been started > > at > com.google.common.base.Preconditions.checkState(Preconditions.java:173) > ~[guava-18.0.jar:na] > > at > org.apache.curator.framework.recipes.leader.LeaderSelector.close(LeaderSelector.java:270) > ~[curator-recipes-2.11.0.jar:na] > > at > org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager.stop(CuratorLeaderElectionManager.java:159) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.FlowController.shutdown(FlowController.java:1303) > [nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService.stop(StandardFlowService.java:339) > [nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.web.server.JettyServer.start(JettyServer.java:753) > [nifi-jetty-1.0.0.jar:1.0.0] > > at org.apache.nifi.NiFi.<init>(NiFi.java:152) > [nifi-runtime-1.0.0.jar:1.0.0] > > at org.apache.nifi.NiFi.main(NiFi.java:243) > [nifi-runtime-1.0.0.jar:1.0.0] > > 2016-10-19 13:14:45,062 WARN [Cluster Socket Listener] > org.apache.nifi.io.socket.SocketListener Failed to communicate with Unknown > Host due to java.net.SocketException: Socket closed > > java.net.SocketException: Socket closed > > at java.net.PlainSocketImpl.socketAccept(Native Method) > ~[na:1.8.0_51] > > at > java.net<http://java.net>.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:404) > ~[na:1.8.0_51] > > at java.net.ServerSocket.implAccept(ServerSocket.java:545) > ~[na:1.8.0_51] > > at > sun.security.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:348) > ~[na:1.8.0_51] > > at > org.apache.nifi.io.socket.SocketListener$2.run(SocketListener.java:112) > ~[nifi-socket-utils-1.0.0.jar:1.0.0] > > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51] > > 2016-10-19 13:14:45,064 WARN [main] org.apache.nifi.web.server.JettyServer > Failed to start web server... shutting down. > > java.lang.Exception: Unable to load flow due to: java.io.IOException: > org.apache.nifi.controller.UninheritableFlowException: Failed to connect > node to cluster because local flow is different than cluster flow. > > at > org.apache.nifi.web.server.JettyServer.start(JettyServer.java:755) > ~[nifi-jetty-1.0.0.jar:1.0.0] > > at org.apache.nifi.NiFi.<init>(NiFi.java:152) > [nifi-runtime-1.0.0.jar:1.0.0] > > at org.apache.nifi.NiFi.main(NiFi.java:243) > [nifi-runtime-1.0.0.jar:1.0.0] > > Caused by: java.io.IOException: > org.apache.nifi.controller.UninheritableFlowException: Failed to connect > node to cluster because local flow is different than cluster flow. > > at > org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:497) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.web.server.JettyServer.start(JettyServer.java:746) > ~[nifi-jetty-1.0.0.jar:1.0.0] > > ... 2 common frames omitted > > Caused by: org.apache.nifi.controller.UninheritableFlowException: Failed to > connect node to cluster because local flow is different than cluster flow. > > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:879) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:493) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > ... 3 common frames omitted > > Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed > Authorizer is not inheritable by the flow controller because of Authorizer > differences: Proposed Authorizations do not match current Authorizations > > at > org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:252) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1435) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:83) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:671) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > at > org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:857) > ~[nifi-framework-core-1.0.0.jar:1.0.0] > > ... 4 common frames omitted > > [root@ncm-cm1 logs]# > > > > I don’t know if the ‘Proposed Authorizer is not inheritable…’ exception is > part of the problem too. > > The docs weren’t very clear on whether (when upgrading and using the legacy > support of the authorized-user.xml path required the nodes to be also added > to the authorizers.xml. > > I did add them in the end as various attempts to get the cluster up and > running without them failed (as each server didn’t seem to have rights to do > anything. > > > > I have a lot of RPG in my work flows as I am ingesting many syslog data > sources and this was the recommended pattern to distribute the data > (listensyslog…run on primary, output to port (RPG), pick up in rest of data > flow), > > > > Any suggestions on where to start trying to get this working? > > I’ve tried creating a new RPG on one on the datanodes and connecting the > syslog to that which sort of worked but then I have a bunch of other errors > when trying to enable the ports to do with not being able to connect to > (what was) the NCM. > > > > Thanks > > Conrad > > > > SecureData, combating cyber threats > > ________________________________ > > The information contained in this message or any of its attachments may be > privileged and confidential and intended for the exclusive use of the > intended recipient. If you are not the intended recipient any disclosure, > reproduction, distribution or other dissemination or use of this > communications is strictly prohibited. The views expressed in this email are > those of the individual and not necessarily of SecureData Europe Ltd. Any > prices quoted are only valid if followed up by a formal written quote. > > SecureData Europe Limited. Registered in England & Wales 04365896. > Registered Address: SecureData House, Hermitage Court, Hermitage Lane, > Maidstone, Kent, ME16 9NT ***This email originated outside SecureData*** Click here<https://www.mailcontrol.com/sr/0ulpuIS9abTGX2PQPOmvUu5zZAYN1MosvyIBd3ccm1uXNGYSg1FTwTmtRvHb6XdL25LWvxYjTGeVGm43FW9a3A==> to report this email as spam.
