You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/05/24 01:11:20 UTC
[jira] [Resolved] (HADOOP-9546) "setsid exited with exit code"
message on each hadoop command
[ https://issues.apache.org/jira/browse/HADOOP-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe resolved HADOOP-9546.
--------------------------------
Resolution: Duplicate
Fixed by HADOOP-9593.
> "setsid exited with exit code" message on each hadoop command
> -------------------------------------------------------------
>
> Key: HADOOP-9546
> URL: https://issues.apache.org/jira/browse/HADOOP-9546
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Jason Lowe
>
> Each hadoop command is printing an INFO message about a setsid exit code. This is at best annoying, and it prevents the start-dfs.sh startup script from working properly since the INFO message is interpreted as more namenode hosts to connect to. start-dfs.sh uses {{hdfs getconf -namenodes}} which like other hadoop commands prints the extra INFO message. For example:
> {noformat}
> $ hdfs getconf -namenodes
> 2013-05-06 20:11:22,096 INFO [main] util.Shell (Shell.java:isSetsidSupported(311)) - setsid exited with exit code 0
> localhost
> {noformat}
--
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