You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Ramya Sunil (JIRA)" <ji...@apache.org> on 2012/05/26 19:21:22 UTC
[jira] [Created] (AMBARI-439) Gmetad start fails sometimes.
Ramya Sunil created AMBARI-439:
----------------------------------
Summary: Gmetad start fails sometimes.
Key: AMBARI-439
URL: https://issues.apache.org/jira/browse/AMBARI-439
Project: Ambari
Issue Type: Bug
Affects Versions: ambari-186
Reporter: Ramya Sunil
Assignee: Ramya Sunil
Mahadev's investigation of a failure on Suresh's test system:
612 => "Thu May 24 03:35:28 -0400 2012
Servicehdp-gmetad(provider=redhat) (debug): Executing '/sbin/service
hdp-gmetad start'" 613 => "Thu May 24 03:35:28
-0400 2012 /Stagemain/Hdp-ganglia::Service::Gmetad/Servicehdp-gmetad/ensure
(err): change from stopped to ru
nning failed: Could not start Servicehdp-gmetad: Execution of
'/sbin/service hdp-gmetad start' returned 1: at
/etc/puppet/agent/modules/hdp-ganglia/manifests/init.pp:65"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-439) Gmetad start fails sometimes.
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated AMBARI-439:
-------------------------------------------
Affects Version/s: (was: ambari-186)
0.9.0
> Gmetad start fails sometimes.
> -----------------------------
>
> Key: AMBARI-439
> URL: https://issues.apache.org/jira/browse/AMBARI-439
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Ramya Sunil
> Assignee: Ramya Sunil
> Fix For: 0.9.0
>
> Attachments: AMBARI-439-1.patch, AMBARI-439-2.patch, AMBARI-439.patch
>
>
> Mahadev's investigation of a failure on Suresh's test system:
> 612 => "Thu May 24 03:35:28 -0400 2012
> Servicehdp-gmetad(provider=redhat) (debug): Executing '/sbin/service
> hdp-gmetad start'" 613 => "Thu May 24 03:35:28
> -0400 2012 /Stagemain/Hdp-ganglia::Service::Gmetad/Servicehdp-gmetad/ensure
> (err): change from stopped to ru
> nning failed: Could not start Servicehdp-gmetad: Execution of
> '/sbin/service hdp-gmetad start' returned 1: at
> /etc/puppet/agent/modules/hdp-ganglia/manifests/init.pp:65"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMBARI-439) Gmetad start fails sometimes.
Posted by "Vikram Dixit K (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vikram Dixit K resolved AMBARI-439.
-----------------------------------
Resolution: Fixed
Fix Version/s: ambari-186
Committed. Thanks Ramya!
> Gmetad start fails sometimes.
> -----------------------------
>
> Key: AMBARI-439
> URL: https://issues.apache.org/jira/browse/AMBARI-439
> Project: Ambari
> Issue Type: Bug
> Affects Versions: ambari-186
> Reporter: Ramya Sunil
> Assignee: Ramya Sunil
> Fix For: ambari-186
>
> Attachments: AMBARI-439-1.patch, AMBARI-439-2.patch, AMBARI-439.patch
>
>
> Mahadev's investigation of a failure on Suresh's test system:
> 612 => "Thu May 24 03:35:28 -0400 2012
> Servicehdp-gmetad(provider=redhat) (debug): Executing '/sbin/service
> hdp-gmetad start'" 613 => "Thu May 24 03:35:28
> -0400 2012 /Stagemain/Hdp-ganglia::Service::Gmetad/Servicehdp-gmetad/ensure
> (err): change from stopped to ru
> nning failed: Could not start Servicehdp-gmetad: Execution of
> '/sbin/service hdp-gmetad start' returned 1: at
> /etc/puppet/agent/modules/hdp-ganglia/manifests/init.pp:65"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-439) Gmetad start fails sometimes.
Posted by "Ramya Sunil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramya Sunil updated AMBARI-439:
-------------------------------
Attachment: AMBARI-439-2.patch
> Gmetad start fails sometimes.
> -----------------------------
>
> Key: AMBARI-439
> URL: https://issues.apache.org/jira/browse/AMBARI-439
> Project: Ambari
> Issue Type: Bug
> Affects Versions: ambari-186
> Reporter: Ramya Sunil
> Assignee: Ramya Sunil
> Attachments: AMBARI-439-1.patch, AMBARI-439-2.patch, AMBARI-439.patch
>
>
> Mahadev's investigation of a failure on Suresh's test system:
> 612 => "Thu May 24 03:35:28 -0400 2012
> Servicehdp-gmetad(provider=redhat) (debug): Executing '/sbin/service
> hdp-gmetad start'" 613 => "Thu May 24 03:35:28
> -0400 2012 /Stagemain/Hdp-ganglia::Service::Gmetad/Servicehdp-gmetad/ensure
> (err): change from stopped to ru
> nning failed: Could not start Servicehdp-gmetad: Execution of
> '/sbin/service hdp-gmetad start' returned 1: at
> /etc/puppet/agent/modules/hdp-ganglia/manifests/init.pp:65"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-439) Gmetad start fails sometimes.
Posted by "Ramya Sunil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramya Sunil updated AMBARI-439:
-------------------------------
Attachment: AMBARI-439.patch
> Gmetad start fails sometimes.
> -----------------------------
>
> Key: AMBARI-439
> URL: https://issues.apache.org/jira/browse/AMBARI-439
> Project: Ambari
> Issue Type: Bug
> Affects Versions: ambari-186
> Reporter: Ramya Sunil
> Assignee: Ramya Sunil
> Attachments: AMBARI-439.patch
>
>
> Mahadev's investigation of a failure on Suresh's test system:
> 612 => "Thu May 24 03:35:28 -0400 2012
> Servicehdp-gmetad(provider=redhat) (debug): Executing '/sbin/service
> hdp-gmetad start'" 613 => "Thu May 24 03:35:28
> -0400 2012 /Stagemain/Hdp-ganglia::Service::Gmetad/Servicehdp-gmetad/ensure
> (err): change from stopped to ru
> nning failed: Could not start Servicehdp-gmetad: Execution of
> '/sbin/service hdp-gmetad start' returned 1: at
> /etc/puppet/agent/modules/hdp-ganglia/manifests/init.pp:65"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-439) Gmetad start fails sometimes.
Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated AMBARI-439:
-------------------------------------------
Fix Version/s: (was: ambari-186)
0.9.0
> Gmetad start fails sometimes.
> -----------------------------
>
> Key: AMBARI-439
> URL: https://issues.apache.org/jira/browse/AMBARI-439
> Project: Ambari
> Issue Type: Bug
> Affects Versions: ambari-186
> Reporter: Ramya Sunil
> Assignee: Ramya Sunil
> Fix For: 0.9.0
>
> Attachments: AMBARI-439-1.patch, AMBARI-439-2.patch, AMBARI-439.patch
>
>
> Mahadev's investigation of a failure on Suresh's test system:
> 612 => "Thu May 24 03:35:28 -0400 2012
> Servicehdp-gmetad(provider=redhat) (debug): Executing '/sbin/service
> hdp-gmetad start'" 613 => "Thu May 24 03:35:28
> -0400 2012 /Stagemain/Hdp-ganglia::Service::Gmetad/Servicehdp-gmetad/ensure
> (err): change from stopped to ru
> nning failed: Could not start Servicehdp-gmetad: Execution of
> '/sbin/service hdp-gmetad start' returned 1: at
> /etc/puppet/agent/modules/hdp-ganglia/manifests/init.pp:65"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-439) Gmetad start fails sometimes.
Posted by "Ramya Sunil (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramya Sunil updated AMBARI-439:
-------------------------------
Attachment: AMBARI-439-1.patch
Patch to patch the above fix.
> Gmetad start fails sometimes.
> -----------------------------
>
> Key: AMBARI-439
> URL: https://issues.apache.org/jira/browse/AMBARI-439
> Project: Ambari
> Issue Type: Bug
> Affects Versions: ambari-186
> Reporter: Ramya Sunil
> Assignee: Ramya Sunil
> Attachments: AMBARI-439-1.patch, AMBARI-439.patch
>
>
> Mahadev's investigation of a failure on Suresh's test system:
> 612 => "Thu May 24 03:35:28 -0400 2012
> Servicehdp-gmetad(provider=redhat) (debug): Executing '/sbin/service
> hdp-gmetad start'" 613 => "Thu May 24 03:35:28
> -0400 2012 /Stagemain/Hdp-ganglia::Service::Gmetad/Servicehdp-gmetad/ensure
> (err): change from stopped to ru
> nning failed: Could not start Servicehdp-gmetad: Execution of
> '/sbin/service hdp-gmetad start' returned 1: at
> /etc/puppet/agent/modules/hdp-ganglia/manifests/init.pp:65"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira