ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jay vyas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-4412) Deployment fails without reporting cause of "ServiceComponent" erros.
Date Sat, 25 Jan 2014 16:02:39 GMT

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

jay vyas commented on AMBARI-4412:
----------------------------------

For the curious : We have found that these sorts of errors can happen when you have repository
inconsitencies.  

Is a way to gaurd against these sorts of errors before deployment?  If so I'd say lets keep
this JIRA alive.

If 'not' , then maybe we can close the JIRA. 

Ideally, I'd love to see think if  some action that can be taken to make the install a little
more defensive against rpm/yum related errors 

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

Mime
View raw message