I think we found a solution. I am not exactly sure what has helped but
renewing kerberos tokens seems to have done the trick.
Georg Heiler schrieb am Di. 13. Juni 2017 um
10:44:
> Please see the logs below from the commands you suggested
>
> [root@devbox logs]# lsof -i
Please see the logs below from the commands you suggested
[root@devbox logs]# lsof -i :9090
COMMAND PIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME
ssh 11192 vagrant4u IPv6 225355 0t0 TCP localhost:websm
(LISTEN)
java20304root 1730u IPv4 2426500 0t0 TCP
Thanks I will try this later at work. Yesterday at a quick glance in
netstat it looked like the right pid was bound to 9090.
Andy LoPresto schrieb am Di. 13. Juni 2017 um 01:53:
> Hi Georg,
>
> Can you run a command to see if anything else is listening on those ports?
> If
Hi Georg,
Can you run a command to see if anything else is listening on those ports? If
another process is listening when NiFi tries to start, it should detect that
and stop itself, but if something else started listening after or
intermittently, it might be causing issues.
The command lsof
Hi,
to me it looks like NiFi is starting correctly, and only there is no access
to the web interface.
The curl is run from the same host. No firewall in between.
I downloaded and extracted a fresh copy of the latest NiFi (1.3) and
extracted it to a different folder. When started there, I could
Hey,
It looks like NiFi is correctly starting:
2017-06-12 18:02:09,570 INFO [main] org.apache.nifi.web.server.JettyServer
NiFi has started. The UI is available at the following URLs:
2017-06-12 18:02:09,570 INFO [main] org.apache.nifi.web.server.JettyServer
http://10.248.139.86:9090/nifi
Georg,
Thanks for providing the logs. They look very normal and I'm not sure why
it's not working without knowing more. Other than port 9090, any other
customized properties/configuration? Any firewalls that could be preventing
access to that port?
Thanks
Matt
On Mon, Jun 12, 2017 at 11:19 AM,
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
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://:/nifi