1.4.1 Extracting lasts forever

[morwalz]

I tried to install meteor on another system. Installation go well. then i copied my project and i am running meteor run but
" Extracting [email protected]" it is happening forever. then i tried to update version number to 1.4.1 and run again "meteor run". Now i do not need to install 1.4.0.1 so it worked but got stuck on extracting on other modules.

Possible reasons can be extraction program of this is release is faulty. this is urgent please someone suggest a solution or how can i download 1.4.0.1 release of meteor directly.

[RemyLespagnol]

I'm facing the same problem.

3 hours and nothing happens... I tried to restart but it doesn't work.

I try a meteor reset, an uninstallation of meteor... nothing...

I see that the .meteor folder size is increasing, but very slowly...

I'm on Windows 10

[laosb]

Do you have old versions of tar or 7z in your PATH? If so, install a new version of tar/7z (or even don't install at all since meteor will try a js-implementation of tar) and remove the old version. This might be related to #7689 .

[RemyLespagnol]

I reinstall 7z yesterday, but it's still the same issue.
I look at my PATH this evening and I'll retry this solution.

[morwalz]

same case for me. i tried without 7z and with latest 7z it is still not working.

[morwalz]

@laosb any quick help ? i am like stuck on this.

[jalalat]

i am also facing the same issue. Please help.

[RemyLespagnol]

I try in windows 7 and windows 10 without any workaround...

I don't have tar or 7z in my PATH.

[laosb]

So that was not related to #7689. Not sure what was happening if 7z itself works fine. @benjamn I guess this is in your realm?

[joelviel]

I have the same issue (Win10 64-bit Home). Endless extracting operation!

tar is not in my PATH

[bhawani21]

I am also facing this issue. I am completely stuck. any helps on this ?

[jalalat]

i do not know whether it is the right solution or not. I checked my task manager when extraction was in progress and i saw my antivirus was scanning and using a lot of memory. I immediately disabled it. Somehow it worked.
(NOT AN EXPERT)

[jalalat]

and use --patch option as there is a patch 1.4.1.1 now

[joelviel]

Actually the extraction operation was not endless for me, just insanely long (more than 30min).

[ManuelDeLeon]

After completely removing Meteor with a 3rd party uninstaller, it doesn't take forever anymore, but it still takes a LONG time to do anything. By anything I mean create a new project, add a package, update an existing project, etc. By long I mean 30-60mins.

Right now Meteor is unusable in Windows.

[morwalz]

it is still not working for me. I tried to keep it open for two days nothing happened. It does create new project, but does not install 1.4.0.1 stuck there.

[AliMor]

@morwalz use

where tar

command find all instance tar files and remove them. I had the same issue couple of days ago. I also, remove old version of 7z from my PC. I needed 7z so I installed new version (not necessary for Meteor) problem gone.

[redsummit]

I am seeing the same behavior on Max OS X. Any meteor (1.4.0.1) command that downloads files takes forever to run. Using bsdtar 2.8.3.

Update - it looks like this was related to an inaccessible download site.

[Nakroma]

Problem for me too. Can't add packages because weird extraction errors, and reverting doesn't work because it doesn't unpack meteor-tools. My friend also can't update meteor.

[suits-at]

+1

[bouchepat]

Same problem. Tried to do a simple meteor update as of last tuesday and stuck on extracting [email protected]_1...
On windows 7

[stefanholzapfel]

Hi!

I had the same issue. Obviously it is a problem with tar extractor.

I installed the newest 7zip and renamed the tar.exe in my GIT program folder ("where tar" command in cmd revealed, that somehow that exe was associated with .tar archives) to tar.exe.old.

Don't know which action solved the problem, but now extraction works.

[NenadPavlov]

Just to confirm as well it was an issue with tar that came with old version of git (which meteor was using for extraction). In my case I have upgraded git and tar disappeared. If I get it correctly instance of 7zip comes along with meteor update files and it is used for extracting. Everything went well reasonably quickly.

[morwalz]

i confirm this as well. it is due to tar.exe in git folder. I renamed it and it worked for me.

[abernix]

@spawn-guy Despite the fact that you may be on a 64-bit Windows, do you mind trying the 32-bit version of 7z1604 and see if the improvements are also noticeable? If I'm not mistaken, meteor-tool currently only builds a 32-bit Windows version for maximum compatibility. If the 7z1604 32-bit also shows the improvement you've indicated, then the version of 7z which is bundled with Meteor can easily be bumped. If it's still slow, then the (correct) solution might be a bit more complicated (e.g. a 64-bit exception or a separate build).

[aliig]

Running Windows 10 with Meteor 1.4.2.3. @meteorplus 's solution from 12 days ago worked for me (deleting 7z.exe from meteor_tool)

[ltung]

@mgleed & @metrorplus, Thanks for the idea. Instead of deleting 7z.exe (in case of breaking something), I just copied my newest version of 7z.exe from "c:\Proggram Files\7-zip" into "AppData\Local.meteor\packages\meteor-tool\1.4.2_3\mt-os.windows.x86_32\dev_bundle\bin" and everything seems working.

[bastiW]

@abernix

I can confirm that 7z1604 32bit is working on 64bit Windows 10

[jeffersondesouza]

The Download 7-Zip 16.04 (2016-10-04) for Windows: version worked to me.

type: .exe
Windows: 64-bit x64
Description: 7-Zip for 64-bit Windows x64 (Intel 64 or AMD64)

[abernix]

@bastiW Thank you for that confirmation and taking the time to test it. I've gone ahead and bumped the version of 7-Zip to the 32-bit version 1604 in 0dbfda3 and published it in 1.4.3-beta.3.

Unfortunately, due to the way that updating to a new version works and the implications of the the full effects of this fix will not be seen until the next release AFTER Meteor 1.4.3 becomes recommended. This is due to the fact that the previous version must extract the new version. I'll leave this open until that can be confirmed.

[benjamn]

This is going to be included in a small patch release (Meteor 1.4.2.4), which won't help with updating to Meteor 1.4.2.4 but will help when you later update to 1.4.3 or later.

[gepolv]

Meteor 1.4.2.7 still cannot work.

[santhosh-ps]

Installed Meteor 1.4.3 after uninstalling previous version, still not working. waiting to finish Extracting for more than 30 minutes now.

Edit: it worked after retrying and waiting for around 35minutes

[manuelro]

I have a 32 GB RAM Windows computer, and even though the process hangs and the fans start working like crazy. Meteor version 1.4.4.1. I did remove the 7z file provided by Meteor and replaced it with a freshly installed 7z from my local folder. Nothing seems to work. Although it will eventually install the new version, it's taking an enormous amount of time and resources.

[BadOPCode]

RAM is not a variable to this problem in Windows. The RAM drive (tmpfs) problem is something that can happen in *nix. Fans kicked on signifies that there is intense amount of CPU usage going on. Maybe snoop to see what processes are taking so much resource when it's installing. Just shooting blindly in the dark at the problem as I run Meteor in Linux... Sounds like something trying to do a ridiculously big recursion. It is finishing, but it's taking forever and gobbling resources. NPM has been known to lose it's mind in recursion when it's trying to solve dependencies. Sorry I can't be more help.

[spawn-guy]

Disable Windows Defender (or the AntiVirus that you use) while installing modules - It'll drastically speed up things!

Aaand there is nothing else to fix in current process, as Defender does what it needs to do - check the JS files and binaries for malicious code from an "unknown" source ( read the internets). And there are TONS of these files in distros.

7z distribution is fixed(to my knowledge) with official sources. High CPU load is doe to antivirus.

Don't forget to turn it ON afterwards. Or, well, just wait

[spawn-guy]

And another issue with LongPaths on Windows10 can be fixed with group Policies https://msdn.microsoft.com/en-us/library/aa365247(v=vs.85).aspx#maxpath

This, Imo, is worth mentioning in Readme

[x5engine]

@spawn-guy I don't use an anti virus and I have a gaming workstation :p this is due to the build taking too long due either to tmp folder full or some packages are not downloaded and keep getting re-downloaded and so on... sometimes it happens on linux but I found that it is related to the tmp folder being full so I clear it and it's good to go!

otherwise I will have to meteor reset the app to get it working again!

so I think this is just related to the build path! (needs some checking and validations)

[toledoroy]

Try to turn off Windows Defender

[muninn9]

Freeing up disk space worked for me

[llermaly]

After disabling windows defender instantly worked.

Windows key + Windows defender

Go go Windows defender security center
Click "Antivirus protection and against threats"
Configure antivirus and threat protection
Disable everything

good luck

[stevenqzhang]

I had a similar issue for 1.5.2. The extraction process just took super long (30+ min), and the lack of the spinner working led me to (wrongly) believe the extraction process was stalled

[hershko765]

also had this issue and i also tought its stuck, but its mostly just takes super long since the tar file is more or less extracting the globe, if your not sure you check if this folder is growing while the process is extracting:
C:\Users<USER>\AppData\Local.meteor
just verify that the process is not stuck and the folder size is growing

[afriC84]

This fixed the problem for me:
(I am running Meteor 1.6.1 on a Windows 10 machine)

1. Update git
2. choco uninstall meteor
3. check that the %appdata%/Local/.meteor folder is removed
4. remove the [project-folder]/.meteor/local directory
5. remove the versions-file in [project-folder]/.meteor
6. remove the [project-folder]/node_modules directory
7. choco install meteor
8. in the project-folder, run meteor npm install
9. in the project-folder, run meteor
10. wait, see and celebrate

edit: I afterwards got an error like Error: EPERM: operation not permitted with some more info concerning the eslint-plugin-react module. So I updated everything via meteor update.

Good luck ;-)

[yozawiratama]

thanks @llermaly it work, and now everything work fast.

when you run meteor command dont forget to disabled windows defender, and activate it when meteor ready