You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2012/09/12 11:49:08 UTC
[jira] [Created] (WHIRR-651) Failure of the JT to start up due to a
bad user name doesn't get picked up
Steve Loughran created WHIRR-651:
------------------------------------
Summary: 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
[jira] [Commented] (WHIRR-651) Failure of the JT to start up due to
a bad user name doesn't get picked up
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453911#comment-13453911 ]
Steve Loughran commented on WHIRR-651:
--------------------------------------
Installation is 1.0.3 from RPMs; service not in svn yet. I'm sure the config problem is in my side (user creation?)
However, failure isn't being picked up, probably because the hadoop-daemon script isn't registering the problem
> 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
[jira] [Updated] (WHIRR-651) Failure of the JT to start up due to a
bad user name doesn't get picked up
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated WHIRR-651:
---------------------------------
Comment: was deleted
(was: Whirr log
{code}
+ echo 'Starting hadoop-jobtracker'
+ service hadoop-jobtracker start
chown: invalid user: `hadoop'
/usr/lib/hadoop/bin/hadoop-daemon.sh: line 135: /var/log/hadoop/logs/hadoop-hadoop-jobtracker-nn1.out: Permission denied
head: cannot open `/var/log/hadoop/logs/hadoop-hadoop-jobtracker-nn1.out' for reading: No such file or directory
+ retval=0
+ (( 0 == 0 ))
+ echo 'Service hadoop-jobtracker is started'
+ CONFIGURE_HADOOP_DONE=1
{code})
> 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
[jira] [Commented] (WHIRR-651) Failure of the JT to start up due to
a bad user name doesn't get picked up
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453869#comment-13453869 ]
Steve Loughran commented on WHIRR-651:
--------------------------------------
{code}
+ echo 'Starting hadoop-jobtracker'
+ service hadoop-jobtracker start
chown: invalid user: `hadoop'
/usr/lib/hadoop/bin/hadoop-daemon.sh: line 135: /var/log/hadoop/logs/hadoop-hadoop-jobtracker-nn1: Permission denied
head: cannot open `/var/log/hadoop/logs/hadoop-hadoop-jobtracker-nn1' for reading: No such file or directory
+ retval=0
+ (( 0 == 0 ))
+ echo 'Service hadoop-jobtracker is started'
+ CONFIGURE_HADOOP_DONE=1
+ cat
+ cat
+ cat
+ cat
{code}
> 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
[jira] [Commented] (WHIRR-651) Failure of the JT to start up due to
a bad user name doesn't get picked up
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453870#comment-13453870 ]
Steve Loughran commented on WHIRR-651:
--------------------------------------
Whirr log
{code}
+ echo 'Starting hadoop-jobtracker'
+ service hadoop-jobtracker start
chown: invalid user: `hadoop'
/usr/lib/hadoop/bin/hadoop-daemon.sh: line 135: /var/log/hadoop/logs/hadoop-hadoop-jobtracker-nn1.out: Permission denied
head: cannot open `/var/log/hadoop/logs/hadoop-hadoop-jobtracker-nn1.out' for reading: No such file or directory
+ retval=0
+ (( 0 == 0 ))
+ echo 'Service hadoop-jobtracker is started'
+ CONFIGURE_HADOOP_DONE=1
{code}
> 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
[jira] [Commented] (WHIRR-651) Failure of the JT to start up due to
a bad user name doesn't get picked up
Posted by "Karel Vervaeke (JIRA)" <ji...@apache.org>.
[ 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