incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-1587) Trouble starting some services
Date Fri, 08 Mar 2013 03:16:12 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mahadev konar updated AMBARI-1587:
----------------------------------

    Fix Version/s: 1.3.0
    
> Trouble starting some services
> ------------------------------
>
>                 Key: AMBARI-1587
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1587
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Dustine Rene Bernasor
>            Priority: Blocker
>             Fix For: 1.3.0
>
>         Attachments: ambari-server.tar.gz
>
>
> I was setting up a cluster with the following set-up
> Crawler51 (9GB)
> * NameNode
> * SNameNode
> * JobTracker
> * HBase Master
> * Nagios Server
> * Ganglia Server
> * Client (HDFS, MapReduce, Piq, Sqoop...)
> Crawler52 (9GB)
> * DataNode
> * TaskTracker
> * ZooKeeper Server
> * HBase RegionServer
> * Client
> Crawler53 (9GB)
> * DataNode
> * TaskTracker
> * ZooKeeper Server
> * HBase RegionServer
> * Client
> Crawler57 (2GB)
> * DataNode
> * TaskTracker
> * ZooKeeper Server
> * HBase RegionServer
> * Client
> Crawler58 (2GB)
> * DataNode
> * TaskTracker
> * HBase RegionServer
> * Client
> Crawler59 (2GB)
> * DataNode
> * TaskTracker
> * HBase RegionServer
> * Client
> Everything is ok, however during the Install, Start, and Test step, some of the services
could not be started (HBase Master, Nagios). There is nothing in the stderr for these services.
For the HDFS Check execute, I got this in the
> stderr "Puppet has been killed due to timeout".
> When I go to the Dashboard and attempt to start either of them,
> they cannot be started.

--
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

Mime
View raw message