nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tanezavm <vft.biz...@gmail.com>
Subject NiFi 1.5.0 can't start with AWS public ip is set to nifi.web.https.host
Date Wed, 21 Feb 2018 21:01:00 GMT
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/

Mime
View raw message