[
https://issues.apache.org/jira/browse/WHIRR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453876#comment-13453876
]
Karel Vervaeke commented on WHIRR-651:
--------------------------------------
The problem is IMO that the correct behaviour for whirr (in case of different
types of failures) isn't really defined.
The 'correct behaviour' would be not to fail to begin with ;-)
The actual user depends on how you install hadoop (tarball or cdh).
Assuming you are using cdh: did you change both install-function and
configure-function to use the cdh variants?
> Failure of the JT to start up due to a bad user name doesn't get picked up
> --------------------------------------------------------------------------
>
> Key: WHIRR-651
> URL: https://issues.apache.org/jira/browse/WHIRR-651
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.8.1
> Environment: BYON
> Reporter: Steve Loughran
> Priority: Minor
>
> A service failed to start because the chmod command failed, yet this didn't
> get picked up by whirr. It may be an init.d script issue -it isn't checking
> the return value of chmod.
--
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
