I believe you are having issues related to hostname resolution on your nodes and NCM. By leaving the varies host properties in your NiFi properties file blank, they are resolving to localhost. Each stem thinks localhost is itself. Try filling in the properties either with FQDNs that each node can successfully resolve or populate these host properties with IPs. So the rest are multiple host properties to populate. One under site-to-site properties, one under web properties, and a couple under cluster properties. On Dec 18, 2015 3:00 PM, "plj" <[email protected]> wrote:
> Thank you for your help. I deleted the flow.xml.gz . So now I have the > NCM > on machine 'b' and a node on machine 'c'. I start up a and then start up > b. > In b's logs I see logs of heartbeats: > 2015-12-18 14:41:05,807 INFO [Process NCM Request-10] > o.a.n.c.p.impl.SocketProtocolListener Finished processing request > 790c06c7-6857-4a90-9d4f-76ec99159369 (type=HEARTBEAT, length=3250 bytes) in > 2 millis > > On machine c is also see heartbeats: > 2015-12-18 14:39:55,741 INFO [Clustering Tasks Thread-3] > org.apache.nifi.cluster.heartbeat Heartbeat created at 2015-12-18 > 14:39:55,664 and sent at 2015-12-18 14:39:55,741; send took 6 millis > > Everything seems fine. > > Then I try to view NiFi on the NCM which I set the web to: > nifi.web.http.port=8089 > > http://machine-b.mitre.org:8089/nifi/ > > I see: > An unexpected error has occurred > > No nodes were able to process this request. > > > I don't see anything in the logs to suggest what went wrong. > > Thoughts? > > > > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Cluster-Setup-tp5853p5860.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
