Mark Payne created NIFI-3436:
--------------------------------
Summary: Occasionally NiFi will indicate that it is not running
when trying to stop the process
Key: NIFI-3436
URL: https://issues.apache.org/jira/browse/NIFI-3436
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Reporter: Mark Payne
Assignee: Mark Payne
When I run "bin/nifi.sh stop" or "bin/nifi.sh restart" I occasionally see an
error indicating that NiFi is not currently running. I can then run "ps -ef |
grep nifi" and see the PID that is in the run/nifi.pid file, so it is clear
that the Process is in fact running, but NiFi thinks it is not.
When I look in logs/nifi-bootstrap.log I see:
2017-02-03 14:05:04,796 WARN [main] org.apache.nifi.bootstrap.RunNiFi Apache
NiFi appears to have died. Restarting...
2017-02-03 14:05:04,940 ERROR [NiFi logging handler] org.apache.nifi.StdErr
ERROR: transport error 202: bind failed: Address already in use
2017-02-03 14:05:04,941 ERROR [NiFi logging handler] org.apache.nifi.StdErr
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
2017-02-03 14:05:04,941 ERROR [NiFi logging handler] org.apache.nifi.StdErr
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[debugInit.c:750]
This was on a restart, hence the JDWP Transport dt_socket failed to initialize.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
