Hi Matt, started vis bin/nifi.sh start
Logs do not show anything interesting. Indeed, I see the mentioned lines, but a curl on http://localhost:9090/nifi returns curl: (52) Empty reply from server Bootstrap logs shows: 2017-06-12 18:01:50,459 INFO [main] o.a.n.b.NotificationServiceManager Successfully loaded the following 0 services: [] 2017-06-12 18:01:50,462 INFO [main] org.apache.nifi.bootstrap.RunNiFi Registered no Notification Services for Notification Type NIFI_STARTED 2017-06-12 18:01:50,462 INFO [main] org.apache.nifi.bootstrap.RunNiFi Registered no Notification Services for Notification Type NIFI_STOPPED 2017-06-12 18:01:50,462 INFO [main] org.apache.nifi.bootstrap.RunNiFi Registered no Notification Services for Notification Type NIFI_DIED 2017-06-12 18:01:50,487 INFO [main] org.apache.nifi.bootstrap.Command Starting Apache NiFi... 2017-06-12 18:01:50,488 INFO [main] org.apache.nifi.bootstrap.Command Working Directory: /opt/nifi/nifi-1.2.0-SNAPSHOT 2017-06-12 18:01:50,488 INFO [main] org.apache.nifi.bootstrap.Command Command: /lib/jvm/java-openjdk/bin/java -classpath /opt/nifi/nifi-1.2.0-SNAPSHOT/./conf:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/nifi-properties-1.2.0-SNAPSHOT.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/nifi-nar-utils-1.2.0-SNAPSHOT.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/nifi-runtime-1.2.0-SNAPSHOT.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/nifi-framework-api-1.2.0-SNAPSHOT.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/log4j-over-slf4j-1.7.12.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/jcl-over-slf4j-1.7.12.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/ojdbc6.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/jul-to-slf4j-1.7.12.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/nifi-api-1.2.0-SNAPSHOT.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/logback-classic-1.1.3.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/slf4j-api-1.7.12.jar:/opt/nifi/nifi-1.2.0-SNAPSHOT/./lib/logback-core-1.1.3.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m -Djava.library.path=/usr/hdp/2.6.0.3-8/hadoop/lib -Djava.security.egd=file:/dev/urandom -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -XX:+UseG1GC -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dnifi.properties.file.path=/opt/nifi/nifi-1.2.0-SNAPSHOT/./conf/nifi.properties -Dnifi.bootstrap.listen.port=37055 -Dapp=NiFi -Dorg.apache.nifi.bootstrap.config.log.dir=/opt/nifi/nifi-1.2.0-SNAPSHOT/logs org.apache.nifi.NiFi 2017-06-12 18:01:50,506 INFO [main] org.apache.nifi.bootstrap.Command Launched Apache NiFi with Process ID 20304 2017-06-12 18:01:51,063 INFO [NiFi Bootstrap Command Listener] org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening for Bootstrap requests on port 44585 App log shows https://gist.github.com/geoHeil/9df1947ab7ddb5027c67669aa0f83d0e Regards, Georg Matt Gilman <matt.c.gil...@gmail.com> schrieb am Mo., 12. Juni 2017 um 15:13 Uhr: > Georg, > > The UI will be available once you see these log messages: > > 2017-06-09 09:02:37,208 INFO [main] org.apache.nifi.web.server.JettyServer > NiFi has started. The UI is available at the following URLs: > 2017-06-09 09:02:37,208 INFO [main] org.apache.nifi.web.server.JettyServer > http://<host>:<port>/nifi > 2017-06-09 09:02:37,208 INFO [main] org.apache.nifi.web.server.JettyServer > http://<host>:<port>/nifi > > If you search through the logs looking for the port you're configured to > listen on, do you find anything? If these haven't printed yet, the UI will > not be available. If they have, then the UI should be available. > > Also, anything interesting in the bootstrap log? > > Thanks > > Matt > > > On Mon, Jun 12, 2017 at 9:09 AM, Georg Heiler <georg.kf.hei...@gmail.com> > wrote: > >> After restarting my NiFi host no longer the NiFi web interface will >> start. From the logs it looks like everything lese of NiFi is working fine. >> >> a curl to localhost:<NiFiPort> will return an empty response. >> >> What else can I try? >> The logs do not show any errors. >> >> Regards, >> Georg >> > >
