You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2014/06/26 00:56:28 UTC

[jira] [Commented] (AMBARI-5888) Nagios Alerts On SLES Toggle In Maintenance Mode

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

Jonathan Hurley commented on AMBARI-5888:
-----------------------------------------

I believe this behavior is due to the nagios process never dying. When multiple nagios processes are running, the state changes are not persisted properly to the status.dat.
This would also make sense why this happens on SLES but not others since it seems to be a process/PID issue.

> Nagios Alerts On SLES Toggle In Maintenance Mode
> ------------------------------------------------
>
>                 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
>            Assignee: Jonathan Hurley
>            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)