You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Johnny Zhang (JIRA)" <ji...@apache.org> on 2012/07/03 22:22:34 UTC

[jira] [Created] (BIGTOP-667) start hadoop-httpfs in SLES return 3 instead of 0

Johnny Zhang created BIGTOP-667:
-----------------------------------

             Summary: start hadoop-httpfs in SLES return 3 instead of 0
                 Key: BIGTOP-667
                 URL: https://issues.apache.org/jira/browse/BIGTOP-667
             Project: Bigtop
          Issue Type: Bug
    Affects Versions: 0.4.0
            Reporter: Johnny Zhang


this is a small issue, this only happened in SLES as I tested. 
when start/restart hadoop-httpfs in SLES, it still can bring up the service, however, the return code is 3 instead of 0
{noformat}
service hadoop-httpfs start
__EOT__
12/07/03 11:15:39 TRACE shell.Shell: return: 3
12/07/03 11:15:39 TRACE shell.Shell:
<stdout>
Starting Hadoop httpfs: ..done
......
service hadoop-httpfs restart
__EOT__
12/07/03 11:15:48 TRACE shell.Shell: return: 3
12/07/03 11:15:48 TRACE shell.Shell:
<stdout>
Stopping Hadoop httpfs: ..done
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (BIGTOP-667) start hadoop-httpfs in SLES return 3 instead of 0

Posted by "Sean Mackrory (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory reassigned BIGTOP-667:
------------------------------------

    Assignee: Sean Mackrory
    
> start hadoop-httpfs in SLES return 3 instead of 0
> -------------------------------------------------
>
>                 Key: BIGTOP-667
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-667
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Johnny Zhang
>            Assignee: Sean Mackrory
>
> this is a small issue, this only happened in SLES as I tested. 
> when start/restart hadoop-httpfs in SLES, it still can bring up the service, however, the return code is 3 instead of 0
> {noformat}
> service hadoop-httpfs start
> __EOT__
> 12/07/03 11:15:39 TRACE shell.Shell: return: 3
> 12/07/03 11:15:39 TRACE shell.Shell:
> <stdout>
> Starting Hadoop httpfs: ..done
> ......
> service hadoop-httpfs restart
> __EOT__
> 12/07/03 11:15:48 TRACE shell.Shell: return: 3
> 12/07/03 11:15:48 TRACE shell.Shell:
> <stdout>
> Stopping Hadoop httpfs: ..done
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-667) start hadoop-httpfs in SLES return 3 instead of 0

Posted by "Peter Linnell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439184#comment-13439184 ] 

Peter Linnell commented on BIGTOP-667:
--------------------------------------

+1 LGTM
                
> start hadoop-httpfs in SLES return 3 instead of 0
> -------------------------------------------------
>
>                 Key: BIGTOP-667
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-667
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Johnny Zhang
>            Assignee: Sean Mackrory
>         Attachments: BIGTOP-667.patch
>
>
> this is a small issue, this only happened in SLES as I tested. 
> when start/restart hadoop-httpfs in SLES, it still can bring up the service, however, the return code is 3 instead of 0
> {noformat}
> service hadoop-httpfs start
> __EOT__
> 12/07/03 11:15:39 TRACE shell.Shell: return: 3
> 12/07/03 11:15:39 TRACE shell.Shell:
> <stdout>
> Starting Hadoop httpfs: ..done
> ......
> service hadoop-httpfs restart
> __EOT__
> 12/07/03 11:15:48 TRACE shell.Shell: return: 3
> 12/07/03 11:15:48 TRACE shell.Shell:
> <stdout>
> Stopping Hadoop httpfs: ..done
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BIGTOP-667) start hadoop-httpfs in SLES return 3 instead of 0

Posted by "Sean Mackrory (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Mackrory updated BIGTOP-667:
---------------------------------

    Attachment: BIGTOP-667.patch
    
> start hadoop-httpfs in SLES return 3 instead of 0
> -------------------------------------------------
>
>                 Key: BIGTOP-667
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-667
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>            Reporter: Johnny Zhang
>            Assignee: Sean Mackrory
>         Attachments: BIGTOP-667.patch
>
>
> this is a small issue, this only happened in SLES as I tested. 
> when start/restart hadoop-httpfs in SLES, it still can bring up the service, however, the return code is 3 instead of 0
> {noformat}
> service hadoop-httpfs start
> __EOT__
> 12/07/03 11:15:39 TRACE shell.Shell: return: 3
> 12/07/03 11:15:39 TRACE shell.Shell:
> <stdout>
> Starting Hadoop httpfs: ..done
> ......
> service hadoop-httpfs restart
> __EOT__
> 12/07/03 11:15:48 TRACE shell.Shell: return: 3
> 12/07/03 11:15:48 TRACE shell.Shell:
> <stdout>
> Stopping Hadoop httpfs: ..done
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira