You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jim Cistaro (JIRA)" <ji...@apache.org> on 2013/08/07 21:25:48 UTC
[jira] [Created] (AMBARI-2837) gmond cannot be started after stop
due to stale pid files.
Jim Cistaro created AMBARI-2837:
-----------------------------------
Summary: gmond cannot be started after stop due to stale pid files.
Key: AMBARI-2837
URL: https://issues.apache.org/jira/browse/AMBARI-2837
Project: Ambari
Issue Type: Bug
Environment: Latest version of ambari/hdp using hdp 1.3.0
Reporter: Jim Cistaro
Priority: Minor
I noticed an issue for first time today. On a cluster set up today… after stopping ganglia, it fails to restart. It appears that stopping hdp gmond does not remove the pid files and this causes a problem when you try to start and they still exist. Removing stale pid files fixes.
I believe, but not certain, that this was working ok for clusters I set up within the last few days.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira