You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/01/24 17:08:37 UTC
[jira] [Commented] (AMBARI-4412) Deployment fails without reporting
cause of "ServiceComponent" erros.
[ https://issues.apache.org/jira/browse/AMBARI-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881092#comment-13881092 ]
jay vyas commented on AMBARI-4412:
----------------------------------
Just to clarify : I can clearly see that my YUM repos are in both machines of my cluster...
{noformat}
[root@mrg11 ~]# yum repolist 2>&1 | grep 'HDP\|AMBARI' && ssh mrg12 "yum repolist 2>&1 | grep 'HDP\|AMBARI'"
AMBARI.1.4.4-1.x Ambari 1.x 6
HDP-2.0.6.GlusterFS HDP 131+25
HDP-UTILS-1.1.0.16 Hortonworks Data Platform Utils Version - HDP-UTI 61
AMBARI.1.4.4-1.x Ambari 1.x 6
HDP-2.0.6.GlusterFS HDP 131+25
HDP-UTILS-1.1.0.16 Hortonworks Data Platform Utils Version - HDP-UTI 61
{noformat}
> Deployment fails without reporting cause of "ServiceComponent" erros.
> ----------------------------------------------------------------------
>
> Key: AMBARI-4412
> URL: https://issues.apache.org/jira/browse/AMBARI-4412
> Project: Ambari
> Issue Type: Bug
> Reporter: jay vyas
>
> - I'm finding that deployment fails ,but the only way to see whay istailing the ambari-server.log file (at bottom of this jira).
> - Issue 1: The web ui should probably suggest to users to look in ambari-server.log when failures occur OR else paste the logs for the user.
> - Issue 2 : The logs themselves don't seem to report anything that can be interpretted... So the logging should be improved to better describe the SVCCOMP_OP_FAILED failures.
> {noformat}
> redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:20,589 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=SQOOP, hostName=mrg11.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:25,856 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=SQOOP, hostName=mrg11.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 09:30:25,859 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=YARN_CLIENT, hostName=mrg11.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:30,106 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=ZOOKEEPER_CLIENT, hostName=mrg12.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:36,083 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=YARN_CLIENT, hostName=mrg11.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:40,160 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=ZOOKEEPER_CLIENT, hostName=mrg12.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:45,336 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=ZOOKEEPER_CLIENT, hostName=mrg12.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 09:30:45,337 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=ZOOKEEPER_SERVER, hostName=mrg12.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:46,136 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=YARN_CLIENT, hostName=mrg11.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> 09:30:51,130 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=YARN_CLIENT, hostName=mrg11.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 09:30:51,131 ERROR [qtp568526935-152] ServiceComponentHostImpl:716 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=ZOOKEEPER_CLIENT, hostName=mrg11.lab.bos.redhat.com, currentState=INSTALL_FAILED, eventType=HOST_SVCCOMP_OP_IN_PROGRESS, event=EventType: HOST_SVCCOMP_OP_IN_PROGRESS
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)