[ https://issues.apache.org/jira/browse/NIFI-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389937#comment-16389937 ]
Matt Burgess commented on NIFI-3551: ------------------------------------ Is this a duplicate of NIFI-528? > ExecuteStreamCommand processor does not know that .sh script has become a > zombie or killed > ------------------------------------------------------------------------------------------ > > Key: NIFI-3551 > URL: https://issues.apache.org/jira/browse/NIFI-3551 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.1.0 > Environment: Linux RHEL 6.5 > Reporter: Olav Jordens > Priority: Minor > Attachments: ExecuteStreamCommandZombie.png > > > I have a workflow which periodically runs a .sh script using > ExecuteStreamCommand processor which usually takes a few minutes. This > morning, I noticed that the resulting flow had not produced anything for > almost a day. I checked on my Linux box and saw that the .sh script had been > running for almost a day - Something must have been wrong here, so killed the > process from the command line. However, the Nifi processor will not stop. It > continues to show active processes. Restarting the nifi process resolves > this, but this is a radical solution on a production system. > In the image I have shown the zombie extracted from the running workflow. -- This message was sent by Atlassian JIRA (v7.6.3#76005)