brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BROOKLYN-113) Curl command occasionally hanging when deploying to vcloud-director
Date Mon, 12 Jan 2015 10:48:35 GMT

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

Aled Sage edited comment on BROOKLYN-113 at 1/12/15 10:48 AM:
--------------------------------------------------------------

We hit something like this again when installing JBoss 7, but after 2 hours the download failed
from `download.jboss.org`. It went on to the next possible URL (i.e. from `downloads.cloudsoftcorp.com`)
and that worked in a much more reasonable 34 seconds.

Running with `curl --trace-ascii`, we see:

{noformat}
$ ls -ltr
total 326248
drwxr-xr-x. 10 amp wheel      4096 Mar 10  2012 jboss-as-7.1.1.Final
-rw-r--r--.  1 amp wheel       118 Jan  9 12:21 curl-trace-ep9ipB9q.txt
-rw-r--r--.  1 amp wheel  53452205 Jan  9 14:33 curl-trace-KIvFyFNM.txt
-rw-r--r--.  1 amp wheel 132775715 Jan  9 14:33 jboss-as-7.1.1.Final.tar.gz
-rw-r--r--.  1 amp wheel 147829995 Jan  9 14:33 curl-trace-o7Tga0gd.txt
-rw-r--r--.  1 amp wheel        29 Jan  9 14:33 BROOKLYN
{noformat}

The file for `download.jboss.org` shows:

{noformat}
$ grep -i info curl-trace-KIvFyFNM.txt 
== Info: About to connect() to download.jboss.org port 80 (#0)
== Info:   Trying 209.8.115.118... == Info: connected
== Info: Connected to download.jboss.org (209.8.115.118) port 80 (#0)
== Info: Closing connection #0
== Info: Failure when receiving data from the peer
{noformat}

And the stderr shows:

{noformat}
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  1  126M    1 1304k    0     0  4540k      0  0:00:28 --:--:--  0:00:28 10.0M
  8  126M    8 10.6M    0     0  8457k      0  0:00:15  0:00:01  0:00:14 9652k
 18  126M   18 23.7M    0     0  10.3M      0  0:00:12  0:00:02  0:00:10 11.1M
 21  126M   21 26.7M    0     0  7935k      0  0:00:16  0:00:03  0:00:13 8321k
 22  126M   22 28.8M    0     0  6899k      0  0:00:18  0:00:04  0:00:14 7167k
 24  126M   24 31.1M    0     0  6018k      0  0:00:21  0:00:05  0:00:16 6103k
 26  126M   26 33.7M    0     0  5383k      0  0:00:24  0:00:06  0:00:18 4614k
 28  126M   28 35.7M    0     0  4999k      0  0:00:25  0:00:07  0:00:18 2445k
 30  126M   30 38.2M    0     0  4621k      0  0:00:28  0:00:08  0:00:20 2351k
 32  126M   32 40.8M    0     0  4387k      0  0:00:29  0:00:09  0:00:20 2336k
 33  126M   33 42.8M    0     0  4262k      0  0:00:30  0:00:10  0:00:20 2394k
 35  126M   35 44.9M    0     0  4003k      0  0:00:32  0:00:11  0:00:21 2254k
 36  126M   36 45.8M    0     0  3672k      0  0:00:35  0:00:12  0:00:23 1892k
 36  126M   36 45.8M    0     0  3406k      0  0:00:38  0:00:13  0:00:25 1466k
 36  126M   36 45.8M    0     0  3175k      0  0:00:40  0:00:14  0:00:26  969k
 36  126M   36 45.8M    0     0  2974k      0  0:00:43  0:00:15  0:00:28  563k
 36  126M   36 45.8M    0     0  2796k      0  0:00:46  0:00:16  0:00:30  177k
 36  126M   36 45.8M    0     0  2639k      0  0:00:49  0:00:17  0:00:32     0

<snip: lots of current speed 0>

 36  126M   36 45.8M    0     0   6099      0  6:02:50  2:11:22  3:51:28     0
 36  126M   36 45.8M    0     0   6099      0  6:02:50  2:11:23  3:51:27     0
 36  126M   36 45.8M    0     0   6098      0  6:02:53  2:11:24  3:51:29     0
 36  126M   36 45.8M    0     0   6097      0  6:02:57  2:11:25  3:51:32     0
 36  126M   36 45.8M    0     0   6096      0  6:03:00  2:11:26  3:51:34     0
 36  126M   36 45.8M    0     0   6096      0  6:03:00  2:11:26  3:51:34     0
curl: (56) Failure when receiving data from the peer
{noformat}



was (Author: aled.sage):
We hit something like this again when installing JBoss 7, but after 2 hours the download failed
from `download.jboss.org`. It went on to the next possible URL (i.e. from `downloads.cloudsoftcorp.com`)
and that worked in a much more reasonable 34 seconds.

Running with `curl --trace-ascii`, we see:

{noformat}
$ ls -ltr
total 326248
drwxr-xr-x. 10 amp wheel      4096 Mar 10  2012 jboss-as-7.1.1.Final
-rw-r--r--.  1 amp wheel       118 Jan  9 12:21 curl-trace-ep9ipB9q.txt
-rw-r--r--.  1 amp wheel  53452205 Jan  9 14:33 curl-trace-KIvFyFNM.txt
-rw-r--r--.  1 amp wheel 132775715 Jan  9 14:33 jboss-as-7.1.1.Final.tar.gz
-rw-r--r--.  1 amp wheel 147829995 Jan  9 14:33 curl-trace-o7Tga0gd.txt
-rw-r--r--.  1 amp wheel        29 Jan  9 14:33 BROOKLYN
{noformat}

The file for `download.jboss.org` shows:

{noformat}
$ grep -i info curl-trace-KIvFyFNM.txt 
== Info: About to connect() to download.jboss.org port 80 (#0)
== Info:   Trying 209.8.115.118... == Info: connected
== Info: Connected to download.jboss.org (209.8.115.118) port 80 (#0)
== Info: Closing connection #0
== Info: Failure when receiving data from the peer
{noformat}

And the stderr shows:

{noformat}
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  1  126M    1 1304k    0     0  4540k      0  0:00:28 --:--:--  0:00:28 10.0M
  8  126M    8 10.6M    0     0  8457k      0  0:00:15  0:00:01  0:00:14 9652k
 18  126M   18 23.7M    0     0  10.3M      0  0:00:12  0:00:02  0:00:10 11.1M
 21  126M   21 26.7M    0     0  7935k      0  0:00:16  0:00:03  0:00:13 8321k
 22  126M   22 28.8M    0     0  6899k      0  0:00:18  0:00:04  0:00:14 7167k
 24  126M   24 31.1M    0     0  6018k      0  0:00:21  0:00:05  0:00:16 6103k
 26  126M   26 33.7M    0     0  5383k      0  0:00:24  0:00:06  0:00:18 4614k
 28  126M   28 35.7M    0     0  4999k      0  0:00:25  0:00:07  0:00:18 2445k
 30  126M   30 38.2M    0     0  4621k      0  0:00:28  0:00:08  0:00:20 2351k
 32  126M   32 40.8M    0     0  4387k      0  0:00:29  0:00:09  0:00:20 2336k
 33  126M   33 42.8M    0     0  4262k      0  0:00:30  0:00:10  0:00:20 2394k
 35  126M   35 44.9M    0     0  4003k      0  0:00:32  0:00:11  0:00:21 2254k
 36  126M   36 45.8M    0     0  3672k      0  0:00:35  0:00:12  0:00:23 1892k
 36  126M   36 45.8M    0     0  3406k      0  0:00:38  0:00:13  0:00:25 1466k
 36  126M   36 45.8M    0     0  3175k      0  0:00:40  0:00:14  0:00:26  969k
 36  126M   36 45.8M    0     0  2974k      0  0:00:43  0:00:15  0:00:28  563k
 36  126M   36 45.8M    0     0  2796k      0  0:00:46  0:00:16  0:00:30  177k
 36  126M   36 45.8M    0     0  2639k      0  0:00:49  0:00:17  0:00:32     0

<snip: lots of current speed 0>

36  126M   36 45.8M    0     0   6099      0  6:02:50  2:11:22  3:51:28     0
 36  126M   36 45.8M    0     0   6099      0  6:02:50  2:11:23  3:51:27     0
 36  126M   36 45.8M    0     0   6098      0  6:02:53  2:11:24  3:51:29     0
 36  126M   36 45.8M    0     0   6097      0  6:02:57  2:11:25  3:51:32     0
 36  126M   36 45.8M    0     0   6096      0  6:03:00  2:11:26  3:51:34     0
 36  126M   36 45.8M    0     0   6096      0  6:03:00  2:11:26  3:51:34     0
curl: (56) Failure when receiving data from the peer
{noformat}


> Curl command occasionally hanging when deploying to vcloud-director
> -------------------------------------------------------------------
>
>                 Key: BROOKLYN-113
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-113
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Martin Harris
>
> Occasionally when deploying to a VM via BrooklynCentral's advanced-networking vcloud-director,
the curl command will hang on the VM. `ps aux | grep [c]url` shows that the curl command is
still running, but the file is no longer being downloaded



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message