Meteor: Geographical CDN issue causing meteor & package install problem
To China (Mainland) Users:
You should just try VPN/Shadowsocks or other things to get access to _the internet_, and set
HTTP_PROXY,HTTP_PROXYto use your bridge to _the internet_.
您最好尝试使用各类工具以访问完整的互联网，并设置HTTP_PROXY和HTTP_PROXY来让 Meteor 使用您的工具。
Original Issue Content
div@dk:~$ curl https://install.meteor.com/ | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 4772 0 --:--:-- 0:00:01 --:--:-- 4774
Downloading Meteor distribution
### 4.2%
curl: (18) transfer closed with 168048742 bytes remaining to read
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Installation failed.
dksharp
All 297 comments
@dksharp Seems like a connectivity problem.
Can you see what happens if you run this command?
Mac OS X
curl -O --progress-bar "https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz"
Linux
curl -O --progress-bar "https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.linux.x86_64.tar.gz"
If the same thing happens, will you provide the output of: host static-meteor.netdna-ssl.com
And maybe even a traceroute static-meteor.netdna-ssl.com
abernix
on 3 May 2016
@abernix
Same thing happened.
output of: host static-meteor.netdna-ssl.com-
static-meteor.netdna-ssl.com has address 198.232.125.32;; connection timed out; no servers could be reached
traceroute to static-meteor.netdna-ssl.com (198.232.125.32), 30 hops max, 60 byte packets
1 tata-photon-max.wifi (192.168.1.1) 1.551 ms 1.790 ms 2.140 ms
2 172.29.145.129 (172.29.145.129) 52.426 ms 60.799 ms 67.414 ms
3 172.29.145.140 (172.29.145.140) 67.639 ms 75.511 ms 75.629 ms
4 172.29.145.169 (172.29.145.169) 82.270 ms 82.486 ms 90.231 ms
5 115.113.247.17.static-delhi.vsnl.net.in (115.113.247.17) 89.510 ms 100.620 ms 100.846 ms
6 172.29.250.33 (172.29.250.33) 122.365 ms 117.457 ms 125.681 ms
7 ix-ae-0-100.tcore1.MLV-Mumbai.as6453.net (180.87.38.5) 132.406 ms 83.176 ms 90.256 ms
8 if-ae-9-5.tcore1.WYN-Marseille.as6453.net (80.231.217.17) 205.243 ms if-ae-9-6.tcore1.WYN-Marseille.as6453.net (80.231.217.77) 205.472 ms 212.367 ms
9 if-ae-8-1600.tcore1.PYE-Paris.as6453.net (80.231.217.6) 213.368 ms 213.596 ms 214.214 ms
10 if-ae-2-2.tcore1.PVU-Paris.as6453.net (80.231.154.17) 213.091 ms 212.853 ms 215.080 ms
11 ae12.mpr1.cdg11.us.zip.zayo.com (64.125.14.49) 218.599 ms 213.933 ms 213.805 ms
12 ae4.mpr2.cdg12.fr.zip.zayo.com (64.125.22.166) 243.455 ms 235.928 ms 243.434 ms
13 netdna-gw.cdg.ip4.above.net (94.31.25.206) 177.279 ms 180.537 ms 177.367 ms
14 32-125-232-198.static.unitasglobal.net (198.232.125.32) 190.672 ms 183.886 ms 191.000 ms
PS: I have seen one recent same question, maybe of yesterday, on stackoverflow. same problem.
dksharp
on 3 May 2016
I am able to do all other work just fine. installing other things and all. Connection is fine. Only installing meteor is giving me this error.
dksharp
on 3 May 2016
@dksharp There were no additional error messages from the curl command? #6944 might be related, though I'm not having any problems at all and I'm using the same 198.232.125.32 as you.
But you're right, I've seen other recent similarities #6723 (comment).
abernix
on 3 May 2016
@abernix I have been trying this since Sunday. can't find any solution.
dksharp
on 3 May 2016
Ok, new command, old CDN:
Mac OS X
curl -O --progress-bar "https://d3sqy0vbqsdhku.cloudfront.net/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz"
Linux
curl -O --progress-bar "https://d3sqy0vbqsdhku.cloudfront.net/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.linux.x86_64.tar.gz"
@dksharp, Can you see if that works? (It's a 167MB file, just FYI, so it needs a long, reliable download.)
abernix
on 3 May 2016
@abernix Yeah. It works. Why that standard command is not working :(
dksharp
on 3 May 2016
It's a network problem. I can't say for sure why, but it seems to be a problem with the new CDN. It's only happening to some people. Thank you very much for helping to figure it out.
Could you try one more time with this (slightly different) command: _(which enables cURL retries and file-resume)_
Mac OS X
curl -O -C - --retry 4 --progress-bar "https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz"
Linux
curl -O -C - --retry 4 --progress-bar "https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.linux.x86_64.tar.gz"
Thanks again, @dksharp
abernix
on 3 May 2016
Its working. I think new CDN is closing connection abruptly or something like that.
Thank you for helping me out @abernix .
dksharp
on 3 May 2016
Ok, that last command works though? If it does, then we can look into changing the install script to use those extra flags. Please report back if it works with the --retry or the -C - (or if it needs both!) :smile:
abernix
on 3 May 2016
Btw, while this is not the recommended installation method, you can use that bootstrap tarball by:
tar xfz meteor-bootstrap-os.YOUR_OS_ARCH.tar.gz -C $HOME
Which will install it into your home directory in the .meteor directory (the correct place).
You can then:
- Add "
$HOME/.meteor" to your path, - (_optional_) Install the
meteorlauncher in/usr/local/bin/using this command (requires root):
sudo cp $HOME/.meteor/$(dirname $(readlink "$HOME/.meteor/meteor"))/scripts/admin/launch-meteor /usr/local/bin/meteor
abernix
on 3 May 2016
The last command worked. I did it using both flags. Will report with using individually.
dksharp
on 3 May 2016
Thanks, we're looking into this.
glasser
on 3 May 2016
Folks who are having problems (eg @dksharp): Where in the world are you located? This may be a geographically specific issue with our new CDN.
glasser
on 3 May 2016
I saw India (2x) and Lebanon.
abernix
on 3 May 2016
I've replicated the issue with a VPN to India. We'll be filing a support ticket with the CDN when we have more details.
In the mean time, we've reverted to the old CDN for the installer.
The meteor package updater (warehouse.meteor.com) is still using the new CDN. We have not yet seen issues with package downloads, but if anyone spots a download issue with packages (as opposed to installers) please let us know!
Thanks again, @abernix, for your help here. Much appreciated.
n1mmy
on 3 May 2016
Yes, guys I'm facing this issue in India from past 3+ days. Though, I did installed meteor manually but it was painful as compared to our recommended process. Also, becuase of this...now everytime I had to use sudo with meteor command.
allpratik
on 3 May 2016
@allpratik When did you see this? We reverted an hour or two ago, so if you're still seeing problems then there's a surprise.
glasser
on 3 May 2016
Or do you mean you're seeing the issue downloading packages?
glasser
on 3 May 2016
@glasser No I didn't tried packages. Also, I tested it before 10 hrs. So, let me check current situation and also check packages as well.
allpratik
on 3 May 2016
I tested downloading multiple files over the VPN to India. Curious results. Here's what I've found so far:
warehouse.meteor.comdownloads via meteor cli: GOOD. (tested by runningmeteor --release 1.3.2.2 --helpand downloading a new tool, for 3 different releases)curl -v -o /dev/null https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.1/meteor-bootstrap-os.linux.x86_64.tar.gz: BAD (fails consistently)curl -v -o /dev/null https://warehouse.meteor.com/builds/EXSxwGqYjjJKh3WMJ/1459125225532/3AAHkWZLi8/babel-compiler-6.5.2-os+web.browser+web.cordova.tgz(small file): GOODcurl -v -o /dev/null https://warehouse.meteor.com/builds/EXSxwGqYjjJKh3WMJ/1459133033542/egJ3SEgtYM/meteor-tool-1.3.0_3-os.linux.x86_64+web.browser+web.cordova.tgz(big file): BAD (fails consistently)
So it seems the error only occurs with big files, via curl not the meteor tool, from some places (only tested India so far).
n1mmy
on 4 May 2016
If anyone else who saw this issue could please post their IP address and the output of traceroute static-meteor.netdna-ssl.com that would be very useful for us to debug.
n1mmy
on 4 May 2016
And if you are not comfortable posting your IP publicly, feel free to email me privately at [email protected].
n1mmy
on 4 May 2016
@shaileshtheroyal You also had problems installing/downloading, I believe. Could you provide your information as @n1mmy posted above?
@n1mmy Is it possible the Windows installer is/was accessing the new CDN already as well? If so, maybe reach out to the two people in #6955 for their traceroute...err...tracert.
abernix
on 4 May 2016
@n1mmy I've been having the same problem in Belgium last couple of days. I can confirm it's due to bad internet connection but I don't think it's because of curl. When trying wget, the same problem occurred.
Network at my student house is pretty bad. Downloading over 4G did the trick for me.
saltslag
on 4 May 2016
Sounds like my problem...
MacOS standart installation doesn't go over 27%
traceroute returns a stack of *
gothicn
on 4 May 2016
@abernix Yup, windows is the same CDN as the installer. Updated the windows ticket too. Thanks.
@gothicn @titmastercrunch Not sure if you folks have the same issue, but I'd really appreciate it if you could try something for me. Can you please run each of these commands:
curl https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.linux.x86_64.tar.gz -o /dev/null
curl https://d3sqy0vbqsdhku.cloudfront.net/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz -o /dev/null
2 or 3 times each and report back the results?
n1mmy
on 5 May 2016
Everything fine. No errors, download finishes 100% successfully. MacOS el capitan
It seems i got another type problem... It always stops at 27-30% with curl |sh
And also freezes at 27/60% of manual installation pre-build download step, finishing with SSL error
Should i create a separate issue? I didn't find any solutions.
Few men with(prolly) the same issue had it resolved by a miracle.
gothicn
on 6 May 2016
Thanks @gothicn. Yeah, sounds like a separate issue.
n1mmy
on 7 May 2016
After talking with MaxCDN support we think this was a transient issue. I'm going to try cutting back to the new CDN in a few minutes. I'll try and keep a sharp eye out for reports of installs failing, and @abernix I'd appreciate your continued help too =)
n1mmy
on 10 May 2016
Having not seen any new issues on this since the cutover, I'm gonna call this closed for now. Please comment if you notice any issues downloading the installer.
n1mmy
on 12 May 2016
If you're still having this problem please help debug!
Please copy-and-paste the contents of the following four things into this issue
- http://debug.netdna-cdn.com
- http://checkip.amazonaws.com
- The output of
traceroute static-meteor.netdna-ssl.com(ortracerton Windows) - Your location/country/geographic area
It would be greatly appreciated!
abernix
on 13 May 2016
the contents of http://debug.netdna-cdn.com below：
You are hitting the MaxCDN Frankfurt Datacenter
the contents of http://checkip.amazonaws.com below：
183.16.7.241
My location is Shenzhen , China
glad i can help.
gitlinming
on 13 May 2016
Same issue...Meteor installation fails..
Contents of http://debug.netdna-cdn.com:
You are hitting the MaxCDN London Datacenter
Contents of http://checkip.amazonaws.com/:
117.207.161.224
My location is Kerala, India.
Gadheyan
on 16 May 2016
Thanks, folks! I'll be in touch with MaxCDN support with the new data and we'll see what we can find.
n1mmy
on 16 May 2016
Same issue as above. Using
$ curl https://install.meteor.com/ | sh I get
`$ curl https://install.meteor.com/ | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 1641 0 --:--:-- 0:00:04 --:--:-- 1641
Downloading Meteor distribution
########################## 45.4%
curl: (18) transfer closed with 90806516 bytes remaining to read
.meteor/packages/meteor-tool/.1.3.2_4.lbyo5v++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/babel-preset-meteor/node_modules/babel-register/node_modules/core-js/client/library.min.js: (Empty error message)
tar: Error exit delayed from previous errors.
Installation failed.
Contents of http://debug.netdna-cdn.com:
You are hitting the MaxCDN London Datacenter
Contents of http://checkip.amazonaws.com/:
41.212.101.149`
Location: Kenya
AC6567
on 16 May 2016
@n1mmy @abernix
still no luck for me in installing...
here is the output of traceroute static-meteor.netdna-ssl.com for me (in Kenya).
traceroute static-meteor.netdna-ssl.com
traceroute to static-meteor.netdna-ssl.com (198.232.125.32), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.201 ms 0.837 ms 0.624 ms
2 * * *
3 41.212.1.181 (41.212.1.181) 139.996 ms 274.786 ms 131.019 ms
4 41.212.1.113 (41.212.1.113) 129.572 ms 129.415 ms 95.898 ms
5 * * *
6 10.138.104.1 (10.138.104.1) 10.409 ms 9.387 ms 9.220 ms
7 * 10.138.104.1 (10.138.104.1) 8.298 ms 55.106 ms
8 178.2.212.41.in-addr.arpa (41.212.2.178) 75.987 ms 49.
```203 ms 38.981 ms
9 129.2.212.41.in-addr.arpa (41.212.2.129) 177.305 ms 179.278 ms *
10 ix-xe-1-0-1-0.thar1.ly9-london.as6453.net (195.219.92.77) 151.802 ms 156.411 ms 153.106 ms
11 if-ae-25-2.tcore1.l78-london.as6453.net (80.231.130.141) 156.012 ms 149.854 ms 149.700 ms
12 if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 157.401 ms 155.453 ms 154.006 ms
13 80.231.62.2 (80.231.62.2) 150.102 ms 144.916 ms 223.487 ms
14 ae4.mpr3.lhr3.uk.zip.zayo.com (64.125.21.1) 197.375 ms 195.844 ms 193.403 ms
15 ae2.mpr1.lhr9.uk.zip.zayo.com (64.125.29.62) 210.131 ms 152.673 ms 153.107 ms
16 netdna-gw.lhr.ip4.above.net (94.31.25.230) 170.416 ms 171.811 ms 187.158 ms
17 32-125-232-198.static.unitasglobal.net (198.232.125.32) 152.638 ms 160.063 ms *
AC6567
on 16 May 2016
@BlackGuyCoding Sorry about the problems. Hopefully the CDN will figure out a solution soon. Meanwhile, see my instructions to download manually in this comment and then my instructions for installing it in this comment. Thanks for providing your traceroute and CDN information – very helpful.
abernix
on 16 May 2016
@abernix
I am getting the following error message still.. (am I downloading manually correctly?)
curl -O -C - --retry 4 --progress-bar "https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz"
########################### 38.2%
curl: (18) transfer closed with 102701761 bytes remaining to read
@abernix actually I did get the tar to download. file name is meteor-bootstrap-os.osx.x86_64.tar.gz. Its in my download folder, tried running tar xfz meteor-bootstrap-os.osx.x86_64.tar.gz and I get
tar: (Empty error message) tar: Error exit delayed from previous errors.
and I tried unzipping and running just tar xfz meteor-bootstrap-os.osx.x86_64.tar each time I get this error tar: Truncated tar archive tar: Error exit delayed from previous errors.
AC6567
on 16 May 2016
Hey all. I've been chatting with CDN support. We're working on getting more edge nodes turned on in Asia.
In the mean time, what they've said what would be most helpful is traceroutes from affected users to static-meteor.netdna-ssl.com, along with the output from http://checkip.amazonaws.com/ taken at the same time as the traceroute. Can any users who have been affected by this please try to gather this information. Thanks!
n1mmy
on 17 May 2016
@n1mmy
This is the output for traceroute:
$ traceroute static-meteor.netdna-ssl.com traceroute to static-meteor.netdna-ssl.com (198.232.125.32), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 6.380 ms 6.361 ms 6.352 ms 2 117.207.160.1 (117.207.160.1) 28.664 ms 33.541 ms 38.232 ms 3 218.248.173.122 (218.248.173.122) 44.599 ms 49.489 ms 54.691 ms 4 218.248.235.162 (218.248.235.162) 73.660 ms * * 5 125.17.180.233 (125.17.180.233) 90.629 ms 96.494 ms 98.968 ms 6 182.79.222.197 (182.79.222.197) 353.973 ms 296.740 ms 300.373 ms 7 te0-0-1-4.rcr21.b015591-1.lon01.atlas.cogentco.com (149.14.81.201) 304.842 ms te0-0-0-7.rcr21.b015591-1.lon01.atlas.cogentco.com (149.14.81.193) 296.997 ms 298.879 ms 8 netdna-gw.lhr.ip4.cogentco.com (149.11.30.58) 306.728 ms 312.886 ms 316.832 ms 32-125-232-198.static.unitasglobal.net (198.232.125.32) 321.739 ms 323.184 ms 332.801 ms
Output of http://checkip.amazonaws.com/ is:
117.207.162.225
Gadheyan
on 17 May 2016
@n1mmy any chance someone could tell me where I went wrong on the manually download @abernix suggested above? I have a development project pending. Thanks
AC6567
on 17 May 2016
@BlackGuyCoding That curl command it meant to run multiple times until it fully downloads the file – it _should_ automatically resume where it left off (that's what the -C - does. You may have to run it several times until it finishes without error. Unfortunately, if the connection is bad enough (which it sounds like it was in your case), the file might be corrupted.
Your best bet would be to try running the first command again, to see if it picks up where it left off, but if that doesn't work, delete the file and try again because the second command will fail if the file is corrupted.
You can check the file to make sure it's complete by ensuring that when you type md5 meteor-bootstrap-os.osx.x86_64.tar.gz that the result matches the correct value below:
$ md5 meteor-bootstrap*.tar.gz
MD5 (meteor-bootstrap-os.osx.x86_64.tar.gz) = 58f8a45174596ebcffc7528fd6321cb8 # OS X
MD5 (meteor-bootstrap-os.linux.x86_64.tar.gz) = 6505d1ae1272eb31758c56e403a5aeef # Linux
@abernix I'll give that a try and report back.
AC6567
on 17 May 2016
@abernix also to make sure is the correct unzip command tar **xfz** meteor... I've never used xfz before only xvf.
AC6567
on 17 May 2016
@BlackGuyCoding It doesn't matter on OS X, but on non-OSX systems you have to use z to clarify that it's tar AND gz. (OS X figures it out automatically).
You can also add 'v' if you want to see it doing something while it works.
abernix
on 17 May 2016
@abernix ok it worked! Thanks for all of your help. @n1mmy
AC6567
on 17 May 2016
You are hitting the MaxCDN London Datacenter
traceroute to static-meteor.netdna-ssl.com (198.232.125.32), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 0.824 ms 0.612 ms 0.564 ms
2 125.121.32.1 (125.121.32.1) 10.096 ms 4.391 ms 9.234 ms
3 61.164.22.98 (61.164.22.98) 31.247 ms 3.242 ms 3.190 ms
4 61.164.22.137 (61.164.22.137) 5.232 ms
61.164.22.141 (61.164.22.141) 4.267 ms
61.164.22.157 (61.164.22.157) 6.704 ms
5 202.97.55.21 (202.97.55.21) 8.909 ms
202.97.68.141 (202.97.68.141) 10.058 ms 9.948 ms
6 202.97.33.78 (202.97.33.78) 58.699 ms *
202.97.50.238 (202.97.50.238) 7.456 ms
7 * * 202.97.35.78 (202.97.35.78) 9.468 ms
8 202.97.52.194 (202.97.52.194) 294.409 ms 296.201 ms
202.97.52.46 (202.97.52.46) 273.082 ms
9 ge-3-2-4.lon21.ip4.tinet.net (213.200.79.237) 235.514 ms * 184.175 ms
10 netdna-gw.lhr.ip4.gtt.net (46.33.89.78) 280.907 ms 272.338 ms 272.921 ms
11 32-125-232-198.static.unitasglobal.net (198.232.125.32) 304.979 ms * 296.975 ms
Location: China,Hangzhou
LocIP:125.121.34.160
install not work for me -_-
mdreamfly
on 17 May 2016
http://debug.netdna-cdn.com
You are hitting the MaxCDN Frankfurt Datacenter
http://checkip.amazonaws.com
84.150.27.142
$ traceroute static-meteor.netdna-ssl.com ⬡ 5.10.1
traceroute to static-meteor.netdna-ssl.com (198.232.125.32), 30 hops max, 60 byte packets
1 speedport.ip (192.168.2.1) 3.814 ms 3.700 ms 3.654 ms
2 217.0.116.84 (217.0.116.84) 50.137 ms 54.977 ms 60.849 ms
3 217.0.69.246 (217.0.69.246) 69.005 ms 72.853 ms 80.732 ms
4 f-ed5-i.F.DE.NET.DTAG.DE (217.5.95.18) 88.780 ms 99.700 ms 99.838 ms
5 80.157.204.62 (80.157.204.62) 105.660 ms 111.500 ms 116.676 ms
6 xe-8-3-0.fra27.ip4.gtt.net (89.149.132.42) 122.571 ms xe-3-1-0.fra27.ip4.gtt.net (89.149.132.54) 124.934 ms xe-8-0-0.fra27.ip4.gtt.net (89.149.132.58) 129.799 ms
7 netdna-gw.fra.ip4.gtt.net (46.33.89.130) 142.820 ms 65.447 ms 53.754 ms
8 32-125-232-198.static.unitasglobal.net (198.232.125.32) 59.617 ms 64.525 ms 70.643 ms
Your location/country/geographic area
munich/germany/europe
install closed with:
curl: (18) transfer closed with 49199206 bytes remaining to read
Goyapa
on 17 May 2016
Thanks for the updates everyone, please keep them coming if you are experiencing this issue!
(@Goyapa yours looks particularly weird because latency looks reasonable – you're not far away)
Going to move some comments I made in #7054 over here...
there are changes to the install script itself right now that could be made to improve this –
curlcould download to a local file (instead of piping directly totar, as nice as that might be), which would allow:
- retrying multiple times
- auto-resume
- checking MD5 and retrying
abernix
on 17 May 2016
Here is the output of my last tries...
$ curl https://install.meteor.com/ | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 1329 0 --:--:-- 0:00:05 --:--:-- 1401
Downloading Meteor distribution
.######################################################### 79,5%
curl: (18) transfer closed with 35993702 bytes remaining to read
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Installation failed.
[18:25:46]
> $ curl https://install.meteor.com/ | sh ⬡ 5.10.1
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 7795 0 --:--:-- --:--:-- --:--:-- 7788
Downloading Meteor distribution
############################################################# 85,1%
curl: (18) transfer closed with 26081382 bytes remaining to read
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Installation failed.
[18:40:04]
> $ curl https://install.meteor.com/ | sh ⬡ 5.10.1
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 7064 0 --:--:-- --:--:-- --:--:-- 7063
Downloading Meteor distribution
################################################### 71,9%
curl: (18) transfer closed with 49199206 bytes remaining to read
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Installation failed.
[19:16:04]
> $ curl https://install.meteor.com/ | sh ⬡ 5.10.1
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 8058 0 --:--:-- --:--:-- --:--:-- 8051
Downloading Meteor distribution
######################################################### 79,5%
curl: (18) transfer closed with 35977318 bytes remaining to read
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Installation failed.
would help it
Goyapa
on 17 May 2016
@Goyapa Consider my manual instructions above and instructions for checking md5 checksum too!
Also, if you don't mind running this command 2 or 3 times and seeing if it finishes for you, it would be greatly appreciated.
curl https://d3sqy0vbqsdhku.cloudfront.net/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz -o /dev/null
download finished
$ curl -O -C - --retry 4 --progress-bar "https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.linux.x86_64.tar.gz"
#################################### 59,3%
curl: (18) transfer closed with 71448678 bytes remaining to read
michael@mjm ~ [20:30:06]
$ curl -O -C - --retry 4 --progress-bar "https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.linux.x86_64.tar.gz"
################################################################## 100,0%
this one was for osx but download was much faster
$ curl https://d3sqy0vbqsdhku.cloudfront.net/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz -o /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 158M 100 158M 0 0 175k 0 0:15:22 0:15:22 --:--:-- 174k
boath downloads succesfull
thanks a lot
Goyapa
on 17 May 2016
@Goyapa and after the download what 's next im experiencing the same issue i cant download it from the website on my mac and i tried since this morning...if i manage to download it somehow how should i install it? please
zjjt
on 17 May 2016
AAAAAHHHH hurray...managed to download and installed it normally through the meteor website's link...it is unexpected and miraculous i dont think they fixed it yet so beware...
zjjt
on 17 May 2016
Hey folks. Our CDN provider has just made a couple changes we hope will fix the issue. 1) they activated edge nodes in Hong Kong, Singapore, Tel Aviv and Tokyo, and 2) they have changed which cluster and routes are used for Meteor.
Can anyone who was affected please re-run the tests (curl installer download and see if it fails, which datacenter you are accessing, traceroute, and checkip).
Thanks again to everyone helping debug this. Really appreciate it! @abernix @Goyapa @mdreamfly @Gadheyan @BlackGuyCoding
n1mmy
on 17 May 2016
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 643 0 --:--:-- 0:00:10 --:--:-- 1911
Downloading Meteor distribution
################################################################## 100.0%
Meteor 1.3.2.4 has been installed in your home directory (~/.meteor).
Writing a launcher script to /usr/local/bin/meteor for your convenience.
it work thanks
You are hitting the MaxCDN London Datacenter
Loc Ip : 125.121.34.160
traceroute to static-meteor.netdna-ssl.com (146.88.128.4), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 0.624 ms 0.572 ms 0.608 ms
2 125.121.32.1 (125.121.32.1) 120.355 ms 144.346 ms 4.584 ms
3 61.164.22.98 (61.164.22.98) 3.283 ms 3.489 ms 3.241 ms
4 61.164.22.153 (61.164.22.153) 4.836 ms
220.191.143.161 (220.191.143.161) 4.904 ms
61.164.22.141 (61.164.22.141) 3.832 ms
5 202.97.34.193 (202.97.34.193) 8.347 ms
202.97.55.9 (202.97.55.9) 7.488 ms 7.599 ms
6 202.97.33.162 (202.97.33.162) 55.034 ms * *
7 202.97.91.62 (202.97.91.62) 34.151 ms *
202.97.91.74 (202.97.91.74) 55.961 ms
8 202.97.63.114 (202.97.63.114) 69.766 ms 83.657 ms
202.97.63.118 (202.97.63.118) 86.284 ms
9 202.97.62.134 (202.97.62.134) 76.552 ms 64.754 ms 62.362 ms
10 pacnet-ic-128274-hnk-b2.c.telia.net (213.248.95.66) 114.486 ms 81.879 ms 79.013 ms
11 so-0-0-3-0.cr4.hkg3.10026.telstraglobal.net (202.147.16.225) 70.532 ms 111.199 ms 110.300 ms
12 te0-0-2-0.wr2.hkg0.10026.telstraglobal.net (61.14.157.105) 71.264 ms 112.944 ms 112.865 ms
13 te0-0-4-0.wr1.hkg0.10026.telstraglobal.net (61.14.157.29) 140.358 ms 92.651 ms 92.125 ms
14 te0-0-0-0.wr1.sin0.10026.telstraglobal.net (61.14.157.74) 95.883 ms 131.543 ms 123.897 ms
15 te0-0-4-0.wr2.sin0.10026.telstraglobal.net (61.14.157.38) 130.159 ms 144.747 ms 112.222 ms
16 * ae1-0.gw2.sin0.10026.telstraglobal.net (61.14.157.186) 146.894 ms 146.587 ms
17 sfl-0022.10026.telstraglobal.net (202.147.33.14) 149.871 ms 107.650 ms 108.735 ms
18 ae0.bbr02.pn01.hkg01.networklayer.com (50.97.18.173) 142.170 ms 103.243 ms 100.453 ms
19 ae6.dar02.hkg02.networklayer.com (50.97.19.35) 139.466 ms
ae6.dar01.hkg02.networklayer.com (50.97.19.33) 107.103 ms 143.623 ms
20 po4.fcr01.hkg02.networklayer.com (119.81.138.141) 142.258 ms
po3.fcr01.hkg02.networklayer.com (119.81.138.139) 141.755 ms 163.291 ms
21 * 146.88.128.4 (146.88.128.4) 138.338 ms 101.721 ms
@n1mmy thank you
mdreamfly
on 17 May 2016
Thanks, @mdreamfly . Anyone else able to confirm it's working now?
n1mmy
on 18 May 2016
@n1mmy
It worked...
output for http://checkip.amazonaws.com/:
117.204.112.5
output for http://debug.netdna-cdn.com/:
You are hitting the MaxCDN London Datacenter
output for traceroute is :
$ traceroute static-meteor.netdna-ssl.com traceroute to static-meteor.netdna-ssl.com (146.88.128.4), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 5.008 ms 6.369 ms 6.400 ms 2 117.204.112.1 (117.204.112.1) 27.931 ms 32.788 ms 38.101 ms 3 218.248.173.118 (218.248.173.118) 49.776 ms 49.781 ms 55.568 ms 4 * 218.248.235.162 (218.248.235.162) 77.269 ms 83.107 ms 5 125.17.180.233 (125.17.180.233) 92.731 ms 95.654 ms 100.520 ms 6 125.16.7.66 (125.16.7.66) 101.471 ms 42.765 ms 40.644 ms 7 ae7.bbr01.sr01.che01.networklayer.com (50.97.19.246) 48.990 ms 51.466 ms 58.558 ms 8 ae1.bbr02.eq01.sng02.networklayer.com (50.97.19.249) 101.921 ms 104.124 ms 110.987 ms 9 ae0.bbr02.pn01.hkg01.networklayer.com (50.97.18.173) 187.431 ms 187.853 ms 157.056 ms 10 ae6.dar01.hkg02.networklayer.com (50.97.19.33) 164.424 ms ae6.dar02.hkg02.networklayer.com (50.97.19.35) 164.434 ms ae6.dar01.hkg02.networklayer.com (50.97.19.33) 172.508 ms 11 * po3.fcr01.hkg02.networklayer.com (119.81.138.139) 110.418 ms * 12 146.88.128.4 (146.88.128.4) 114.137 ms 117.248 ms 123.649 ms
@n1mmy,Thank you..
Gadheyan
on 18 May 2016
@laosb Can you see how this looks for you? I'm particularly interested in what your http://debug.netdna-cdn.com is.
abernix
on 18 May 2016
Yes it works from meteor homepage now...
``` [9:37:54]
$ curl https://install.meteor.com/ | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6675 0 6675 0 0 3875 0 --:--:-- 0:00:01 --:--:-- 3874
Removing your existing Meteor installation.
Downloading Meteor distribution################################################################## 100,0%
Meteor 1.3.2.4 has been installed in your home directory (~/.meteor).
http://debug.netdna-cdn.com
You are hitting the MaxCDN Frankfurt Datacenter
http://checkip.amazonaws.com
84.150.27.142
$ traceroute static-meteor.netdna-ssl.com
traceroute to static-meteor.netdna-ssl.com (94.31.29.248), 30 hops max, 60 byte packets
1 speedport.ip (192.168.2.1) 4.556 ms 4.477 ms 4.444 ms
2 217.0.116.84 (217.0.116.84) 50.654 ms 55.046 ms 61.096 ms
3 217.0.69.246 (217.0.69.246) 68.977 ms 73.897 ms 79.041 ms
4 217.239.44.154 (217.239.44.154) 93.178 ms 96.926 ms 101.165 ms
5 80.150.170.214 (80.150.170.214) 105.711 ms 111.841 ms 116.772 ms
6 netdna-gw.fra.ip4.above.net (94.31.25.226) 123.720 ms 121.325 ms 126.209 ms
7 94.31.29.248.IPYX-077437-ZYO.above.net (94.31.29.248) 134.819 ms 53.483 ms 55.405 ms
Your location/country/geographic area
munich/germany/europe
```
Thanks a lot!
Goyapa
on 18 May 2016
All right! Multiple people confirm things are working now. I'm going to close this.
Please let me know here if things aren't resolved for you.
Thanks again everyone for all your help debugging this. A real team effort!
n1mmy
on 18 May 2016
Closing. :smile:
abernix
on 19 May 2016
@abernix You are hitting the MaxCDN San Francisco Datacenter from Ningbo, Zhejiang, China with China Telecom.
laosb
on 19 May 2016
@laosb Yeah, I figured. 😞 Highly inefficient, but without local POPs, almost impossible for a CDN to solve. This is called "tromboning". uCloud or something local would likely be better.
But I'm curious if it's more efficient than the route you were going over previously? (which was likely to Frankfurt, Germany). Can you reliably run this a few times?:
curl https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.2.4/meteor-bootstrap-os.osx.x86_64.tar.gz -o /dev/null
FYI, the MaxCDN people warn that the debug endpoint won't always give the right location for Asia and Australia. Since the extra nodes are an add-on feature, they vary by account, and are not in the debug url's DNS.
"""
However, please note that edge locations in Asia and Australia are not behind anycast DNS like their US and EU counterparts, which means that the debug URL is still going to show US and EU locations for those users. The only way to identify which edge location is serving the content for those users is to take a look at the traceroute. Also, sometimes, the physical proximity of a particular edge location for a particular user might not always provide the best performance, which means that some requests may be routed to other edge locations. In this particular case, the Chinese end user was routed to our Sydney edge location instead of some closer locations (Hong Kong and Singapore).
"""
n1mmy
on 19 May 2016
Having this problem, with updated curl on Linux Mint 17.3
~ $ traceroute static-meteor.netdna-ssl.com
traceroute to static-meteor.netdna-ssl.com (146.88.128.4), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.808 ms 1.792 ms 2.640 ms
2 10.101.0.1 (10.101.0.1) 13.268 ms 13.696 ms 19.302 ms
3 10.100.0.1 (10.100.0.1) 20.480 ms 20.471 ms 20.401 ms
4 203.177.196.237 (203.177.196.237) 134.931 ms 134.932 ms 135.766 ms
5 120.28.10.221 (120.28.10.221) 172.488 ms 173.160 ms 173.147 ms
6 120.28.10.34 (120.28.10.34) 142.072 ms 120.28.9.202 (120.28.9.202) 132.001 ms 120.28.10.34 (120.28.10.34) 130.319 ms
7 * * 120.28.0.26 (120.28.0.26) 106.711 ms
8 120.28.4.210 (120.28.4.210) 156.905 ms 156.868 ms 156.882 ms
9 203.190.230.61 (203.190.230.61) 208.955 ms 209.484 ms *
10 ae0.bbr01.pn01.hkg01.networklayer.com (50.97.18.167) 257.857 ms 257.076 ms *
11 ae5.dar01.hkg02.networklayer.com (50.97.19.29) 252.287 ms ae5.dar02.hkg02.networklayer.com (50.97.19.31) 257.803 ms 169.946 ms
12 po4.fcr01.hkg02.networklayer.com (119.81.138.141) 175.587 ms * po2.fcr01.hkg02.networklayer.com (119.81.138.133) 174.525 ms
13 146.88.128.4 (146.88.128.4) 167.527 ms 164.912 ms 166.741 ms
MaxCDN: You are hitting the MaxCDN San Francisco Datacenter
http://checkip.amazonaws.com/: 203.177.196.238
Location: Philippines
Tried to reinstall Meteor, since I can't update to 1.3.3 beta, and now I'm stuck :(
myknbani
on 22 May 2016
Chinese users can try curl install-cn.ourmeteor.com/1.3.2.4 | sh to install Meteor 1.3.2.4. I'll update this soon after 1.3.3 release so you can do curl install-cn.ourmeteor.com/1.3.3 | sh then.
Note: This China CDN is provided by myself, not by MDG. For now it has no SSL protection, means it's unsafe.
laosb
on 22 May 2016
Hi, I still have this problem, trying to install meteor from Sweden on Ubuntu 16.04 LTS.
Scorpiion
on 22 May 2016
I think this should be reopened.
Even meteor add and meteor update just hangs prematurely and requires "luck and repetition." No such issues with npm install.
myknbani
on 22 May 2016
I'm having this issue as well, I am from the Philippines and is using Ubuntu for Windows on Windows 10 Build 14342.
MaxCDN: You are hitting the MaxCDN Virginia Datacenter
checkip: 112.210.77.130
ghost
on 22 May 2016
Confirming this issue again from India.
I think it is high time to resolve this CDN issue as many users are not able to install meteor. As I take occasional free workshops for new users, Potentially 250+ new users faced this issue and we had to cancel workshop. They got a very bad first impression about this framework.
allpratik
on 22 May 2016
Ya....it's true Pratik....I think it only happens in India as the foreign
users are not getting any issue regarding to installing of meteor as they
say.....my request to meteor team is please make the appropriate correction
in the script or else give another download link
Thanking you
A meteor user
On May 23, 2016 12:10 AM, "Pratik Khandagale" [email protected]
wrote:
Confirming this issue again from India.
I think it is high time to resolve it as many users are not able to
install meteor. As I take occasional free workshops for new users.
Potentially 250+ new users faced this issue. They got a very bad first
impression about this framework.—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/meteor/meteor/issues/6960#issuecomment-220848406
shaileshbagade
on 22 May 2016
@shaileshtheroyal If you need to install on your machine for some urgent work then I recommend you to download installation package manually by visiting https://install.meteor.com. The package URL is mentioned there.
allpratik
on 22 May 2016
i can install manually, since the downloads can resume. is there any workaround for adding or updating atmosphere packages? that is, aside from cloning into the packages directory of your app? thanks.
myknbani
on 23 May 2016
If you want to install in Asia, try the one I mentioned for China users, it may also works good for other Asian countries, but I have no guarantee for that as China has a very different status in connecting to Internet.
laosb
on 23 May 2016
Out of the Issue Triage policies, I would risk reopening this again as many users have problem in installing both Meteor and Atmosphere packages.
laosb
on 23 May 2016
@myknbani In #7054 I exposed an ENV called METEOR_WAREHOUSE_URLBASE to enable the ability to override the default warehouse.meteor.com. You can set up a mirror of it by reverse proxies (and do some caching of course). But I would say you should wait for MDG and MDG should be responsible for this.
laosb
on 23 May 2016
@laosb I tried using curl install-cn.ourmeteor.com/1.3.2.4 | sh last night, it was not working for me. The download will stall at some point.
ghost
on 23 May 2016
Just to be clear, this is not an Asia only issue, I tried today again from Sweden (northern Europe) and still get the same error.
Scorpiion
on 23 May 2016
OK, edited my comment :)
laosb
on 23 May 2016
Downloading from China worked for me in India by using
curl install-us.ourmeteor.com/1.3.2.4 | sh
Thanks @laosb .
@johncrisostomo What problem did you face? Did you download from China ended abruptly? My download was 'dead slow' but it did finished in 2hrs of time.
Tusharsb
on 23 May 2016
I second with @allpratik . I was also trying to introduce meteor to a bunch of engineers in my region of India. Some half a dozen engineers - they have put their meteor experimentation on hold due to this issue of meteor install
Tusharsb
on 23 May 2016
Anyone else here who has trouble installing packages from Atmosphere without "hacks"? Most comments here so far are for the Meteor installer.
EDIT: Found this comment by @n1mmy on package downloads
The meteor package updater (warehouse.meteor.com) is still using the new CDN. We have not yet seen issues with package downloads, but if anyone spots a download issue with packages (as opposed to installers) please let us know!
myknbani
on 23 May 2016
Downloading from a China CDN by the way I offered should be fast in Asia, but might be slow down due to the China's restrictions of Internet. So I think MDG should pay attention to this as Meteor only have Atmosphere for package hosting for now.
Note: This China CDN is provided by myself, not by MDG. For now it has no SSL protection, means it's unsafe.
laosb
on 24 May 2016
Was able to install last night using the China CDN, don't know how long it took though. I left is for dinner and was done by the time I came back. Thank you @laosb , this will do for now.
ghost
on 24 May 2016
I tried the "big file" link by n1mmy, using curl, and even using the browser. https://warehouse.meteor.com/builds/EXSxwGqYjjJKh3WMJ/1459133033542/egJ3SEgtYM/meteor-tool-1.3.0_3-os.linux.x86_64+web.browser+web.cordova.tgz
it actually works when I use my phone as a wireless hotspot, but using our wired internet at home, it cannot make significant progress. The wired internet is supposedly faster. I still cannot be sure if this is an ISP-specific problem though, since the test by n1mmy using curl failed as well.
An added note, my mobile and home networks are by different ISPs.
myknbani
on 24 May 2016
Thanks for the reports! Sorry to hear it isn't quite working for everyone. We're working with CDN support to try to resolve this and also looking at other solutions including using multiple CDNs for different geographic areas.
n1mmy
on 25 May 2016
Same from Russia
178.141.80.26
SPAHI4
on 26 May 2016
Can I get past this frustrating problem by routing my machine through a VPN Server hosted in United States ? Is that a sensible idea - so that meteor installation and atmosphere downloads get routed from USA IP? I am growing impatient
Tusharsb
on 26 May 2016
@n1mmy If you need help with CDN in China, I think I could help you!
@Tusharsb Please be patient! You may try the command I provided before, which downloads the bootstrap from China.
laosb
on 26 May 2016
I have deployed what I hope is a temporary fix. If you've been affected by this issue and can't install, please try now.
n1mmy
on 26 May 2016
@laosb Thanks! Can you email me off-list and we can discuss? nick at meteor dot com.
n1mmy
on 26 May 2016
Hi @n1mmy, I just tried it from Sweden and it worked for me now:
$ curl https://install.meteor.com/ | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6676 0 6676 0 0 3609 0 --:--:-- 0:00:01 --:--:-- 3608
Downloading Meteor distribution
######################################################################## 100,0%
Meteor 1.3.2.4 has been installed in your home directory (~/.meteor).
Let me know if you need me to try the final solution later, just tag my name in a comment and I'll try it again.
Scorpiion
on 26 May 2016
Great, thanks for the report @Scorpiion . Hopefully we'll have a more permanent solutions soon. Sorry everyone for the inconvenience and thanks for your patience!
n1mmy
on 26 May 2016
Sounds good!
Scorpiion
on 26 May 2016
@n1mmy Worked for me in India. Also no problems with packages as well now.
allpratik
on 26 May 2016
I had the same issue here in the Philippines and tried downloading through 2 different ISP's with slightly lower speeds (Approx 250KBps)... but last night I tried it in a house of a friend with 1MBps, first it failed but after another try it was successful.
darkgraven
on 27 May 2016
Great! But China weren't covered in this fix. Dropped you an email, @n1mmy !
laosb
on 27 May 2016
Hi folks. I've made another hopefully more permanent change. Can anyone affected please check again? @allpratik @Scorpiion @Tusharsb @SPAHI4
Thank you!
n1mmy
on 27 May 2016
@n1mmy Thanks Nick for your efforts. After cd'ing into my meteor code directory i typed 'meteor' and it looks hung on downloading 'webapp'. 'meteor' installation was successfully complete on my desktop when I installed it few weeks back (prior to this CDN issue was recorded)
=> Started proxy.
=> Started MongoDB.
=> Meteor 1.3.2.4 is available. Update this project with 'meteor update'.
Downloading [email protected]... [==== ] 18% 1407.3s
The download of 'webapp' takes forever. I tried retrying 2 times
Tusharsb
on 27 May 2016
@n1mmy Thanks for working on this! The meteor install works, I tried it TWICE just to be really sure. :D
But Atmosphere package installs still flaky similar to @Tusharsb.
myknbani
on 27 May 2016
What i do is that i watch both the terminal progress bar and the network activity via Conky. The progress bars just disappear, with the spinner remaining, and a close to zero download speed.
$ meteor add aldeed:collection2
Downloading [email protected]... /
I have to cancel that and issue the command again.
myknbani
on 27 May 2016
Hi @n1mmy, I just completed a new download/install and it worked perfectly!
Scorpiion
on 28 May 2016
Hi @n1mmy , Installation is working fine and packages as well, as of now.
allpratik
on 29 May 2016
Thanks all for the reports! Glad to hear install is now working for people.
It seems there are still some issues with package downloads, I'll be working on moving that too this week.
n1mmy
on 31 May 2016
I think also this my issue #7090 is a problem with CDN.
I made also this pull request to at least throw useful errors when there are CDN issues: #7143
mitar
on 31 May 2016
I'm not sure if this is the same issue, but package installation fails in India Or it is very very slow. I can confirm this thing from Singapore location as well that even meteor installation takes long time as compared to earlier time.
allpratik
on 7 Jun 2016
@allpratik same here in the Philippines, it can't download packages. I think it has gotten worse.
myknbani
on 7 Jun 2016
https://github.com/meteor/meteor/issues/7136#issuecomment-222639965 Found this comment in a dupe, my predicament right now is that the thing doesn't even start.
$ meteor update --release 1.3.3-rc.1
Downloading [email protected]... [ ] 0% 0.0s
@n1mmy Can you please look into this? Or can you share any method where we can integrate these packages efficiently in existing projects?
@myknbani Yes, it doesn't even starts.
allpratik
on 7 Jun 2016
Hi @allpratik I've definitely not forgotten about this! I know package downloads are still affected, and I apologize to affected users. I'm looking into other options but it is quite a bit of traffic, so finding another vendor as generous as our current benefactors is tough.
I also hope @mitar 's patch over at #7143 will less the impact here.
n1mmy
on 9 Jun 2016
What about using http://ipfs.io/ or Bittorrent?
mitar
on 9 Jun 2016
@abernix @n1mmy I am located in Istanbul, Turkey, having a bad day with meteor update --release 1.3.3 getting stuck with downloading [email protected] and here are my output to the commands/urls you wanted to see:
_traceroute static-meteor.netdna-ssl.com_
traceroute to static-meteor.netdna-ssl.com (146.88.128.4), 30 hops max, 60 byte packets
1 172.20.10.1 (172.20.10.1) 5.727 ms 5.721 ms 5.749 ms
2 * * *
3 172.17.154.99 (172.17.154.99) 54.706 ms 55.810 ms 57.082 ms
4 * * *
5 172.17.243.10 (172.17.243.10) 78.342 ms 80.587 ms 81.875 ms
6 172.17.225.2 (172.17.225.2) 70.147 ms 36.655 ms 40.385 ms
7 host-195-33-215-25.reverse.superonline.net (195.33.215.25) 48.729 ms 50.483 ms 50.514 ms
8 * * *
9 * * *
10 ix-ae-10-0.tcore1.IT5-Istanbul.as6453.net (5.23.0.37) 33.845 ms 35.900 ms 36.165 ms
11 if-ae-8-2.tcore1.FNM-Frankfurt.as6453.net (195.219.156.21) 178.312 ms 174.022 ms 183.389 ms
12 if-ae-6-2.tcore1.AV2-Amsterdam.as6453.net (195.219.194.149) 191.640 ms if-ae-6-4.tcore1.AV2-Amsterdam.as6453.net (195.219.156.62) 191.495 ms if-ae-6-3.tcore1.AV2-Amsterdam.as6453.net (195.219.194.77) 169.759 ms
13 if-ae-2-2.tcore2.AV2-Amsterdam.as6453.net (195.219.194.6) 181.806 ms 169.793 ms 179.834 ms
14 if-ae-8-2.tcore2.L78-London.as6453.net (80.231.131.5) 179.886 ms 159.815 ms 168.066 ms
15 63.243.128.37 (63.243.128.37) 179.680 ms if-ae-4-2.tcore2.N0V-New-York.as6453.net (80.231.131.158) 169.989 ms 160.005 ms
16 if-ae-2-2.tcore1.N0V-New-York.as6453.net (216.6.90.21) 161.492 ms if-ae-9-2.tcore1.N75-New-York.as6453.net (63.243.128.122) 165.472 ms if-ae-2-2.tcore1.N0V-New-York.as6453.net (216.6.90.21) 177.645 ms
17 i-0-0-1-3-peer.ny8a02.pr.telstraglobal.net (134.159.48.37) 336.246 ms 336.828 ms if-ae-7-2.tcore1.NTO-New-York.as6453.net (63.243.128.25) 164.018 ms
18 i-0-0-2-0.ny8a-core01.bi.telstraglobal.net (202.84.252.145) 362.106 ms if-ae-9-2.tcore1.N75-New-York.as6453.net (63.243.128.122) 157.650 ms 157.396 ms
19 i-0-0-1-3-peer.ny8a02.pr.telstraglobal.net (134.159.48.37) 335.251 ms i-0-2-0-1.eqnx-core01.bi.telstraglobal.net (202.84.141.126) 355.781 ms i-0-1-0-7.eqnx-core01.bi.telstraglobal.net (202.84.136.182) 381.679 ms
20 i-0-4-2-0.siko-core03.bx.telstraglobal.net (202.84.136.86) 373.094 ms i-0-4-0-9.ny8a-core01.bi.telstraglobal.net (202.84.252.49) 350.420 ms 346.780 ms
21 i-0-3-0-8.hkhh-core02.bx.telstraglobal.net (202.84.144.117) 358.341 ms 202.84.249.121 (202.84.249.121) 354.550 ms 202.84.144.74 (202.84.144.74) 372.813 ms
22 i-0-6-0-3.hkhh-core02.bx.telstraglobal.net (202.84.136.161) 349.100 ms i-0-5-0-5.siko-core03.bx.telstraglobal.net (202.84.143.166) 370.329 ms i-0-6-0-3.hkhh-core02.bx.telstraglobal.net (202.84.136.161) 409.291 ms
23 i-0-5-2-0.hkhh-core02.bx.telstraglobal.net (202.84.144.74) 437.519 ms i-0-1-0-3.eqnx-core01.bi.telstraglobal.net (202.84.249.34) 245.387 ms i-0-2-0-1.eqnx-core01.bi.telstraglobal.net (202.84.141.126) 248.933 ms
24 i-0-0-0-5.hkth12.bi.telstraglobal.net (202.84.153.41) 436.988 ms unknown.telstraglobal.net (134.159.100.98) 416.855 ms i-0-4-0-20.hkth12.bi.telstraglobal.net (202.84.156.142) 437.014 ms
25 i-0-0-0-7.hkhh-core02.bx.telstraglobal.net (202.84.249.121) 437.411 ms i-0-4-0-20.hkth12.bi.telstraglobal.net (202.84.156.142) 435.197 ms ae6.dar01.hkg02.networklayer.com (50.97.19.33) 404.459 ms
26 unknown.telstraglobal.net (134.159.100.98) 410.756 ms * 403.339 ms
27 unknown.telstraglobal.net (134.159.100.98) 413.167 ms po4.fcr01.hkg02.networklayer.com (119.81.138.141) 431.429 ms 146.88.128.4 (146.88.128.4) 414.407 ms
_http://debug.netdna-cdn.com/_
You are hitting the MaxCDN Frankfurt Datacenter
_http://checkip.amazonaws.com/_
188.58.57.149
_curl https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz -o /dev/null_
performs around 600k average download speed
_curl https://d3sqy0vbqsdhku.cloudfront.net/packages-bootstrap/1.3.3/meteor-bootstrap-os.osx.x86_64.tar.gz -o /dev/null_
performs around 200k average download speed
serkandurusoy
on 14 Jun 2016
@n1mmy, I also try to update my project from 1.3.2.4 to 1.3.3 with meteor update but result is very long wait times downloading meteor-tools on update (and it's not finished at all) I have same issue with this forum post:
https://forums.meteor.com/t/very-long-wait-times-downloading-meteor-tools-on-update/24440
This is traceroute static-meteor.netdna-ssl.com output:
traceroute to static-meteor.netdna-ssl.com (217.22.29.249), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 2.764 ms 2.729 ms 3.735 ms
2 * * *
3 78.39.161.182 (78.39.161.182) 48.524 ms 78.39.161.250 (78.39.161.250) 57.212 ms 78.39.161.182 (78.39.161.182) 64.558 ms
4 78.39.161.249 (78.39.161.249) 71.421 ms 79.314 ms 88.238 ms
5 217.218.189.134 (217.218.189.134) 95.390 ms 103.741 ms 111.387 ms
6 * 10.201.42.34 (10.201.42.34) 106.009 ms *
7 10.201.42.98 (10.201.42.98) 38.156 ms 10.10.36.218 (10.10.36.218) 46.521 ms 10.201.42.98 (10.201.42.98) 53.348 ms
8 so-9-0-0-xcr2.fra.cw.net (62.208.212.145) 168.539 ms 175.946 ms 184.411 ms
9 ae30-xcr1.fix.cw.net (195.2.2.89) 193.007 ms 201.970 ms 209.525 ms
10 be1273.agr21.fra03.atlas.cogentco.com (130.117.15.141) 237.736 ms 217.114 ms 205.775 ms
11 bezeq.demarc.cogentco.com (149.14.89.122) 205.334 ms 162.616 ms 144.692 ms
12 bzq-161-218.pop.bezeqint.net (212.179.161.218) 201.350 ms bzq-219-189-125.dsl.bezeqint.net (62.219.189.125) 199.570 ms bzq (212.179.161.218) 208.519 ms
13 bzq-114-65-2.cust.bezeqint.net (192.114.65.2) 195.938 ms bzq-179-124-189.cust.bezeqint.net (212.179.124.189) 199.814 ms bzq-179-124-250.cust.bezeqint.net (212.179.124.250) 205.079 ms
14 bzq-179-124-158.cust.bezeqint.net (212.179.124.158) 204.539 ms epic.interhost.co.il (82.80.236.100) 204.007 ms bzq-114-65-1.cust.bezeqint.net (192.114.65.1) 209.030 ms
15 bzq (212.179.124.158) 220.454 ms epic.interhost.co.il (82.80.236.100) 197.097 ms bzq (212.179.124.158) 216.097 ms
16 static (217.22.29.249) 197.882 ms 194.168 ms 210.184 ms
http://debug.netdna-cdn.com/
You are hitting the MaxCDN Frankfurt Datacenter
http://checkip.amazonaws.com/
2.190.234.73
How to fix this?
cyclops24
on 15 Jun 2016
This is my output:
1 12 ms 18 ms 9 ms 10.6.0.1
2 15 ms 10 ms 14 ms 66.140.116.91.static.reverse-mundo-r.com [91.116.140.66]
3 15 ms 16 ms 16 ms 212.51.33.222
4 80 ms 123 ms 45 ms 25.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.25]
5 21 ms 21 ms 15 ms te0-0-1-1.rcr11.vgo02.atlas.cogentco.com [149.14.84.5]
6 27 ms 26 ms 31 ms te0-0-0-3.ccr21.bio02.atlas.cogentco.com [130.117.2.173]
7 44 ms 43 ms 43 ms be2475.ccr41.par01.atlas.cogentco.com [130.117.48.182]
8 39 ms 37 ms 38 ms be2097.agr22.par01.atlas.cogentco.com [130.117.49.77]
9 39 ms 107 ms 44 ms be2947.rcr12.b019498-0.par01.atlas.cogentco.com [154.25.7.105]
10 44 ms 109 ms 45 ms netdna-gw.cdg.ip4.cogentco.com [149.6.114.82]
11 41 ms 129 ms 45 ms 94.31.29.248.IPYX-077437-ZYO.above.net [94.31.29.248]
http://debug.netdna-cdn.com/
You are hitting the MaxCDN Paris Datacenter
http://checkip.amazonaws.com/
83.165.79.225
Currently I can't do anything with my projects...
iarapm
on 15 Jun 2016
@n1mmy I also try re install meteor with curl https://install.meteor.com/ | sh command and It's remove 1.2.3.4 and install 1.3.3 successfully but then I can't run my previous project and currently I can't do anything with my projects (I can't run project because it's try to download 1.2.3.4 and again very long wait times downloading meteor-tools and unfinished download) and my computer.
I also try to re install 1.2.3.4 and re back to last stable state with curl https://install.meteor.com/1.3.2.4 | sh but it's return below output and error:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6673 0 6673 0 0 3337 0 --:--:-- 0:00:01 --:--:-- 3336
Downloading Meteor distribution
######################################################### 88.7%
curl: (18) transfer closed with 17550809 bytes remaining to read
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Installation failed.
Please help my working computer totally was destroyed at all. :sob: :cry:
cyclops24
on 15 Jun 2016
Greetings from Malaysia!
I manage to install Meteor 1.3 on my Windows PC by keep on running the installer when it fails to complete the download.
But I can't download the meteor tool for 1.3.3...
My tracert is:
`tracert static-meteor.netdna-ssl.com
Tracing route to static-meteor.netdna-ssl.com [146.88.128.4]
over a maximum of 30 hops:
1 <1 ms <1 ms 4 ms 10.20.53.254
2 4 ms <1 ms <1 ms 10.20.105.253
3 <1 ms <1 ms <1 ms 10.239.10.45
4 2 ms 2 ms 2 ms 10.239.238.241
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * ^C`
http://checkip.amazonaws.com/
58.27.115.84
http://debug.netdna-cdn.com/
You are hitting the MaxCDN Paris Datacenter
And normal curl install for meteor will always stuck in the middle of download...
Can assist on this issue? TQ~
zidane28
on 16 Jun 2016
Hi folks! I'm sorry to hear install _still_ isn't working right. We switched to a new new CDN, and it seemed the problems on the installer were gone (package downloads hanging are somewhat separate, known, and still unsolved issue).
For anyone still having issues installing meteor (as opposed to package downloads), please try running the following commands and report back:
curl https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz -o /dev/null
wget https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz -O /dev/null
(I have a theory that wget does retrying better and will work where curl fails)
And for those of you still having problems with package downloads, I apologize for the inconvenience. If my theory on wget vs curl and retrying turns out to be correct, it at least points in the direction of a potential workaround on package downloads.
And to be clear, we still don't really understand the root cause here... it's weird that the same issue happens on two totally different CDNs.
n1mmy
on 16 Jun 2016
(and actually, come to think of it, I'd appreciate anyone who has had problems with installing over the course of this issue trying the above commands and reporting back)
n1mmy
on 16 Jun 2016
For my side, both command completed successfully with fast download speed...
But I tested with my Ubuntu machine...
zidane28
on 16 Jun 2016
@n1mmy both curl and wget downloads for the links from your last comment performed around 200k average download speed.
I tried this on a 32mb/s broadband connection in Turkey so 200kb/s is super duper low :(
serkandurusoy
on 16 Jun 2016
Thanks @serkandurusoy and @zidane28 for the reports. Keep them coming.
I'm especially interested in anyone who sees failures with curl. You can also try the https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz and see if you get a failure there.
n1mmy
on 16 Jun 2016
@n1mmy with this url, curl yields an average of 170k and wget performs around 45k which seems kind of odd. I hope it helps.
serkandurusoy
on 16 Jun 2016
With
https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz
, I also get download speed around 200k to 600k...
Hope this helps~
zidane28
on 16 Jun 2016
Hello,
French here, whenever trying to update or even run our project, we get stuck on this :
Downloading [email protected]_4... |
I've been struggling with this the whole day, we're supposed to work but we can't do anything... I've uninstalled and reinstalled painfully (it didn't want to uninstall for a while, had to rename a lot of files in .meteor folder because the path was too long so I could delete them...)
Here is what I've tried for debugging :
>tracert static-meteor.netdna-ssl.com
Détermination de l’itinéraire vers static-meteor.netdna-ssl.com [94.31.29.248]
avec un maximum de 30 sauts :
1 1 ms 1 ms 1 ms 192.168.43.1
2 62 ms 58 ms 68 ms 172.31.255.248
3 42 ms 40 ms 34 ms 172.31.255.2
4 41 ms 52 ms 48 ms bzn-9k-4-be1016.intf.routers.proxad.net [194.149.161.17]
5 36 ms 60 ms 50 ms bzn-9k-5-be2100.intf.routers.proxad.net [194.149.162.73]
6 54 ms 58 ms 43 ms bzn-9k-4-be1022.intf.routers.proxad.net [194.149.161.113]
7 52 ms 45 ms 49 ms th2-9k-2-be2001.intf.routers.proxad.net [194.149.161.202]
8 48 ms 58 ms 49 ms ae2.mpr1.cdg11.fr.zip.zayo.com [64.125.14.37]
9 43 ms 46 ms 61 ms ae4.mpr2.cdg12.fr.zip.zayo.com [64.125.22.166]
10 43 ms 61 ms 202 ms netdna-gw.cdg.ip4.above.net [94.31.25.206]
11 54 ms 54 ms 50 ms 94.31.29.248.IPYX-077437-ZYO.above.net [94.31.29.248]
Itinéraire déterminé.
http://checkip.amazonaws.com/
37.162.45.102
http://debug.netdna-cdn.com/
You are hitting the MaxCDN Paris Datacenter
curl https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz -o c:\users\me\document\test
seems to work, ~250k download speed, 10 minutes to complete
the other one won't work, I assume it's for unix...
Tell me if you need anything
Thanks for your work !
TheYojimbo
on 16 Jun 2016
What about just using Bittorrent, IPFS, of WebTorrent to distribute files?
mitar
on 16 Jun 2016
@serkandurusoy Hrm... The bandwidth difference between curl and wget is odd. Can you try them each a few time times and see if it averages out?
@mitar Interesting. Could definitely be a workaround and a big improvement for some users (eg China!). I guess it would have to either a) test the environment for bittorrent or ipfs and fall back to curl / wget, or b) include the necessary binaries built for each platform in the dev bundle. If you're interested in developing a PR for this, I'd suggest coordinating with the Meteor framework team. @zol
n1mmy
on 17 Jun 2016
For IPFS, they are just working on JavaScript implementation now: https://github.com/ipfs/js-ipfs
cc @jbenet who might tell better what it would take to distribute Meteor packages and installer through IPFS.
mitar
on 17 Jun 2016
Thank you all for your help debugging this so far!
For those having package download problems -- that is, if you see problems where meteor gets stuck "Downloading [email protected]... |" (@TheYojimbo @serkandurusoy @zidane28? @cyclops24?): here is a potential workaround to try.
First, lookup the IP address for d3fm2vapipm3k9.cloudfront.net (eg with host d3fm2vapipm3k9.cloudfront.net). For me it is currently 54.230.119.80, but it will be different depending on where in the world you are, and might also change over time.
Next, edit /etc/hosts (eg sudo vi /etc/hosts) and add the line:
<the IP you got eg 54.230.119.80> warehouse.meteor.com
Now try re-running the meteor command that downloads packages. Once you have downloaded the packages, I recommend removing the line from /etc/hosts as it's easy to forget about and come back later and not know why package downloads are broken =)
Note this is for Linux and MacOS. I'm sure there is an equivalent way to do this on Windows, but I don't know it. Maybe someone here can contribute a way to override DNS on Windows?
Please report back how this workaround works for you!
For those of you who have had install problems -- that is, seeing curl: (18) transfer closed errors when trying to install meteor (@dksharp @BlackGuyCoding @Goyapa @Gadheyan @allpratik @Scorpiion) I'd appreciate it if you could run a test for me. See if you can replicate the error with any of:
curl -v -o /dev/null https://static-meteor.netdna-ssl.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz
curl -v -o /dev/null https://d3sqy0vbqsdhku.cloudfront.net/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz
curl -v -o /dev/null https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz
If you consistently get an error on any of those, please try and run:
wget -O /dev/null <the URL that failed>
And see if it succeeds where curl fails.
Thanks!
n1mmy
on 17 Jun 2016
On Windows, hosts file is at %SystemRoot%\System32\drivers\etc\hosts.
mitar
on 17 Jun 2016
Hi @n1mmy ,
I run host d3fm2vapipm3k9.cloudfront.net and this is output:
d3fm2vapipm3k9.cloudfront.net has address 54.240.172.78
Host d3fm2vapipm3k9.cloudfront.net not found: 2(SERVFAIL)
;; connection timed out; no servers could be reached
Then I add 54.240.172.78 warehouse.meteor.com to hosts file with sudo nano /etc/hosts command.
Now when I run meteor update it not wait on Downloading [email protected] and it start download but it's wait 10 minutes in 38% and I stop this.
I'm going to test curl and wget and report result here.
cyclops24
on 17 Jun 2016
@n1mmy his solution not works, In windows with meteor 1.3.3 installed, Modifying the hosts file with params after pinging at warehouse.meteor.com (54.230.82.235). I place for example:
meteor create my-poject
There are faster download for Download [email protected], but after 100%, there is a long time with message in console: Downloading [email protected]... It has 28 min without any answer.
I am attentive to any improvement.
José Luis.
jlmu10
on 17 Jun 2016
@n1mmy @mitar That's great! With WebTorrent or ipfs builtin Meteor, everything will be easier for people in China.
laosb
on 17 Jun 2016
@n1mmy,
This is curl output:
curl https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz -o /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
13 148M 13 19.9M 0 0 60122 0 0:43:17 0:05:47 0:37:30 61034
curl: (18) transfer closed with 135286233 bytes remaining to read
and this is wget output:
wget https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz -O /dev/null
--2016-06-17 08:35:55-- https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz
Resolving meteorinstall-4168.kxcdn.com (meteorinstall-4168.kxcdn.com)... 136.243.68.197
Connecting to meteorinstall-4168.kxcdn.com (meteorinstall-4168.kxcdn.com)|136.243.68.197|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 156191541 (149M) [application/x-tar]
Saving to: ‘/dev/null’
48% [============================================================> ] 75,627,868 54.8KB/s in 21m 17s
2016-06-17 08:57:13 (57.8 KB/s) - Connection closed at byte 75627868. Retrying.
--2016-06-17 08:57:14-- (try: 2) https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz
Connecting to meteorinstall-4168.kxcdn.com (meteorinstall-4168.kxcdn.com)|136.243.68.197|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 156191541 (149M), 80563673 (77M) remaining [application/x-tar]
Saving to: ‘/dev/null’
91% [+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++======================================================> ] 143,063,695 61.1KB/s in 18m 31s
2016-06-17 09:15:47 (59.3 KB/s) - Connection closed at byte 143063695. Retrying.
--2016-06-17 09:15:49-- (try: 3) https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz
Connecting to meteorinstall-4168.kxcdn.com (meteorinstall-4168.kxcdn.com)|136.243.68.197|:443... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 156191541 (149M), 13127846 (13M) remaining [application/x-tar]
Saving to: ‘/dev/null’
100%[++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++==========>] 156,191,541 59.5KB/s in 3m 36s
2016-06-17 09:19:26 (59.3 KB/s) - ‘/dev/null’ saved [156191541/156191541]
@n1mmy my project finished and I want to update from 1.2.3.4 to 1.3.3 and then deploy but now it's 2 days that my project stop at all. Please use same approach as previous version I think all people can use previous version without issue. Pleeeeease fix this as soon as possible or still introduce a temporary solution. :cry:
cyclops24
on 17 Jun 2016
@laosb or others, do you have any new unoffitial CDN for Meteor install like curl install-cn.ourmeteor.com/1.3.2.4 | sh I really needs fix this temporary now.
cyclops24
on 17 Jun 2016
@cyclops24 Perfect! That is just what I was hoping to see.
This confirms my theory that the install problems can be drastically reduced by adding retries (either by using wget or a for loop with curl).
This may also point at a solution for package download problems, we can use a retrying-and-continuing downloader in node.
n1mmy
on 17 Jun 2016
@jlmu10 thats... odd. To confirm, before changing hosts it would only get part way through downloading and stop at some percentage less than 100%. Now, with the hosts change it gets to 100% downloaded but still does not finish installing?
n1mmy
on 17 Jun 2016
This may also point at a solution for package download problems, we can use a retrying-and-continuing downloader in node.
This is why I made #7143. To introduce a timeout. And yes, we could wrap it to retry after a timeout.
mitar
on 17 Jun 2016
@n1mmy thanks man. So we hope to see a fix for this soon? :wink:
cyclops24
on 17 Jun 2016
@mitar Yeah timeout is a big step in the right direction. Unfortunately, I don't think just wrapping a retry loop around the current code will work... it needs to save partial progress and resume where it left off. That way each time you make progress.
n1mmy
on 17 Jun 2016
I would really be surprised if there is no requests module extension which already does that internally?
Maybe: https://www.npmjs.com/package/node-request-retry
Not sure if it continues.
If it does not exist, this could be made as an independent module and then just used in Meteor. So instead of timeout throwing an error, it should reconnect and retry.
mitar
on 17 Jun 2016
Doesn't look like node-request-retry continues, unfortunately. I found https://github.com/tusharmath/Multi-threaded-downloader which looks like it might do what we need.
n1mmy
on 17 Jun 2016
@n1mmy I tried again and both curl & wget perform around 6-700k
serkandurusoy
on 17 Jun 2016
@cyclops24 Sorry, I forgot to paste the update of the mirror. I've updated it so you just need to curl http://install-cn.ourmeteor.com/ | sh. You don't need to add the version number after it as the index is the latest version, for now it's 1.3.3.
laosb
on 17 Jun 2016
@laosb, Thanks for your attention but unfortunatly it's return below error for me:
curl http://install-cn.ourmeteor.com/ | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6650 100 6650 0 0 926 0 0:00:07 0:00:07 --:--:-- 1426
Downloading Meteor distribution
curl: (22) The requested URL returned error: 478 Unknown
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Installation failed.
Hello again,
So, little update on the package downloading problem, windows 10.
Yesterday, I've tried meteor update and let it run for all evening.
Here is what I got :
C:\Users\Me\Documents\sms-base>meteor update
Errors prevented isopacket load:
While loading isopacket `ddp`:
module.js:338:15: Cannot find module './_baseClone'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous>
(C:\Users\Me\AppData\Local\.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\babel-compiler\node_modules\babel-plugin-transform-es2015-modules-commonjs\node_modules\babel-types\node_modules\lodash\clone.js:1:17)
(...)
C:\Users\Me\AppData\Local\.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:165
throw error;
^
Error: isopacket load failed?
at loadIsopacketFromDisk (C:\tools\tool-env\isopackets.js:286:11)
(...)
Then I tried what you suggested, @n1mmy, updating the hosts file with "54.230.186.103 warehouse.meteor.com"
Exactly the same issue.
I've tried meteor run --release 1.3.2.4, I get stuck on "Downloading [email protected]... |" (same if I run release 1.3.3)
When I stop it I get this :
[Error: ENOTEMPTY, directory not empty 'C:\Users\Me\AppData\Local\Temp\mt-1l2wqzj\plugin.compileCoffeescript.os\npm\node_modules\meteor\babel-compiler\node_modules\meteor-babel\node_modules\babel-core\node_modules\babel-traverse\node_modules\invariant\node_modules\loose-envify']
(...)
{ [Error: ENOTEMPTY, directory not empty 'C:\Users\Me\AppData\Local\Temp\mt-1v2ckl8\plugin.compile-ecmascript.os\npm\node_modules\meteor\babel-compiler\node_modules\meteor-babel\node_modules\babel-runtime\node_modules\core-js\es6']
(...)
{ [Error: ENOTEMPTY, directory not empty 'C:\Users\Me\AppData\Local\Temp\mt-1wnuqwm\plugin.compileTemplatesBatch.os\npm\node_modules\meteor\babel-compiler\node_modules\meteor-babel\node_modules\babel-core\node_modules\babel-code-frame\node_modules\chalk\node_modules\has-ansi\node_modules\ansi-regex']
(...)
I don't know if it's important, but I find these paths weird, with node_modules getting repeated every two folders...
Thank you again for your help !
Edit : Or I get this :
{ [Error: EBUSY, resource busy or locked 'C:\Users\Me\AppData\Local\Temp\mt-vbylrq\plugin.compileCoffeescript.os\npm\node_modules\meteor\babel-compiler\node_modules\meteor-babel\node_modules\babel-runtime\node_modules\core-js\fn\object\get-own-property-descriptor.js']
errno: 10 (...)}
Edit 2 : seems like most of it is working for now... didn't update to 1.3.3 yet though. Thanks a lot for your help.
TheYojimbo
on 17 Jun 2016
@n1mmy It seems error fixed man. Did you change something? I remove meteor then go to project folder and run meteor it download 1.2.3.4 then I run meteor update and it's update to 1.3.3 successfully and now all things works well. :+1:
cyclops24
on 17 Jun 2016
@cyclops24 No change. That's part of why this issue is so frustrating to debug... it varies from day to day, depending on the internet weather.
@TheYojimbo Hrm... that's interesting. Those look like file errors, not download errors. Maybe something got corrupt from the download timeouts? Maybe try removing downloaded packages and redownloading? I feel your frustration and I'm sorry for all the trouble. I wish I had a good answer for you, but I don't. Also, FYI the repeated node_modules every other level is the normal NPM layout for nested dependancies.
@serkandurusoy Ok, we'll just write that one off to random variation. Thanks.
I'm still interested in anyone else confirming a difference between curl and wget. We have one confirmation already (thanks @cyclops24 ) and it makes sense, but after so many false "it's fixed now" I'm trying to double check all my assumptions =)
n1mmy
on 17 Jun 2016
@n1mmy I have same problem in other system (my friend laptop).
- I done this and it's not working:
- installed 1.3.3 later
- go to project directory that based on 1.2.1
- run
meteorcommand and it's wait on "Downloading [email protected]" and not finished after 15 minutes. - Then run
curl https://install.meteor.com/ | shand it's remove current meteor and also wait on "Downloading" on 36%. - Then stop and run
curl https://install.meteor.com/ | shagain. It's complete successfully. (Install latest version 1.3.3.1) - Then I go to project folder and run
meteorcommand, it's also download 1.2.1 successfully and all things worked now.
My theory is: maybe Asia data centre of CDN has unstable state and break somewhere in download progress. I suggest switch to wget or other retry approach to prevent this issue.
cyclops24
on 18 Jun 2016
@n1mmy well I don't know why, but it worked all right eventually. I already had tried to uninstall, remove everything and reinstall, but it hadn't changed anything.
Anyway, thanks again for your time and your team's amazing work, and good luck with resolving this issue !
TheYojimbo
on 18 Jun 2016
@cyclops24 you are right, I'm in Singapore and the connection fluctuate quite a bit. I spent 30 minutes waiting for "Downloading [email protected]" and still not done. Ended up had to reinstall Meteor.
Can someone fix the CDN issue if that's the case? Thanks in advance.
DerekChia
on 19 Jun 2016
These 'CDN' issues are most likely caused by flakeyness at the network level recently exacerbate by an increase in distribution size.
I've opened two feature requests, #7266 and #7267 that add resuming to downloads both in the installer and package downloader.
We'll prioritize tackling these during an upcoming sprint. In the meantime, we'd welcome contributions.
zol
on 21 Jun 2016
Added a --keepalive-time 2 to the curl command in the shell script
curl --progress-bar --fail --keepalive-time 2 "$TARBALL_URL" | tar -xzf - -C "$INSTALL_TMPDIR" -o
after which I was able to complete the download successfully.
But I have been facing issues with meteor add commands => eg.,meteor add angular-templates which gets stuck trying to download.
niwsa
on 22 Jun 2016
meteor create myapp is not working too. Issued this command 15 minutes prior to this comment:
Edit:
Btw, I am from PH.
alur222
on 22 Jun 2016
@skemb321 The most stable version I got is 1.3.3.1 , please try "meteor create myApp --release 1.3.3.1" it is the fastest and compiles normally does not consume many resources . The problem we have to do " meteor create myApp " is displayed " meteor 1.3.3 Downloading ... " , it stays there looping , including Windows 10 machines, this process V8 indicates that more than 1 GB. Happens is that some very current applications that use components and libraries new versions do not work.
Sorry for my bad english.
José Luis.
jlmu10
on 22 Jun 2016
Okay. I've just tested the curl command and now it works. For those who are experiencing problems like stucked "Downloading webapp...", @n1mmy 's solution worked for me. All you have to do is edit your /ect/hosts file just like stated above, restart networking and run meteor command again. It worked for me, not very fast, but it works! Thanks.
alur222
on 22 Jun 2016
I can't meteor update to 1.3.4.1. I am stuck at "Downloading [email protected]_1...". I'm doing this from Asia too...
yelongren
on 25 Jun 2016
In China, @n1mmy 's hosts solution works, but in a very slow way.
For now, I have no time in updating the install-cn.ourmeteor.com. But it was set to automatically mirror from source. So if you need to install any new versions of Meteor, just use sed to replace 1.3.4 to the version you need in the install script, like:
curl install-cn.ourmeteor.com | sed 's/1.3.4/1.3.4.1/' | sh
PS: The first few download requests of a version may not succeed. You can try it several times or wait a moment after the first try as CDN needs to cache that big file.
laosb
on 25 Jun 2016
Stuck at this
You are hitting the MaxCDN Amsterdam Datacenter
103.10.29.28
curl https://meteorinstall-4168.kxcdn.com/packages-bootstrap/1.3.3/meteor-bootstrap-os.linux.x86_64.tar.gz -o /dev/null
seems to download within ~10 minutes
I am from Nepal, Asia
BipinBhandari
on 25 Jun 2016
@BipinBhandari - I had same thing here using meteor update in socially meteor example app (from brazil).
But including the ip for meteor in /etc/hosts worked for me ( in my case i had to add 54.192.225.217 warehouse.meteor.com )
mariohmol
on 26 Jun 2016
@n1mmy - My update is now working correctly as per your solution. But whenever I want to run meteor from my project, downloading of [email protected]_4 starts downloading. The download gets to 100% within 2 minutes but then it gets stuck and the download never actually completes. Please help me here. I am living in India and my meteor version right now is 1.3.4.1.
devin6391
on 26 Jun 2016
@devin6391 Almost the same problem here, mine gets to 100%, then shows "Downloading of [email protected]_4" for a long time before throwing this error
c:\Users\Olumide\AppData\Local.meteor\packagesmeteor-tool1.3.4_1\mt-os.windo
throw error;
^
Error: No metadata files found for isopack at: /c/Users/Olumide/AppData/Local/.
at Isopack._loadUnibuildsFromPath (c:\tools\isobuild\isopack.js:900:13)
at c:\tools\packaging\tropohouse.js:514:19
at Array.forEach (native)
at Function._.each._.forEach (c:\Users\Olumide\AppData\Local.meteor\packag
at c:\tools\packaging\tropohouse.js:513:11
at c:\tools\utils\buildmessage.js:359:18
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:352:34
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:350:23
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (c:\tools\utils\buildmessage.js:324:26)
at Object.download (c:\tools\packaging\tropohouse.js:448:20)
at c:\tools\packaging\tropohouse.js:592:22
at c:\tools\utils\buildmessage.js:359:18
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:352:34
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:350:23
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (c:\tools\utils\buildmessage.js:324:26)
at [object Object].downloadPackagesMissingFromMap (c:\tools\packaging\tropo
at c:\tools\cli\main.js:440:30
at c:\tools\packaging\catalog\catalog.js:100:5
at c:\tools\utils\buildmessage.js:271:13
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:264:29
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:262:18
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:253:23
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at Object.capture (c:\tools\utils\buildmessage.js:252:19)
at Object.catalog.runAndRetryWithRefreshIfHelpful (c:\tools\packaging\catal
at c:\tools\cli\main.js:439:17
at c:\tools\utils\buildmessage.js:271:13
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:264:29
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:262:18
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at c:\tools\utils\buildmessage.js:253:23
at [object Object].withValue (c:\tools\utils\fiber-helpers.js:89:14)
at Object.capture (c:\tools\utils\buildmessage.js:252:19)
at c:\tools\cli\main.js:437:33
at Console.withProgressDisplayVisible (c:\tools\console\console.js:631:14)
at springboard (c:\tools\cli\main.js:436:11)
at c:\tools\cli\main.js:1045:5
olumytee
on 26 Jun 2016
@olumytee - At least you get error description in windows. In ubuntu 14.04, I don't get any.
devin6391
on 26 Jun 2016
@n1mmy I had the same issue with meteor-tools as others reported. Your /etc/hosts workaround worked for me.
wuworkshop
on 27 Jun 2016
Windows10 in Canada. I am having the same issues with meteor update and meteor add frappapoiy
The hosts workaround does not appear to resolve the issue for me. Looking forward to a resolution.
It was working a couple of weeks ago, so I think you are thinking in the right direction.
cmccowan
on 27 Jun 2016
The hosts workaround works like a charm!!!
musen
on 27 Jun 2016
Not working in Italy!
kevman
on 27 Jun 2016
Not working in Argentina. Waiting and searching solutions for hours now...
jmart2015
on 27 Jun 2016
Not working in India for Windows 7. Working fine for Ubuntu 14.04
linux-nerd
on 28 Jun 2016
Not working in Serbia on Windows. Please fix this, it is a severe issue.
TheRedDevil
on 28 Jun 2016
Hey folks. Thanks for the continued reports!
From what you're saying, it seems we're seeing failures on both the new and old CDNs. The old CDN may fail less for some people, but there are still people that see the same issue on both CDNs.
This reinforces my belief that the issue fundamentally is that networks are flaky. I suspect this has been exacerbated by the increase in meteor package download sizes in 1.3.x which occurred at the same time as we started migrating CDNs.
I think the solution is retry-and-resume style downloading, like wget does, both for initial meteor installation and also package downloading.
Here are the issues filed to implement this: #7266 #7267. PRs would be very welcome!
For those still having trouble downloading, here are a few things I can suggest:
- try a different network (eg, go to a coffeeshop or other location with a different ISP)
- try a different time of day (eg evening instead of morning, when internet conditions might be different)
- for package downloads: try using our secondary CDN (see the
/etc/hostsworkaround above for package downloads) - for meteor install: try using
wgetto get the download tarball and untar manually.
n1mmy
on 28 Jun 2016
Not working from Argentina.
Downloading [email protected]... \
stays forever.
I tried changing the /etc/hosts, and no luck! I tested during the whole day, for the last 2 days.
luchux
on 29 Jun 2016
Not working in South Africa. Windows 8 machine.
First attempt downloads till 100% but then stays on Downloading [email protected]_4....
Other attempts there after it goes straight to Downloading [email protected]_4...
dlodeprojuicer
on 29 Jun 2016
Not working in Nigeria .
meteor create appname gets stuck at Downloading [email protected]_1 for hours
kenshinman
on 30 Jun 2016
Hey all. I just updated our installer script to be a little more robust and try and resume downloads. I'm hopeful it will replicate the behavior of wget and help a lot or most of you here.
Please try installing again and let me know in the comments how it goes (maybe just +1 this comment if it works).
tmeasday
on 1 Jul 2016
From here in Nigeria, Works fine now. Thanks for the update @tmeasday
kenshinman
on 1 Jul 2016
Glad to hear it @kenshinman
tmeasday
on 1 Jul 2016
Thanks @tmeasday, now it works from Patagonia! cheers
luchux
on 1 Jul 2016
Not working in Ukraine on Windows 8. My meteor version right now is 1.3.3. Also meteor update --release 1.3.3.1 not working. Gets stuck at Downloading [email protected] for hours
7kokos
on 1 Jul 2016
Both updating and reinstalling? Or just updating?
tmeasday
on 1 Jul 2016
I had the same problem for downloading meteor-tools since a week, but today I changed the host and it's working!
Thanks for your work!
I'm on ubuntu 16.04 in hungaria
Thibeline
on 1 Jul 2016
My issues solved. Now I tried again and it works fine. Thanks
7kokos
on 1 Jul 2016
Working in South Africa, thank you.
dlodeprojuicer
on 1 Jul 2016
@tmeasday Not sure whether its protocol but just to say a big thank you for all your and Sachas input into meteor - it does not go unnoticed.
I am in South Africa.
Unfortunately no luck with your update – specifically:
curl https://install.meteor.com/ | sh – downloads okay but
when starting the APP
Downloading [email protected]_1 just hangs and hangs.
I tried @n1mmy method of nano etc/hosts – plugged in the new dns
and it worked.
Any idea when the CDN issue will be sorted or is this something that we have to live with?
rodallanmac
on 4 Jul 2016
@rodallanmac sounds like this PR would have helped you with the problem https://github.com/meteor/meteor/pull/7348
I'll try and get that out soon.
tmeasday
on 5 Jul 2016
NOT working.. NYC, Saturday July 9,. 3:28PM!
mralexgray
on 9 Jul 2016
NOT working... NYC, 7/11/2016, 11:48
Stuck on "Downloading [email protected]_4". Any workarounds?
FlyingTigra
on 11 Jul 2016
@FlyingTigra Did the progress bar already go by? Is the bar still spinning? Allow a few minutes for it to extract the (large) tarball. Also, see @n1mmy's instructions above (https://github.com/meteor/meteor/issues/6960#issuecomment-226641013) for a possible workaround. And please always include your operating system to help with triaging! :wink:
abernix
on 11 Jul 2016
Guys, stuck at the same problem.
Stuck on "Downloading [email protected]_4". am hitting amsterdam datacenter from my bangalore server.
Above-Solutions-India-Ltd
on 11 Jul 2016
Not Working, Medellín / Colombia 6:40pm
sebasdeldi
on 12 Jul 2016
@Above-Solutions-India-Ltd - perhaps try deleting (or moving) your ~/.meteor, then running curl https://install.meteor.com | sh again, (which will get you the new launch script with resuming). Then let me know how you go with new / older versions of Meteor.
tmeasday
on 12 Jul 2016
@sebasdeldi can you give more information please?
tmeasday
on 12 Jul 2016
@tmeasday i'm trying to run this project but it gets stuck while Downloading [email protected] / , i literally let it try to finish the download for about 4 hours, but it simply stays downloading, i'm on Mac OsX (El Capitan).
sebasdeldi
on 12 Jul 2016
@sebasdeldi what do you see when you run meteor --version? If not 1.3.4.4, can you try meteor update, and if that fails for the same reason, following the steps I posted above
tmeasday
on 12 Jul 2016
@tmeasday did what you said, my meteor version is 1.3.4.4, but i'm still having the same issue, it won't complete Downloading [email protected]... -
sebasdeldi
on 12 Jul 2016
@sebasdeldi: apologies, I misinterpreted the problem you were having. I think we'll need to ship https://github.com/meteor/meteor/pull/7349 to help with your issue.
tmeasday
on 12 Jul 2016
@n1mmy your solution described in https://github.com/meteor/meteor/issues/6960#issuecomment-226641013 worked well for me, thank you.
jalik
on 12 Jul 2016
@n1mmy Yup /etc/hosts hack works (from India) thanks :)
niwsa
on 12 Jul 2016
I am not really sure what actually happened, but my app's .meteor/release file was pointed to [email protected], so it tries to download [email protected]_4 and FAILS on windows 7. Then I tried same configuration on Ubuntu 16.04 and it WORKED.
On windows 7, I manually removed meteor-tool:1.3.0_4 and meteor-tool:1.3.2_4 ( Which had really long file name problems; so i used some advice from http://answers.microsoft.com/en-us/windows/forum/windows_xp-files/can-not-delete-a-file-the-folder-xxxx-contains/fb10b673-3466-e011-8dfc-68b599b31bf5?auth=1 )
Then I edit .meteor/release manually and changed that line "[email protected]" to "[email protected]" now it WORKS.
Hope that can help someone else.
sabitertan
on 12 Jul 2016
@sabitertan "Then I edit .meteor/release manually and changed that line "[email protected]" to "[email protected]" now it WORKS. "
thanks man! it's working for me!
LapshinIV
on 13 Jul 2016
I'm stuck on "Downloading [email protected]_4... ". I'm based in China. Anyone else?
Eagles2F
on 18 Jul 2016
This issue has started again. It's taking forver to download meteor-tool1.3.4_4 from Nigeria. Need start a new project and this is slowing me down. Thanks
kenshinman
on 18 Jul 2016
@Eagles2F From my discussions with @n1mmy, due to some legal things MDG currently is not able to solve this problem in China. You can try simply a reinstall and then update your app by modifying .meteor/release.
btw, I'm based in China too. You can join MeteorChina QQ group: 438397259
laosb
on 18 Jul 2016
Confirming same issue again from India as well. Cannot update meteor and development is blocked from my 2 days.
allpratik
on 18 Jul 2016
confirm problem also from Congo-Brazzaville. Update from 1.3 to 1.3.4.4 blocks after some % of download.
I'm working from windows so I suppose I can't do curl command.
ghost
on 18 Jul 2016
@n1mmy - Here's my output. i've tried the 'Editing thost file too and the problem persists. Thanks
http://debug.netdna-cdn.com -
You are hitting the MaxCDN London Datacenter
http://checkip.amazonaws.com -
41.58.238.122
The output of tracert static-meteor.netdna-ssl.com
Tracing route to static-meteor.netdna-ssl.com [94.31.29.248]
over a maximum of 30 hops:
1 265 ms 1 ms 1 ms www.huaweimobilewifi.com [192.168.8.1]
2 * * * Request timed out.
3 343 ms 41 ms 21 ms 10.200.15.1
4 48 ms 54 ms 25 ms 41.221.166.29
5 239 ms 212 ms 156 ms 41.221.166.26
6 67 ms 32 ms 32 ms host-13-101.a.nigol.net.ng [217.117.13.101]
7 307 ms 145 ms 158 ms 41.21.232.57
8 * * * Request timed out.
9 128 ms 124 ms 138 ms ae26-100-xcr1.lns.cw.net [195.59.222.29]
10 126 ms 133 ms 428 ms tinet-gw.lns.cw.net [195.2.22.218]
11 455 ms 138 ms 134 ms xe-11-0-3.lon25.ip4.gtt.net [89.149.185.69]
12 127 ms 128 ms 199 ms netdna-gw.lhr.ip4.gtt.net [46.33.89.78]
13 561 ms 140 ms 155 ms 94.31.29.248.ipyx-077437-zyo.above.net [94.31.29.248]
Trace complete.
Your Location Lagos/Nigeria/West Africa
kenshinman
on 19 Jul 2016
this is happening to me all of a sudden; stuck on downloading meteor-tool
troygolden
on 20 Jul 2016
@nosizejosh Did u:
host warehouse.meteor.com?- edit
/etc/hostsand put the IP from no. 1? - restarted networking after no. 2?
alur222
on 22 Jul 2016
@nosizejosh Those are the steps I did. It was stated above by @n1mmy and he explained it well above.
alur222
on 22 Jul 2016
@skemb321 i have just gone through and cannot find the proposed solution. can you please explain what to do? i am on windows. Tx
nosizejosh
on 22 Jul 2016
Changing host did not work for me. I had to uninstall and reinstall and remove the .meteor folder.
Troy
Please excuse my typing. I am out of the office and sending from my mobile device.
On Jul 22, 2016, at 9:40 AM, Raul Torrefiel Jr. [email protected] wrote:
@nosizejosh Did u:
- host warehouse.meteor.com ?
- edit /etc/hosts and put the IP from no. 1?
- restarted networking after no. 2?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
troygolden
on 22 Jul 2016
Hi @kenshinman, I have the same problem but I managed to start a new project by using meteor create --release 1.3.4.1 newProject 1.3.4.1 being the release version that a previous project uses. If you have a previous working project, you can check the release version in /project/.meteor/release
olumytee
on 23 Jul 2016
getting a extremely low download rate from China... maxcdn takes me to the datacenter in London, :-(
albe-rosado
on 25 Jul 2016
@albe-rosado In China, you'll need Shadowsocks/VPN or other ways to get access to _the internet_.
laosb
on 25 Jul 2016
Perhaps some assurance messaging would be helpful - there's just a single state at the moment "downloading meteor-tool@version" even though I'm sure it says downloading when it's actually unpacking/installing. If there was more information we'd know if it was actually hanging or it's just a slow connection etc...
s-devaney
on 26 Jul 2016
Friends,
I am having the same problem. I am using Windows 10.
I tried to add "54.192.225.217 warehouse.meteor.com" to C:\Windows\System32\drivers\etchosts and also to create METEOR_WAREHOUSE_URLBASE environment variable, but they didn't work.
I got a workaround using --release 1.3.2.4, as said before (meteor create myapp --release 1.3.2.4). But this workaround didn't work for todos example (it was fresh, with no /.meteor/local content).
If you want to debug, my IP was 177.33.34.220.
Thanks and regards!
fernandobalm
on 26 Jul 2016
Did a fresh install of Meteor on Windows 10 in Canada. Ran the meteor command on an existing project and it also hangs on Downloading [email protected]_1. Is there an alternative compilation method? Or will we just have to wait until this is fixed?
Thanks
Amritpd
on 28 Jul 2016
@Amritpd at what point does it hang? does it show a progress bar or a spinner?
tmeasday
on 28 Jul 2016
@tmeasday it hangs during the spinner.
Amritpd
on 28 Jul 2016
@Amritpd interesting. The spinner is actually during the unpacking process (i.e. the download finished). I can take several minutes without any real feedback (which is something we are working on).
However there are some reports of the unpacking failing, which we are investigating. How long did you wait?
tmeasday
on 28 Jul 2016
it does hang in the "Downloading meteor-tools 1.4.0" part, im in china.... it does install it, but takes forever, is faster when i install a package with npm...
albe-rosado
on 28 Jul 2016
@tmeasday I waited for over 30 min waiting for something to happen, but at that point I just pressed Ctrl+C and killed the unpacking process.
Amritpd
on 28 Jul 2016
Hi all, does anyone have a reliable workaround for this issue? It is mainly causing problems for us on our build server (Codeship) where we have less control of the environment or where the servers are.
dankelleher
on 28 Jul 2016
On the same laptop with bootcamp (Mac OS 10.11.6/Windows 7) I've been experiencing these issues for a bit now. Oddly enough Windows seems mostly fine now (although it had CDN issues too), but Mac OS is still having issues (seems CDN would be assigned via geolocation, not OS; doesn't that seem odd?)
You are hitting the MaxCDN Los Angeles Datacenter
24.152.181.52
traceroute
traceroute static-meteor.netdna-ssl.com
traceroute to static-meteor.netdna-ssl.com (94.31.29.248), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.483 ms 1.001 ms 1.304 ms
2 142.254.184.197 (142.254.184.197) 302.165 ms 265.364 ms 270.242 ms
3 76.167.20.9 (76.167.20.9) 288.060 ms 347.171 ms 333.399 ms
4 agg33.sndhcaax01r.socal.rr.com (72.129.3.96) 340.960 ms 327.377 ms 326.106 ms
5 72.129.1.0 (72.129.1.0) 315.297 ms 317.983 ms 311.742 ms
6 agg10.tustcaft01r.socal.rr.com (66.75.161.48) 321.115 ms 326.352 ms 327.008 ms
7 bu-ether26.tustca4200w-bcr00.tbone.rr.com (66.109.3.232) 326.865 ms 320.403 ms 320.450 ms
8 agg5.tustcaft01r.socal.rr.com (66.109.1.219) 327.686 ms
0.ae2.pr1.lax10.tbone.rr.com (107.14.19.54) 319.300 ms
0.ae3.pr1.lax10.tbone.rr.com (107.14.19.56) 316.059 ms
9 66.109.7.38 (66.109.7.38) 323.889 ms 325.724 ms 318.813 ms
10 ae10.cr1.lax112.us.zip.zayo.com (64.125.26.6) 328.966 ms 316.445 ms 313.462 ms
11 ae6.er3.lax112.us.zip.zayo.com (64.125.20.222) 319.423 ms 317.570 ms 316.508 ms
12 netdna-gw.lax.ip4.above.net (209.249.99.210) 370.444 ms 363.460 ms 369.462 ms
13 94.31.29.248.ipyx-077437-zyo.above.net (94.31.29.248) 370.365 ms 371.221 ms 371.744 ms
I'm in North San Diego County.
The /etc/hosts workaround for 54.192.225.217 did the trick.
meverett
on 28 Jul 2016
Hello,
I have just downloaded Meteor and cannot start it up. Stuck at "downloading meteor-tools"....
davtsa
on 28 Jul 2016
I'm havng the very same issue :(, this is upsetting
You are hitting the MaxCDN Atlanta Datacenter
200.8.45.204
My traceroute:
traceroute static-meteor.netdna-ssl.com
traceroute to static-meteor.netdna-ssl.com (94.31.29.248), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 3.500 ms 3.467 ms 3.449 ms
2 * * *
3 10.1.236.37 (10.1.236.37) 31.162 ms 31.155 ms 31.140 ms
4 10.1.231.81 (10.1.231.81) 32.106 ms 32.752 ms 32.762 ms
5 10.1.230.214 (10.1.230.214) 32.069 ms 32.308 ms 32.305 ms
6 ro-ccs-bdr-02-TenGig4-1-0.ln.inter.com.ve (10.1.230.62) 32.679 ms 32.626 ms 32.599 ms
7 tengigabitethernet4-1.asr1.ccs1.gblx.net (64.215.248.93) 32.523 ms 32.504 ms 32.485 ms
8 * * *
9 * * *
10 Cogent-level3-40G.Miami2.Level3.net (4.68.110.170) 71.267 ms GTT-level3-40G.Miami2.Level3.net (4.68.127.154) 71.168 ms Cogent-level3-40G.Miami2.Level3.net (4.68.110.170) 58.103 ms
11 be2055.ccr22.mia01.atlas.cogentco.com (154.54.24.233) 57.985 ms be2054.ccr21.mia01.atlas.cogentco.com (154.54.80.41) 74.056 ms be2055.ccr22.mia01.atlas.cogentco.com (154.54.24.233) 57.966 ms
12 netdna-gw.atl.ip4.gtt.net (173.205.55.2) 84.866 ms 78.576 ms 85.706 ms
13 be2848.ccr41.atl04.atlas.cogentco.com (154.54.6.118) 106.167 ms be2847.ccr41.atl04.atlas.cogentco.com (154.54.6.102) 120.418 ms 94.31.29.248.IPYX-077437-ZYO.above.net (94.31.29.248) 103.452 ms
My location is Caracas - Venezuela
Any help please? :(
kkoci
on 29 Jul 2016
I am having the same issue, I've been trying to upgrade to 1.4.
http://debug.netdna-cdn.com/ -
You are hitting the MaxCDN London Datacenter
http://checkip.amazonaws.com/ -
41.78.192.54
My tracert:
1 2 ms 1 ms 5 ms LINKSYS01522 [172.16.13.10]
2 * * * Request timed out.
3 275 ms * 269 ms 41.21.232.201
4 478 ms * 373 ms 10.118.29.90
5 462 ms 422 ms 433 ms 10.118.46.137
6 * 451 ms 402 ms 10.118.46.158
7 419 ms * 438 ms 195.59.222.29
8 453 ms * 450 ms tinet-gw.lns.cw.net [195.2.22.218]
9 451 ms 458 ms 447 ms xe-7-0-2.lon25.ip4.gtt.net [141.136.107.26]
10 425 ms 459 ms 406 ms netdna-gw.lhr.ip4.gtt.net [46.33.89.78]
11 * 414 ms * 94.31.29.248.ipyx-077437-zyo.above.net [94.31.29.248]
12 * 426 ms 463 ms 94.31.29.248.ipyx-077437-zyo.above.net [94.31.29.248]
My location is Kinshasa - DR Congo.
jlmbaka
on 30 Jul 2016
had the same issue with 3 apps one with meteor 1.3.4 and two with 1.3.5 I managed to run the 1.3.4 after couple of hours of trial and error and with using sudo and the hosts file solution. but I can't get the 1.3.5 apps to fire up.
also after the millionth time I got this error up:
/home/user/.meteor/packages/meteor-tool/.1.4.0-1.13j49n2++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:165
throw error;
^
Error: ENOENT: no such file or directory, open '/tmp/mt-657dth/os.json'
at Error (native)
so is this related to anything ?
edit:
outputs for traceroute:
traceroute to static-meteor.netdna-ssl.com (94.31.29.248), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 8.858 ms 8.855 ms 8.846 ms
2 10.45.5.65 (10.45.5.65) 23.429 ms 26.963 ms 28.149 ms
3 10.45.1.5 (10.45.1.5) 31.345 ms 32.869 ms 35.046 ms
4 10.36.4.22 (10.36.4.22) 37.759 ms 40.236 ms 42.735 ms
5 10.36.15.173 (10.36.15.173) 47.385 ms 10.36.11.21 (10.36.11.21) 50.503 ms 10.36.15.173 (10.36.15.173) 55.496 ms
6 10.36.11.46 (10.36.11.46) 52.251 ms 21.922 ms 10.36.15.141 (10.36.15.141) 24.684 ms
7 ae5-243.lon21.ip4.gtt.net (46.33.82.181) 95.906 ms 89.892 ms 93.613 ms
8 xe-7-1-0.lon25.ip4.gtt.net (89.149.183.210) 95.077 ms xe-10-3-1.lon25.ip4.gtt.net (89.149.182.14) 98.082 ms xe-7-1-0.lon25.ip4.gtt.net (89.149.183.210) 99.987 ms
9 netdna-gw.lhr.ip4.gtt.net (46.33.89.78) 103.189 ms 105.395 ms 107.616 ms
10 94.31.29.248.IPYX-077437-ZYO.above.net (94.31.29.248) 111.062 ms 113.030 ms 116.248 ms
You are hitting the MaxCDN London Datacenter
156.212.135.168
Location: Alexandria Egypt
romaad
on 2 Aug 2016
3 days I cant work on my project, and i'm on delivery time. Can't solve it with any of the solutions above.
Quite desperate.
You are hitting the MaxCDN Atlanta Datacenter
201.231.33.34
From Argentina, Windows 7, Downloading [email protected]
Any help is welcome.
jmart2015
on 2 Aug 2016
@jmart2015 - at which point are you hitting a problem
a) downloading the initial distribution curl https://install.meteor.com | sh OR
b) getting the right version of the tool for your project? (after the initial download has completed)
If b), it could be helpful to directly download the version you need for your project curl https://install.meteor.com?release=X.Y.Z | sh.
tmeasday
on 2 Aug 2016
@tmeasday In my case is the latter, the b) option
Going to try as You say, but is still weird tho
kkoci
on 2 Aug 2016
Hi @tmeasday, option B, doing meteor run on the project.
It stucks on downloading Meteor Tool 1.4.0. After the percentages the spinner goes forever.
I'm going to try downloading directly
jmart2015
on 2 Aug 2016
We are working on some inefficiencies with the way the tool downloads alternate versions, so it's definitely potential workaround to just download the one version you need initially.
@jmart2015 - in your case, I'd just update to 1.4.0.1 (if you are on 1.4 right now) - you can do it by modifying .meteor/release if you can't do it with meteor update
tmeasday
on 2 Aug 2016
I've added 54.192.225.217 warehouse.meteor.com to my /etc/hosts file on Linux Mint
It should work on Debian or Ubuntu, Xubuntu, etc
Worked for me though
Edit by @abernix:
The same work around above will work for all Unix-systems.
On Windows you can add the same line to: C:\Windows\System32\drivers\etc\hosts instead of /etc/hosts.
It should take effect immediately on both systems, and you can verify with ping warehouse.meteor.com
kkoci
on 2 Aug 2016
Hi @tmeasday , thank you for your help.
Still no luck with the update. Now i'm trying on Ubuntu (Vagrant), and same problem.
Is there anything I'm doing wrong? is there anything else I can try? Thanks in advance.
jmart2015
on 2 Aug 2016
If all else fails!! I found this very simple workaround.
- Ping warehouse.meteor.com
- Update hosts file in etc/hosts add warehouse.meteor.com IP
- Create a new project, copy files from your project into the newly created project, replace everything when prompted.
- Restart your app.
dlodeprojuicer
on 2 Aug 2016
@jmart2015 - what version do you have in .meteor/release? I would either:
- Update that file to
[email protected]OR - Download 1.4 in the first place:
curl https://install.meteor.com?release=1.4 | sh
tmeasday
on 3 Aug 2016
@tmeasday thank you Tom, it worked.
Now I have another problem related with the node-gyp issue, but thats beyond this.
Thank you again for your time and patience.
jmart2015
on 3 Aug 2016
We are affected by the issue:
Our infor:
debug.netdna-cdn.com / You are hitting the MaxCDN Atlanta Datacenter
http://checkip.amazonaws.com/
190.129.243.229
trace:
Traza a la dirección warehouse.meteor.netdna-cdn.com [198.232.124.36]
sobre un máximo de 30 saltos:
1 1 ms 1 ms 17 ms 10.0.0.2
2 2 ms 5 ms 1 ms 192.168.1.1
3 13 ms 15 ms 16 ms lo-0-cbb-erx-vr-dsl-sil3.entelnet.bo [200.87.254.194]
4 11 ms 17 ms 12 ms ge-1-0-127.cbbmse01.entelnet.bo [200.87.252.89]
5 15 ms 14 ms 14 ms ge-0-1-0-3-22.cbbasr01.entelnet.bo [200.87.251.217]
6 16 ms 18 ms 20 ms te-0-0-0-3.cbbcrs101.entelnet.bo [200.87.251.189]
7 25 ms 22 ms 21 ms 190.129.250.49
8 23 ms 19 ms 24 ms 190.129.250.78
9 25 ms 29 ms 25 ms xe4-2-2-0-graarctw1.net.telefonicaglobalsolutions.com [216.184.112.220]
10 101 ms 102 ms 107 ms 5.53.3.57
11 101 ms 113 ms 97 ms 84.16.14.189
12 101 ms 103 ms 105 ms be3017.ccr21.mia03.atlas.cogentco.com [154.54.11.157]
13 211 ms 218 ms 209 ms be2055.ccr22.mia01.atlas.cogentco.com [154.54.24.233]
14 224 ms 223 ms 227 ms be2123.ccr42.atl01.atlas.cogentco.com [154.54.24.197]
15 169 ms 121 ms 125 ms be2848.ccr41.atl04.atlas.cogentco.com [154.54.6.118]
16 128 ms 128 ms 125 ms netdna-gw.atl.ip4.cogentco.com [38.122.47.58]
17 122 ms 126 ms 131 ms 36-124-232-198.static.unitasglobal.net [198.232.124.36]
location/country/geographic area - Cochabamba/Bolivia/South America
Currently the workaround, 54.192.225.217 warehouse.meteor.com in hosts, is working, had read the details on https://github.com/meteor/meteor/issues/6960#issuecomment-226641013
Thanks
RogerCam
on 4 Aug 2016
54.192.225.217 warehouse.meteor.com
in my hosts file worked for me too:
Mac OSX 10.11.6, Meteor 1.4, Cologne, Germany
sweetppro
on 7 Aug 2016
this issue was fixed for me after setting my ubuntu DNS to google's 8.8.8.8
I don't know if there's any relation between this and the issue but I thought I would post it.
romaad
on 8 Aug 2016
If you're still having this problem please help debug!
Please copy-and-paste the contents of the following four things into this issue
---> You are hitting the MaxCDN San Francisco Datacenter
---> 14.161.12.17
--->
Windows 7 x64, VietNam
itcthienkhiem
on 12 Aug 2016
Hi, same issue here
1) You are hitting the MaxCDN Atlanta Datacenter
2) 201.242.218.171
Caracas, Venezuela
Many thanks and bye ....
mgrivera
on 12 Aug 2016
Mine is breaking for every meteor module, meteor tools, less, templating, you know it.
Singapore
kerukelw
on 14 Aug 2016
In my case, I was running out of diskspace on my macbook and noticed my ~/.meteor folder was consuming 18GB already. Started afresh and deleted ~/.meteor and ran curl https://install.meteor.com/ | sh which worked fine, but on meteor reset or meteor <anything really> it downloads the meteor-tool to 100% and gets stuck for hours with the spinning line.
The hosts file edit worked for me, but I had to give it a couple of minutes chance to finish up after the download. The status message after reaching 100% confusingly still reads 'Downloading meteor-tool@....' for a couple minutes though.
productiveme
on 14 Aug 2016
This is still happening. Download gets stopped at a random percentage. Downloading from India here.
Windows 10 x64
blueelvis
on 15 Aug 2016
Oddly it never works on the first attempt, you have to relaunch once or twice to get the tool (and then, when you try Meteor 1.4, it crashes... I'm having a great summer).
philohelp
on 16 Aug 2016
I'm having the same issue as well.
I think this is another great example of why NPM integration is seriously important.
ElegantSudo
on 16 Aug 2016
I'm having the same issue, we need to fix it asap, I just added the changes to my hosts file, will tell you if it works or not. thanks
davidpintos
on 17 Aug 2016
well, I'm from Argentina, i use OS X and i can confirm that adding 54.192.225.217 warehouse.meteor.com to the hosts file, doing meteor reset and then finally meteor it works fine, thanks.
davidpintos
on 17 Aug 2016
Same experience here on Linux, after reaching 100% for the download of meteor-tools it spins for hours. Same result after now many retries. Not sure if it is a CDN issue, given the download has finished, anyways I tried from Amsterdam and Virginia locations, same behavior.
Is there any way to increase the verbosity? Beginner question maybe, but I can't even meteor --help due to that issue ;-)
nebulade
on 18 Aug 2016
Hello
+1
I will be really happy to now how to increase meteor loading verbosity !
Thanks
sandreanybox
on 18 Aug 2016
Hello.
Same issue. Russia. Stuck at 65%
Downloading [email protected]_3....
aygiz
on 18 Aug 2016
Hey. Still having the issue.
CDN: You are hitting the MaxCDN Atlanta Datacenter
IP: 191.5.169.253
Country: Brasil
Traceroute:
traceroute to static-meteor.netdna-ssl.com (94.31.29.248), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 1.603 ms 2.436 ms 2.538 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
fermuch
on 18 Aug 2016
You are hitting the MaxCDN Atlanta Datacenter
http://checkip.amazonaws.com/: 131.72.78.249
My Location: Trinidad and Tobago
trinicoder
on 19 Aug 2016
Is there no permanent solution to this problem? i keep coming here anytime I run into this issue.
My older apps just get stuck at Downloading [email protected]_1....
Made a few changes and run the app but it just gets stuck Downloading [email protected]_1...
kenshinman
on 19 Aug 2016
Hey all, if you are having trouble downloading, I suggest you try reinstalling the latest version of meteor (1.4.1) (via curl https://install.meteor.com | sh, or using the windows installer), which includes a number of significant fixes to the downloading process. From there, hopefully installing older versions should be easier.
tmeasday
on 19 Aug 2016
Great! I am traveling and my data plan is limited to 3gb/month mobile data. I have to look for a good hotspot where I can download all of meteor, because else this will be the end of working remotely....
Hopefully, there is an end to the annoying auto update of meteor with #7445.
scharf
on 19 Aug 2016
I've installed the latest version of Meteor and my connection is closing when the meteor-tools downloading hits 60% - 80%, what can I do to solve it?
I'm from Brazil, SP.
Here is the error:
/home/loloud/.meteor/packages/meteor-tool/.1.4.1.186av8r++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:165
throw error;
^
Error: ENOENT: no such file or directory, open '/tmp/mt-1o9haw7/os.json'
Thanks!
allanesquina
on 23 Aug 2016
You are hitting the MaxCDN Atlanta Datacenter
181.233.198.74
Perú
the /etc/hosts hack worked for me too
merunga
on 24 Aug 2016
Hello, I installed the latest version meteor 1.4.1 on windows 7 professional, and now it's impossible run my projects. I use the last version of Webstorm, he try to connect many times to the CDN with this message in my console
warehouse.meteor.com/builds/EXSxwGqYjjJKh3WMJ/1471540227018/Hcy3FpwzyE/meteor-tool-1.4.1-os.windows.x86_32+web.browser+web.cordova.tgz
Sorry, this project uses Meteor 1.4.1, which is not installed and could
not be downloaded. Please check to make sure that you are online.
If I put the address of the CDN in the browser I can download the file.
From the command line it is not possible, the same from WebStorm.
Configuring the proxy in the terminal I get the following error:
https://warehouse.meteor.com/builds/EXSxwGqYjjJKh3WMJ/1471540227018/Hcy3FpwzyE/meteor-tool-1.4.1-os.windows.x86_32+web.browser+web.cordova.tgz
_http_client.js:50
throw new TypeError('Request path contains unescaped characters.');
^
TypeError: Request path contains unescaped characters.
at new ClientRequest (_http_client.js:50:11)
at TunnelingAgent.exports.request (http.js:31:10)
at TunnelingAgent.createSocket (MY_NODE_INSTALLnode_modules\request\node_mo
dules\tunnel-agent\index.js:117:25)
at TunnelingAgent.createSecureSocket as createSocket
at TunnelingAgent.addRequest (MY_NODE_INSTALLnode_modules\request\node_modu
les\tunnel-agent\index.js:80:8)
at new ClientRequest (_http_client.js:142:16)
at Object.exports.request (http.js:31:10)
at Object.socket.once.exports.request (https.js:182:15)
at Request.start (MY_NODE_INSTALLnode_modules\request\request.js:584:30)
at Request.end (MY_NODE_INSTALLnode_modules\request\request.js:1238:28)
at MY_NODE_INSTALLnode_modules\request\request.js:413:12
at nextTickCallbackWith0Args (node.js:420:9)
at process._tickCallback (node.js:349:13)
Thank You for help me
wakakokorosensei
on 25 Aug 2016
I'm trying from Montreal at the moment and hitting NY data center. The download gets stuck. Apparently the CDN issue persists.
When I try to create a new app with meteor create app-name it tries to download Meteor all over again and gets stuck, even though I have the latest version installed on my Windows machine. Does anyone know any workaround to this? I have installed Meteor and should be able to create n number of apps on my machine with that installation, avoiding repeated installations for each app.
ashpriom
on 30 Aug 2016
@ashpriom what does meteor --version show for you?
tmeasday
on 30 Aug 2016
@tmeasday Meteor 1.4.0.1
ashpriom
on 30 Aug 2016
@ashpriom that's really odd. Can you paste the output of running meteor create app-name in an otherwise empty directory?
@ashpriom that is not the latest version of Meteor, so it's not surprising that it's trying to download a new tool. I would suggest re-installing from scratch, 1.4.1 included improvements to downloading versions.
tmeasday
on 30 Aug 2016
@tmeasday Thank you. It's fine after update. I think the Windows installer from Meteor website still downloads 1.4.0. Or may be it is 1.4.1.1 but does not overwrite 1.4.0 installation. It only says 1.4 on the website. https://www.meteor.com/install
ashpriom
on 30 Aug 2016
These CDN issues are so bad. I cannot count anymore how many hours I lost to them. Docker images failing to build. CI tests fimeouting. And so on. Meteor became so flaky.
mitar
on 31 Aug 2016
@mitar are you continuing to see those issues with Meteor 1.4.1?
zol
on 1 Sep 2016
So currently it hangs for a bit, and then resumes, probably retry action kicking in. But it takes much longer than normal. So builds take much longer. But they do not fail anymore because of this, I think (they are failing with that tar Docker issue, so it is a bit hard to monitor why they fail, because it is common, but I have not seen timeouts anymore).
But CircleCI tests are still timeouting. For example, for Blaze repository: https://circleci.com/gh/meteor/blaze/67
mitar
on 1 Sep 2016
Got it thanks. The strange thing is (in SF at least) I don't find the new CDN to be any slower than what we used previously.
zol
on 1 Sep 2016
I think what it does it blocks concurrent connections. So I started getting timeouts on CircleCI when I increased parallelism to 4 from 1.
mitar
on 1 Sep 2016
I just tried testing this theory locally with 4 curls and it doesn't seem to affect anything. Can you devise a test that confirms this is happening?
zol
on 1 Sep 2016
But when Meteor is downloading packages, it is hitting up CDN with multiple requests in serial, not only one curl one, no? And then there are multiple ones in parallel.
Maybe you can use the Apache benchmarking tool ab to test it?
mitar
on 1 Sep 2016
I appreciate all the good information. Here is what I have done after I think I understood how to avoid the meteor-tool issue: taking a long time, apparently randomly, when I enter > meteor to run a project.
I am in an online course, and each week they give us a new project beginning. When I put it into the appropriate folder and run it (>meteor) it then takes a long time or even hangs running overnight. I am using Windows 7, but I do not think this is the real issue (I could be wrong). I have searched (using "File Finder") for meteor-tool and found Giga-bytes of different versions (e.g., 1.4.0-1).
Here is what I did (finally). Uninstall Meteor. Delete all .meteor folders on my computer (Not easy on Windows -- see other, but you may have to move to C:\ first or other such ways to get around the "long file name" problem.)
Now, start over. Install Meteor. Run (from a projects folder) > Meteor create myTest to create a myTest project. >cd myTest and then > Meteor to run the project. You can open localhost:3000 to verify that everything is good to here.
Now, go to myTest.meteor and open "release" in a text editor. Mine today shows [email protected]
When I look in C:\Documents and Settings\ ... \AppData\Local.meteor\packagesmeteor-tool, I see a folder 1.4.4_1 and in ... \AppData\Local\PaxHeader.meteor\packagesmeteor-tool
C:\Documents and Settings\Currie Win7 Desk\AppData\Local.meteor\packagesmeteor-tool, I also see a folder 1.4.4_1 .
Good, now when I go to the provided project, I go to provided_project.meteor and open "release" in a text editor I see something like this: [email protected] If I leave this, and run meteor, I have the problem which is being addressed in these posts. However, if I change this to [email protected] (the same as I had in the installation -- notice slight change in how it is presented in this file and in the computer folder: 1.4.4.1 vs 1.4.4_1 (which I do not understand, but it is what it is).
* So again, change the project "release" to 'agree' with the installation folder. *
That is the secret, apparently. Then when I start the project, it just runs!
Hope this helps you with this issue
Malcolm
MalcolmGC
on 1 Sep 2016
@mitar in your CI scripts is the tool downloading older versions? Do you install 1.4.1.1, then run meteor in an older app? Or is the problem the install in the first place?
A workaround (if it is the _tool_ being slow but not curl), would be install the version that you need to begin with with curl https://install.meteor.com?release=X.Y.Z | sh in the CI script.
tmeasday
on 2 Sep 2016
Hm, you are right. I have both devel branch and latest stable Meteor. See here. Do you think having both version on the system could make things break?
mitar
on 2 Sep 2016
@mitar, not necessarily. But am I right in saying that your test script is just running meteor test-packages ./ inside each package directory (or something equivalent)? I can't see why it would need to download older versions of the tool. Can you link me to a timing out build?
tmeasday
on 2 Sep 2016
I linked it above: https://circleci.com/gh/meteor/blaze/67
mitar
on 2 Sep 2016
And no, it should not download latest version of the tool.
mitar
on 2 Sep 2016
@mitar it seems to have hung at "Building plugin lintJshint in packa...", which doesn't seem to be anything to do with downloading the tool. No idea what that could be about.
I think we've seen similar timeout errors of late with meteor/meteor on circle too. I'm not sure if it's something meteor is doing differently (not sure what it could be TBH) or if it's a problem with Circle itself.
tmeasday
on 2 Sep 2016
Hm, maybe the log is cutoff and this is not the latest thing?
mitar
on 2 Sep 2016
CircleCI failure:
Updating package catalog
DDP disconnected while connection in progress
This command requires an up-to-date package catalog. Exiting.
/tmp/meteor/meteor --get-ready returned exit code 1
Action failed: /tmp/meteor/meteor --get-ready
You are hitting the MaxCDN Paris Datacenter
2.88.120.221
Riyadh, Saudi Arabia
I'm getting an error when creating an app using meteor create appname
it tries to download the packages but i get this errors :
=> Errors while creating your project
While downloading [email protected]...:
error: connect EHOSTDOWN 185.18.207.126:443 - Local (0.0.0.0:0)
While downloading [email protected]...:
error: connect EHOSTDOWN 185.18.207.126:443 - Local (0.0.0.0:0)
While downloading [email protected]...:
error: connect EHOSTDOWN 185.18.207.126:443 - Local (0.0.0.0:0)
While downloading [email protected]...:
error: connect EHOSTDOWN 185.18.207.126:443 - Local (0.0.0.0:0)
While downloading [email protected]...:
error: connect EHOSTDOWN 185.18.207.126:443 - Local (0.0.0.0:0)
While downloading [email protected]...:
error: connect EHOSTDOWN 185.18.207.126:443 - Local (0.0.0.0:0)
@n1mmy @MalcolmGC
ameensom
on 27 Sep 2016
I've been trying to install meteor, over the course of _several months_ now, attempting to contribute Markdown Support to Rocket.Chat. You can see there, that I've been working on this since Jul 22. All that time, I have tried to install on several machines, (latest 2 releases of 10.x, Several flavors of Ubuntu 16, and once, even Windows 10 out of desperation) and even tried several different networks, just to ensure it wasn't my networking situation.
I've even used corkscrew to set up tunneling for me on a migratory bastion server that I've moved around different regions using DO droplets. In each case, it's always the same:
I run:
curl https://install.meteor.com/ | sh
And in each case, I get:
curl: (7) Failed to connect to meteorinstall-4168.kxcdn.com port 443: Connection timed out
Retrying download in 5 seconds...
// repeat 9 more times
LongLiveCHIEF
on 30 Sep 2016
I started having problems to download meteor packages since one week ago and it has become worse and worse, not sure if anyone still experiencing the same (meteor per se is downloaded but packages fail):
maxcdn
You are hitting the MaxCDN Paris Datacenter
amazonwsip
84.76.115.221
tracert
static-meteor.netdna-ssl.com [94.31.29.248]
1 2 ms 3 ms 2 ms LIVEBOX [192.168.1.1]
2 26 ms 25 ms 25 ms 84.76.115.254
3 26 ms 29 ms 25 ms 10.255.205.113
4 23 ms 24 ms 24 ms 10.255.204.41
5 29 ms 27 ms 27 ms 10.34.212.157
6 * * * Tiempo de espera agotado para esta solicitud.
7 * * * Tiempo de espera agotado para esta solicitud.
8 * * * Tiempo de espera agotado para esta solicitud.
9 47 ms 43 ms 43 ms 10.34.34.45
10 44 ms 43 ms 43 ms bundle-ether101.madtr3.Madrid.opentransit.net [193.251.249.1]
11 43 ms 44 ms 45 ms be3012.ccr22.mad05.atlas.cogentco.com [130.117.14.137]
12 55 ms 49 ms 48 ms be2293.ccr22.bio02.atlas.cogentco.com [130.117.50.25]
13 61 ms 61 ms 61 ms be2423.ccr42.par01.atlas.cogentco.com [130.117.50.77]
14 62 ms 60 ms 61 ms be2108.agr22.par01.atlas.cogentco.com [130.117.50.133]
15 61 ms 62 ms 62 ms be2947.rcr12.b019498-0.par01.atlas.cogentco.com [154.25.7.105]
16 63 ms 64 ms 64 ms netdna-gw.cdg.ip4.cogentco.com [149.6.114.82]
17 63 ms 63 ms 63 ms 94.31.29.248.IPYX-077437-ZYO.above.net [94.31.29.248]
error
Errors prevented startup:
While downloading alanning:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading aldeed:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading aldeed:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading aldeed:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading aldeed:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading aldeed:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading aldeed:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading aldeed:[email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443While downloading [email protected]...:
error: connect ETIMEDOUT 54.192.62.173:443..etc
EDIT: After a long number of retries and waiting for some time it finally worked 👍
tcastelli
on 3 Nov 2016
@abernix @n1mmy Can something like https://unpkg.com/ help solve the issue for once and for all.
niwsa
on 4 Nov 2016
I think we need a participant vote on this, so please bear with this wall of text and vote at the end because I was about to close this issue about an hour before @tcastelli posted his most recent update. I felt like this was resolved best-as-possible, for a number of reasons:
- First, these are my (shortened) comments from about a week ago on another thread about an _actual_, identified problem with the current package server CDN provider which was occurring. Upon fixing the problem I saw improvement for many users (determined by a _noticeable_ decrease in install-related issue comments here in GitHub Issues across many issues, and success reported on IRC, Slack, emotes and more):
Surprisingly, the CDN was actually just behaving poorly – for example, I just straight-up could not
wgetthe entire meteor-tool through the CDN without it (remotely) closing the connection. I used to be able to, and then it just stopped workingI just reached out to MaxCDN Support over chat and worked with their support team for almost 45 minutes and they reproduced and corrected an issue on their end. For the first time in the last two weeks, I am able to fully download Meteor without using any work-arounds.
- The Meteor Installer now supports retrying on install thanks to #7348
- The Meteor package installer now supports retrying thanks to #7399
- And most recently, (about a week ago) Meteor 1.4.1.3 and Meteor 1.4.2 more intelligently deal with closed network connections (and trigger the above retry) thanks to 545493b34a7d4e00ec1418b69a3f17b385d158fa.
- This issue was actually IDLE for an entire month. I don't feel that would have happened without the above changes and I think this shows the problem is fixed for many users.
- This issue has grown a bit out of control and it's hard to even be sure of _specific_ issues anymore – for example, package downloads, NPM downloads, installer downloads – these all come from different servers and completely different networks! Any updates or +1s are probably involving dozens and dozens of people that aren't even having problems (or the same problem) anymore
- And related to the previous bullet, I think that @tcastelli's problem might be a specific problem with package-downloading/retrying which only affects Windows users. I've seen it myself on Windows from a connection where I have zero Meteor problems from Mac/Unix boxes. (I believe it happens when too many packages are attempted to be downloaded at once, versus a more delicate 2-at-a-time approach.)
Network problems may never (won't) go away – but Meteor _can_ get better at dealing with them, as has tried with the above solutions.
@niwsa, I'm not sure that replacing one CDN with another CDN is _the_ solution (nor do I think it would be a "once and for all"). Unpkg is really just another NPM CDN and using it, even right now, wouldn't solve this problem because Meteor is more than just NPM – its packages are not all NPM and are in their own atmosphere, well, literally.
It could be argued that the best-of-the-best CDN would be the most ideal for Atmosphere packages, but even if a particular CDN performs well for some users, it won't for others – a huge number of Meteor users are in places where network conditions just actually are bad – for example, China where the wall makes it very difficult for _anything_ to work properly – NPM or otherwise! There is no putting CDN problems to rest and NPM has fought with this problem for a long time - Meteor has an additional angle of needing packages from two sources: its own and NPM.
Let's vote, using reactions and comments
- I'll consider a 👍 reaction on this comment as a vote to "close" this issue. This should indicate that you think the CDN issues are resolved or improved enough. Of course, specific issues with specific conditions like @tcastelli's (package download+Windows+
ETIMEDOUT) are always welcome in new issues. - If you have any other feeling other than closing this issue, please post specifically what you are still having problems with (e.g. package/installer/NPM), include actual error messages (e.g.
transfer closed,connection interrupted,ECONNRESET,ETIMEOUT, etc), platforms (Windows, Mac), etc.
Based on the results, I will create new issues for specific problems, create action items, and we can work together to resolve those with the users who are affected by them.
My vote is still to close.
abernix
on 4 Nov 2016
I also think there's always gonna be networks errors and in general I think the new measures in latest versions are normally enough. However, like what happened with METEOR_WAREHOUSE_URLBASE, I think that another env variable could be used for packages url (or not sure if that exists already and we can use the trick to change it like with warehouse). Also some documentation about those env variables would be great (with possible url alternatives when experiencing problems).
Regarding opening more specific issues (Windows + multiple packages at the same time), I also think is a good idea, I just didn't know it was something related to Windows only. @abernix Should I open an issue for that or is that already tracked somewhere else?
tcastelli
on 4 Nov 2016
@tcastelli METEOR_WAREHOUSE_URLBASE is the environment variable for the package server which serves Atmosphere packages and meteor tool updates (which is actually just an Atmosphere package).
My request to you, for testing purposes, would be to use the Windows workaround suggested in this comment by setting METEOR_WAREHOUSE_URLBASE to the cloudfront URL. If you still have the problem you reported above it shows that this problem exists with either a) your own connection (I'm not saying this is the case); or b) completely separate, isolated networks/CDNs, but ultimately, a Meteor on Windows problem exists with package downloading networking code preventing it from being more graceful (namely retrying, failing and being more informative). If the problem goes away with the cloudfront URL, well, then it definitely indicates a CDN deficiency, but the networking code still needs some work. Either way, I think a "Windows package installation ETIMEDOUT error" issue for that would be a wise idea and I'd encourage anyone with those same circumstances to jump into that issue (and off of this one).
(Also, I quasi-agree on the documentation aspect, but that it should be a last resort as if we can get everything working properly it will take care of itself. I dislike the idea of users having to make these "tweaks", which tend to sit around forever, and think it would be preferred if we could intelligently make those decisions for them.)
abernix
on 4 Nov 2016
Thanks for the clarification about warehouse, I tried indeed to change it to cloudfront when I was facing the problem, and it dind't help at that time, so it doesn't seem something related to the CDN then. I have opened a new issue #8013 for Windows specifics.
In terms of documentation I think it won't hurt to have it well documented (especially if later on private servers area allowed), but I agree that automatically trying to fix the problem would be ideal, so maybe internally an array of WAREHOUSE_URLBASE urls could be stored in the build tool, and try to fetch from a different one if the first fails.
tcastelli
on 4 Nov 2016
It could be argued that the best-of-the-best CDN would be the most ideal for Atmosphere packages, but even if a particular CDN performs well for some users, it won't for others
Hm, but the previous CDN worker very well and none of those issues were present there. The long list of fixes you had to introduce now for retrying and all other stuff were simply not present there and there were no such long issues like this one with that CDN. So we do not have to talk about "best-of-the-best CDN" in abstract terms, we can just move to a previous CDN?
mitar
on 4 Nov 2016
I don't think you can say they were not present, just that you did not experience them.
There were absolutely problems with the old CDN as well – some of the problems that the community was hit with full force with the change to the new CDN (which by the way, again had an _identified problem_) were in-fact long-standing problems which may have been skipped over in the past. I think the improvements to the tool all make a lot of sense and most of them should have been there before. These have all made the tool more resilient for folks with sub-par network conditions, and the bottom line is it seems to be working now.
Ultimately, per my comments here I'm guessing this comes down to the _graciousness_ (emphasis on the emphasis) of MaxCDN and that makes a lot of sense. Amazon is probably less _gracious_.
abernix
on 4 Nov 2016
Though China users would still suffer network problems, it seems that the CDN works well for most developers. Thanks @abernix and MDG ones! I guess we can close this.
PS: I had already edited the issue content of this issue for China (Mainland) users. It should work.
laosb
on 5 Nov 2016
My issue also fixed and I can install Meteor and packages successfully. Thanks MDG.
cyclops24
on 6 Nov 2016
Per my comment above (and because this seems to _actually_ be solved), I'm closing this and locking further conversation on it.
I know this issue hit users hard. Thank you to the large number of participants who reported problems, submitted traceroutes, or otherwise provided improvements to the meteor tooling. Hopefully this will be far less of an issue in the future.
abernix
on 18 Nov 2016
Related issues
ADobrzycki
·
82Comments
damjuve
·
101Comments
cdcv
·
227Comments
queso
·
98Comments
jdalton
·
189Comments
Most helpful comment
Thank you all for your help debugging this so far!
For those having package download problems -- that is, if you see problems where meteor gets stuck "Downloading [email protected]... |" (@TheYojimbo @serkandurusoy @zidane28? @cyclops24?): here is a potential workaround to try.
First, lookup the IP address for
d3fm2vapipm3k9.cloudfront.net(eg withhost d3fm2vapipm3k9.cloudfront.net). For me it is currently 54.230.119.80, but it will be different depending on where in the world you are, and might also change over time.Next, edit /etc/hosts (eg
sudo vi /etc/hosts) and add the line:Now try re-running the meteor command that downloads packages. Once you have downloaded the packages, I recommend removing the line from
/etc/hostsas it's easy to forget about and come back later and not know why package downloads are broken =)Note this is for Linux and MacOS. I'm sure there is an equivalent way to do this on Windows, but I don't know it. Maybe someone here can contribute a way to override DNS on Windows?
Please report back how this workaround works for you!
For those of you who have had install problems -- that is, seeing
curl: (18) transfer closederrors when trying to install meteor (@dksharp @BlackGuyCoding @Goyapa @Gadheyan @allpratik @Scorpiion) I'd appreciate it if you could run a test for me. See if you can replicate the error with any of:If you consistently get an error on any of those, please try and run:
And see if it succeeds where curl fails.
Thanks!