You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by tanezavm <vf...@gmail.com> on 2018/02/21 21:01:00 UTC
NiFi 1.5.0 can't start with AWS public ip is set to
nifi.web.https.host
Deployed an instance in AWS, configured NiFi for secure access and set
nifi.web.https.host with the instance's public ip but it seems nifi can't
start successfully with errors below:
2018-02-21 15:33:11,915 WARN [main] org.apache.nifi.web.server.JettyServer
Failed to start web server... shutting down.
java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:298)
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:431)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.apache.nifi.web.server.JettyServer.start(JettyServer.java:777)
at org.apache.nifi.NiFi.<init>(NiFi.java:160)
at org.apache.nifi.NiFi.main(NiFi.java:268)
2018-02-21 15:33:11,916 INFO [Thread-1] org.apache.nifi.NiFi Initiating
shutdown of Jetty web server...
2018-02-21 15:33:11,920 INFO [Thread-1]
o.eclipse.jetty.server.AbstractConnector Stopped
ServerConnector@55b655b4{SSL,[ssl, http/1.1]}{34.203.229.59:9443}
2018-02-21 15:33:11,920 INFO [Thread-1] org.eclipse.jetty.server.session
Stopped scavenging
Note: This setup works with previous versions specifically 1.1.2.
Do we have some workaround for this case?
Thanks.
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Re: NiFi 1.5.0 can't start with AWS public ip is set to
nifi.web.https.host
Posted by tanezavm <vf...@gmail.com>.
Hi Andy,
No other service is running on the instance in that port. Previous nifi
instance is shutdown too. Using the instance private IP though seemed to
work. Maybe this new NiFi does not allow to be configured with an IP that is
not associated to the interfaces?
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Re: NiFi 1.5.0 can't start with AWS public ip is set to
nifi.web.https.host
Posted by tanezavm <vf...@gmail.com>.
Hi Charlie,
Thanks for the tip. NiFi seemed to successfuly start when I set
nifi.web.https.network.interface.default to a particular interface (in my
case, eth0).
Regards,
Virgil
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Re: NiFi 1.5.0 can't start with AWS public ip is set to nifi.web.https.host
Posted by Charlie Meyer <ch...@civitaslearning.com>.
i ran into that earlier today actually, setting the
nifi.web.http(s).network.interface* fixed the issue for me
-Charlie
On Wed, Feb 21, 2018 at 4:48 PM, tanezavm <vf...@gmail.com> wrote:
> Hi Andy,
>
> As far as I know, there's no other services running in the instance that is
> preventing NiFi from binding to it. Previous NiFi instance was shutdown
> too.
> Does this version of NiFi allows to be configured with an IP that is not
> associated to any of the interfaces? Since It worked with using the private
> IP of the instance.
>
> Regards,
> Virgil
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>
Re: NiFi 1.5.0 can't start with AWS public ip is set to
nifi.web.https.host
Posted by tanezavm <vf...@gmail.com>.
Hi Andy,
As far as I know, there's no other services running in the instance that is
preventing NiFi from binding to it. Previous NiFi instance was shutdown too.
Does this version of NiFi allows to be configured with an IP that is not
associated to any of the interfaces? Since It worked with using the private
IP of the instance.
Regards,
Virgil
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Re: NiFi 1.5.0 can't start with AWS public ip is set to nifi.web.https.host
Posted by Andy LoPresto <al...@apache.org>.
Hi,
Is there another service running on this instance that is preventing NiFi from binding to it? Did you shut down your previous instance of NiFi?
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Feb 21, 2018, at 1:01 PM, tanezavm <vf...@gmail.com> wrote:
>
> Deployed an instance in AWS, configured NiFi for secure access and set
> nifi.web.https.host with the instance's public ip but it seems nifi can't
> start successfully with errors below:
>
>
> 2018-02-21 15:33:11,915 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> java.net.BindException: Cannot assign requested address
> at sun.nio.ch.Net.bind0(Native Method)
> at sun.nio.ch.Net.bind(Net.java:433)
> at sun.nio.ch.Net.bind(Net.java:425)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:298)
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at org.eclipse.jetty.server.Server.doStart(Server.java:431)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:777)
> at org.apache.nifi.NiFi.<init>(NiFi.java:160)
> at org.apache.nifi.NiFi.main(NiFi.java:268)
> 2018-02-21 15:33:11,916 INFO [Thread-1] org.apache.nifi.NiFi Initiating
> shutdown of Jetty web server...
> 2018-02-21 15:33:11,920 INFO [Thread-1]
> o.eclipse.jetty.server.AbstractConnector Stopped
> ServerConnector@55b655b4{SSL,[ssl, http/1.1]}{34.203.229.59:9443}
> 2018-02-21 15:33:11,920 INFO [Thread-1] org.eclipse.jetty.server.session
> Stopped scavenging
>
> Note: This setup works with previous versions specifically 1.1.2.
>
> Do we have some workaround for this case?
> Thanks.
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/