You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/04 12:27:20 UTC

[jira] [Commented] (NIFI-1069) Nifi Service Status return 0 when service not running

    [ https://issues.apache.org/jira/browse/NIFI-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15545224#comment-15545224 ] 

ASF GitHub Bot commented on NIFI-1069:
--------------------------------------

GitHub user michalklempa opened a pull request:

    https://github.com/apache/nifi/pull/1093

    Fixes NIFI-1069 init script status exit code 3 when not running

    Fixes NIFI-1069 init script status exit code 3 when not running , 0 when running

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/michalklempa/nifi NIFI-1069_fix_init_status_exit_code

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1093.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1093
    
----
commit 460da679ed66e6d7ba1c93b06d5660f2d7a0a70b
Author: Michal Klempa <mi...@gmail.com>
Date:   2016-10-04T12:25:49Z

    Fixes NIFI-1069 init script status exit code 3 when not running, 0 when running

----


> Nifi Service Status return 0 when service not running
> -----------------------------------------------------
>
>                 Key: NIFI-1069
>                 URL: https://issues.apache.org/jira/browse/NIFI-1069
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.3.0
>         Environment: CentOS 6.7
>            Reporter: Andy Kruth
>            Priority: Minor
>
> After successfully installing Nifi as a service with the following command:
> sudo /opt/nifi-0.3.0/bin/nifi.sh install
> running service nifi status has a return code of 0.
> According to http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html if the service is not running then status should return 3.
> This is not a major issue, you can still start and stop the service just fine, but when using an idempotent tool like Ansible you cannot start the service because the return code of status says the service is already started.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)