You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Michael Harp (JIRA)" <ji...@apache.org> on 2014/05/30 02:11:01 UTC
[jira] [Updated] (AMBARI-5888) Nagios is not stopping on sles11
[ https://issues.apache.org/jira/browse/AMBARI-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Harp updated AMBARI-5888:
---------------------------------
Description:
`service nagios start` creates /var/run/nagios/nagios.pid correctly but `service nagios stop` checks /var/run/nagios.pid for the process id and the kill command fails since /var/run/nagios.pid is an empty file.
This error is caused by hardcoded pid location in /etc/init.d/nagios, "NagiosRunFile=/var/run/nagios.pid". Changing to "NagiosRunFile=/var/run/nagios/nagios.pid" is our current workaround.
was:
`service flume start` creates /var/run/nagios/nagios.pid correctly but `service flume stop` checks /var/run/nagios.pid for the process id and the kill command fails since /var/run/nagios.pid is an empty file.
This error is caused by hardcoded pid location in /etc/init.d/nagios, "NagiosRunFile=/var/run/nagios.pid". Changing to "NagiosRunFile=/var/run/nagios/nagios.pid" is our current workaround.
> Nagios is not stopping on sles11
> --------------------------------
>
> Key: AMBARI-5888
> URL: https://issues.apache.org/jira/browse/AMBARI-5888
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: sles11 Only issue
> Reporter: Michael Harp
> Priority: Critical
> Fix For: 1.6.1
>
>
> `service nagios start` creates /var/run/nagios/nagios.pid correctly but `service nagios stop` checks /var/run/nagios.pid for the process id and the kill command fails since /var/run/nagios.pid is an empty file.
> This error is caused by hardcoded pid location in /etc/init.d/nagios, "NagiosRunFile=/var/run/nagios.pid". Changing to "NagiosRunFile=/var/run/nagios/nagios.pid" is our current workaround.
--
This message was sent by Atlassian JIRA
(v6.2#6252)