whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (WHIRR-207) Handle curl timeouts better
Date Mon, 07 Feb 2011 16:53:57 GMT

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

Andrei Savu edited comment on WHIRR-207 at 2/7/11 4:52 PM:
-----------------------------------------------------------

We are seeing this failure because we do at the beginning of script {{set -e}} and we don't
handle the curl exit code (18). The loop and the retry are never executed in this failure
scenario.  

      was (Author: savu.andrei):
    We are seeing this failure because we do at the beginning of script {{set -e}} and we
don't handle the curl exit code (18). The loop and the retry is never executed in this failure
scenario.  
  
> Handle curl timeouts better
> ---------------------------
>
>                 Key: WHIRR-207
>                 URL: https://issues.apache.org/jira/browse/WHIRR-207
>             Project: Whirr
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>            Reporter: Lars George
>             Fix For: 0.4.0
>
>
> I have had that happen before and now again. We need to handle this better:
> {code}
> + for i in '`seq 1 3`'
> + curl --retry 3 --silent --show-error --fail -O http://archive.apache.org/dist/hbase/hbase-0.20.6/hbase-0.20.6.tar.gz
> curl: (18) transfer closed with 12646997 bytes remaining to read
> {code}

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message