'Remote instance of NiFi is not configured to allow RAW Socket site-to-site communications'

Question

'Remote instance of NiFi is not configured to allow RAW Socket site-to-site communications'

Question by David DN Sep 06, 2016 at 07:35 AM Nifi

In cluster mode of NiFi 1.0.0. I try to distribute the flowfiles from primary node to cluster nodes by using Remote Process Group.

The property 'Transport Protocol' of Remote Process Group is 'RAW'. I get the error message:

'Remote instance of NiFi is not configured to allow RAW Socket site-to-site communications'

How to resolve it?

Thanks for your help.

David

0

10 |6000 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Answer 1 · 2016-09-06T12:18:30Z

Best Answer

Answer by Matt Clarke · Sep 06, 2016 at 12:18 PM

@David DN

Before Site-to-Site (S2S) can be used the following properties must be set in the nifi.properties file on all the Nodes in your NiFi cluster:

# Site to Site properties
nifi.remote.input.host=<FQDN of Host>              <-- Set to resolveable FQDN by all Nodes
nifi.remote.input.secure=false                     <-- Set to True on if NiFi is running HTTPS
nifi.remote.input.socket.port=<Port used for S2S)  <-- Needs to be set to support Raw/enable S2S
nifi.remote.input.http.enabled=true                <-- Set if you want to support HTTP transport
nifi.remote.input.http.transaction.ttl=30 sec

A restart of your NiFi instances will be necessary for this change to take affect.

Matt

2 · Share

10 |6000 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Answer 2 · 2017-03-23T12:23:58Z

Answer by Roger Young · Mar 23, 2017 at 12:23 PM

Hi @Matt Clarke. I have been using nifi fine in a virtual machine. Recently i have it installed on my windows 10 host but i keep getting the same error as above even though i have configured the nifi.properties file as follows. I am just using localhost at the minute as i have minifi also installed for testing.

# Site to Site properties
nifi.remote.input.host=localhost
nifi.remote.input.secure=false
nifi.remote.input.socket.port=10000
nifi.remote.input.http.enabled=true
nifi.remote.input.http.transaction.ttl=30 sec

# web properties #
nifi.web.war.directory=./lib
nifi.web.http.host=
nifi.web.http.port=9191
nifi.web.https.host=
nifi.web.https.port=
nifi.web.jetty.working.directory=./work/jetty
nifi.web.jetty.threads=200

Is there any other configurations to be changed? Thank you

0 Show 1 · Share

10 |6000 characters needed characters left characters exceeded

Attachments: Up to 5 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Matt Clarke · Mar 23, 2017 at 12:35 PM 0

Share

@Roger Young

I assume the Remote Process Group (RPG) is on MiNiFi.

Try checking the following things:

1. NiFi will not fail startup if it cannot bind to the configured nifi.renote.input.socket.port. Make sure there are no other applications or NiFi instances running on this box that way have already bound to this port. Try using a different port and restarting

2. Since you are just testing, try leaving nifi.remote.input.host blank or setting it to 127.0.0.1 instead on your Windows 10 install.

Thanks,

Matt

'Remote instance of NiFi is not configured to allow RAW Socket site-to-site communications'

2 Replies

Your answer