nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andre <andre-li...@fucs.org>
Subject Re: Clustering configuration error -- HTTPS hostname wrong
Date Mon, 05 Dec 2016 00:57:29 GMT
Adam,

Is the X509 certificate of host1.foo.com reflecting the correct Subject
Name?

Would you know where the URL tihdedg11.troweprice.com:8080 come from?

Cheers

On Mon, Dec 5, 2016 at 10:34 AM, Adam J. Shook <adamjshook@gmail.com> wrote:

> Hello all,
>
> I am trying to enable clustering on my NiFi instance, starting with the
> original single-node instance which uses Kerberos and HTTPS.  I've been
> following the Clustering Configuration section in the admin guide, and I
> see in the logs that the node takes over as the Coordinator and elects the
> dataflow.  When I try to connect to the UI I receive the below error -- it
> looks like there is no hostname in the GET request when it tries to
> replicate it?  I started up the second node and I see it join the cluster,
> but accessing the UI throws the same erro -- failing to replicate the
> request to both nodes.
>
> Any ideas?
>
> Thank you,
> --Adam
>
>
> 2016-12-04 23:28:02,105 WARN [Replicate Request Thread-1] o.a.n.c.c.h.r.ThreadPoolRequestReplicator
> Failed to replicate request GET /nifi-api/flow/current-user to
> tihdedg11.troweprice.com:8080 due to {}
> com.sun.jersey.api.client.ClientHandlerException: java.io.IOException:
> HTTPS hostname wrong:  should be <host1.foo.com>
>
>

Mime
View raw message