Ok, that was a certificate hostname problem. Now, when I connect to the NCM login page it says "Your account is active and you are already logged in." but hitting the web UI give "Not authorized."
On Fri, Jul 1, 2016 at 4:59 PM, Joe Skora <[email protected]> wrote: > I'm trying to setup a small ncm+2 node cluster all running locally. I'm > replicating a configuration I setup on another system, but I don't have > access to the working original at the moment. > > The NCM and node1 come up without any noticeable problems, but when I try > to access the NCM web UI I get this exception and the GUI says no nodes > were available to process the request. > > 2016-07-01 16:53:37,436 WARN [NiFi Web Server-58] >> o.a.n.c.m.impl.HttpRequestReplicatorImpl Node request for >> [id=632514f6-036f-4025-8775-819ed5210804, apiAddress=localhost, >> apiPort=8180, socketAddress=localhost, socketPort=8198, >> siteToSiteAddress=localhost, siteToSitePort=8190] encountered exception: >> java.util.concurrent.ExecutionException: >> com.sun.jersey.api.client.ClientHandlerException: java.io.IOException: >> HTTPS hostname wrong: should be <localhost> > > > The NCM appears to be receiving heartbeats from the clients. > > Any idea what I might have configured wrong from that? >
