[
https://issues.apache.org/jira/browse/NIFI-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne resolved NIFI-3436.
------------------------------
Resolution: Cannot Reproduce
This Jira is almost 2 years old. I don't remember seeing this for a very long
time. Will close as Cannot Reproduce, as it appears to have been addressed.
> 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
> Priority: Major
>
> 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
(v8.3.4#803005)
