If the firewall isn't the problem, there could be a resource conflict for the port. On CentOS,
netstat -ant > will show the listening and connected ports. If something shows on LocalAddress=0.0.0.0:8080 or <host_ip>:8080 and State=LISTEN, then the port is already in use by another process. You find the process with netstat -pant > which will include a column with information about the process that is using the port. (Ubuntu syntax should be similar, but check the manpage if these parameters don't work as expected.) On Thu, Aug 27, 2015 at 11:55 AM, Joe Witt <joe.w...@gmail.com> wrote: > Chris, > > Also please take a look in the 'logs/nifi-app.log' and > 'logs/nifi-bootstrap.log' to see if there is anything interesting > there. > > Thanks > Joe > > On Thu, Aug 27, 2015 at 11:53 AM, Corey Flowers <cflow...@onyxpoint.com> > wrote: > > Check your firewalls. If you have a running instance and can't open the > > graph, the firewall is the first place to start. If there is a conflict > on > > the port, you will see it in the app log. It will say something like > "Port > > XXXX already in use" but if it starts and seems to be running fine, then > it > > is probably your firewalls. > > > > On Thu, Aug 27, 2015 at 11:42 AM, Chris Teoh <chris.t...@gmail.com> > wrote: > >> > >> Hey all, > >> > >> I've noticed trying to run Nifi on Centos 7 and a docker Ubuntu image > >> doesn't seem to launch the server. > >> > >> Is there something I'm missing here? > >> > >> Kind regards > >> Chris > > > > > > > > > > -- > > Corey Flowers > > Vice President, Onyx Point, Inc > > (410) 541-6699 > > cflow...@onyxpoint.com > > > > -- This account not approved for unencrypted proprietary information -- >
