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

Edgardo Vega commented on NIFI-2163:
------------------------------------

I just reviewed it. It did not work. I did service nifi status while it was 
running. Then got exit code 0 then service nifi stop. Then service nifi status 
and still go exit code 0 instead of 3.

I also found two other issues.

1) The defaultCharset / locale isnt being set correct
2) When i do ssh <ip> sudo service nifi restart or start nifi closes when the 
command completes. Other service do not have this problem. 

I also noticed that the nifi.sh points to karaf which has a template for 
services that looks nothing like what is being produced. 
https://raw.githubusercontent.com/apache/karaf/master/assemblies/features/base/src/main/resources/resources/bin/contrib/karaf-service-template.init-redhat

I think the first additional problem I found is because this isn't included  ". 
/etc/init.d/functions" and the second because of lines 75-83 where it uses 
daemon or forces it to run in the background.

Cheers,

Edgardo

> Nifi Service does not follow LSB Sevice Spec
> --------------------------------------------
>
>                 Key: NIFI-2163
>                 URL: https://issues.apache.org/jira/browse/NIFI-2163
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 1.0.0, 0.7.0
>         Environment: Centos
>            Reporter: Edgardo Vega
>            Assignee: Puspendu Banerjee
>            Priority: Critical
>              Labels: platform-consistency
>
> Trying to use the lastest off master with nifi.sh and nifi-env.sh and they do 
> not follow the spec for services, whcih causes some configuration tools not 
> to work as they use the return codes to determine if things are running, 
> dead, or stopped.
> http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html



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

Reply via email to