Yep, certificate is fine. I ended up changing the cluster.load.balance.host
to the IP address and everything worked fine. The cluster UI in nifi
identifies the server by its FQDN. Good enough!
Total mystery though.
On Wed, 4 Dec 2019 at 21:21, Andy LoPresto wrote:
> Hi Phil,
>
> Are you sure
Hi Phil,
Are you sure that the certificates have valid SubjectAlternativeName entries
for the proper hostnames?
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Dec 3, 2019, at 7:53 PM, Phil H wrote:
>
>
Hello,
To get rid of the old values from before securing your cluster, remove
the state/local directory on both servers (assuming you don't have any
processor state that you care about since this is a new cluster).
For the other issue, is there a stacktrace with more info?
Thanks,
Bryan
On
Hi there,
I (almost) have a secure nifi 1.9.2 cluster of two servers. Server A starts
up fine, but Server B fails to start with this error (I cannot copy/paste
as it is an offline system)
Could not start listening for incoming connections in order to load balance
data across the cluster. Please
Team, I did not hear back on this.
Here are some additional scenario's.
We have a 1 node cluster. We have a flow. When we run that flow, we get the
below error. After which we see the following message in canvas - Action
cannot be performed because there is currently no Cluster Coordinator
