Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.3.4.3 + windows] Error: EPERM, symlink ... dev_bundle #7374

Closed
gjr-qm opened this issue Jul 9, 2016 · 28 comments
Closed

[1.3.4.3 + windows] Error: EPERM, symlink ... dev_bundle #7374

gjr-qm opened this issue Jul 9, 2016 · 28 comments

Comments

@gjr-qm
Copy link

@gjr-qm gjr-qm commented Jul 9, 2016

An hour ago meteor-tool was automatically updated on my machine (Windows 10). After that my existing application resulted in an error when starting (meteor).

Creating a new project with 'meteor create test-app' doesn't work either. The error i get is:

...\AppData\Local.meteor\packages\meteor-tool\1.3.4_3\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:165
throw error;
^
Error: EPERM, symlink '...\AppData\Local.meteor\packages\meteor-tool\1.3.4_3\mt-os.windows.x86_32\dev_bundle'

I tried stepping back to version 1.3.4_1 (which worked), but then meteor-tool is automatically updated again to version 1.3.4_3.

Anyone else having this problem? And is there a workaround (previous version worked just fine)?

@gjr-qm gjr-qm changed the title meteor-tool error in primise_server after upgrade to 1.3.4_3 (Windows 10) meteor-tool error in promise_server.js after upgrade to 1.3.4_3 (Windows 10) Jul 9, 2016
@jordnz
Copy link

@jordnz jordnz commented Jul 9, 2016

Same here, windows 8.1

Can't do anything..

Can't run any apps, update meteor, or even check what version I'm on - just get the same error you are.

@dongzhi-yang
Copy link

@dongzhi-yang dongzhi-yang commented Jul 9, 2016

Same here, I am on windows10
C:\Users\claud_000\AppData\Local.meteor\packages\meteor-tool\1.3.4_3\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:165
throw error;
^
Error: EPERM, symlink 'C:\Users\claud_000\AppData\Local.meteor\packages\meteor-tool\1.3.4_3\mt-os.windows.x86_32\dev_bundle'

It was working a few hours ago, and all of sudden it stopped working and giving this error.

@Jogibaer1963
Copy link

@Jogibaer1963 Jogibaer1963 commented Jul 9, 2016

Same here on Windows 10.

@Rahman-S-M
Copy link

@Rahman-S-M Rahman-S-M commented Jul 9, 2016

I got it for windows 7

@Rahman-S-M
Copy link

@Rahman-S-M Rahman-S-M commented Jul 9, 2016

any workarounds would help.. completely blocked..not able to do any thing.

@Jogibaer1963
Copy link

@Jogibaer1963 Jogibaer1963 commented Jul 9, 2016

How can I downgrade the meteor-tool and stop the automatic update ?

@NitroBAY
Copy link

@NitroBAY NitroBAY commented Jul 9, 2016

Same here I tried uninstalling, reinstalling but the bug is still here on windows 10. Whenever I try to create a new project with an old release meteor --release 1.3.2, I can't run with meteor as it says You're not in a Meteor project directory and when I retry to create a project it says You're not in a Meteor project directory. I need in emergency a solution, I'd already a lot of retard with my current project, now I'm in a critical situation... If anyone can furnish a solution it would be great.

@Rahman-S-M
Copy link

@Rahman-S-M Rahman-S-M commented Jul 9, 2016

I found a way to downgrade to old version.

there is a meteor.bat file @ C:\users\XYZ\AppData\Local .meteor
change the version from 1.3.4_3 to 1.3.4 and its working..

@echo off
SETLOCAL
SET METEOR_INSTALLATION=%~dp0%
"%~dp0\packages\meteor-tool# 1.3.4\mt-os.windows.x86_32\meteor.bat" %*
ENDLOCAL
EXIT /b %ERRORLEVEL%

@NKumarPraveen
Copy link

@NKumarPraveen NKumarPraveen commented Jul 9, 2016

I too facing same issue windows 7

@NitroBAY
Copy link

@NitroBAY NitroBAY commented Jul 9, 2016

In any way I hope such a problem will not happen again, and meteor will test its releases, a full framework who's front and back-end make code unusable without the framework. Without guaranties for the future, I'll definitively stop counting on the framework as a reliable solution...
PS : only one month before windows integrates Ubuntu shell and so no problem with windows cmd anymore for those on W10 :D

@D-Nice
Copy link

@D-Nice D-Nice commented Jul 9, 2016

Same issue here... I will try Rahman's fix, in mean time this needs to be resolved.

EDIT: On Windows 7. I personally did not have 1.3.4, so downgraded to 1.3.4_1 and it works now.

@Kootain
Copy link

@Kootain Kootain commented Jul 9, 2016

same issue here. but there will no problem when i create app in c:/users/username. So i try to run as administrator and it works.

@gjr-qm
Copy link
Author

@gjr-qm gjr-qm commented Jul 9, 2016

Running the commandprompt as administrator works for me too.

Before that i used Rahman's approach, in addition to which i made the meteor.bat file read-only, because it was overwritten each time i started meteor.

@benjamn
Copy link
Member

@benjamn benjamn commented Jul 9, 2016

I will unrecommend 1.3.4.3, which should prevent meteor.bat from getting updated to that version.

Can anyone provide a longer stack trace than what's already been provided?

@gjr-qm
Copy link
Author

@gjr-qm gjr-qm commented Jul 9, 2016

Is there a switch that i can use for a longer stack trace? I'd be glad to help out, but a clue would be welcome.

@benjamn
Copy link
Member

@benjamn benjamn commented Jul 9, 2016

Running the shell (cmd.exe or PowerShell) as an Administrator should be a workaround for this problem, as @Kootain suggested.

Alternatively, here's how you can grant a non-Administrator user the ability to create symbolic links (though it takes an Administrator to grant the privilege).

I will note that fs.symlink(target, link, "junction") is supposed to be possible without Administrator privileges, so I'm not sure why it wouldn't work.

One more question: Are your application directories also on the C:\ drive?

@gjr-qm
Copy link
Author

@gjr-qm gjr-qm commented Jul 9, 2016

My applications are on another drive (not C:)

Using meteor create blah on the C:\ drive results in de same error

@benjamn
Copy link
Member

@benjamn benjamn commented Jul 9, 2016

@gjr-qm can you try creating an app on C:? Note: at this point you'll have to do meteor create --release 1.3.4.3 app-name, since 1.3.4.3 is no longer "recommended."

@gjr-qm
Copy link
Author

@gjr-qm gjr-qm commented Jul 9, 2016

@benjamn your command produces the same error when i run it as a regular user.

@abernix
Copy link
Member

@abernix abernix commented Jul 9, 2016

@benjamn These stack traces appear to be missing a slash in the path between Local and .meteor, no?

AppData\Local.meteor\
@benjamn
Copy link
Member

@benjamn benjamn commented Jul 9, 2016

@abernix I think that's just from copy-pasting the \.

@gjr-qm
Copy link
Author

@gjr-qm gjr-qm commented Jul 9, 2016

Check! The \ is there in the stack traces

@benjamn
Copy link
Member

@benjamn benjamn commented Jul 9, 2016

My hunch is that the fs.symlink is failing because the target is on a different disk (C:\) from the app, though I haven't ruled out the administrator privilege issue.

@gjr-qm
Copy link
Author

@gjr-qm gjr-qm commented Jul 9, 2016

I think it is not the drive, because it doesn't matter on which drive i try to run or create the app, it always results in the error when i do it as a regular user.

But when i run the command prompt/Powershell as administrator, then it simply works on all drives.

benjamn added a commit that referenced this issue Jul 9, 2016
benjamn added a commit that referenced this issue Jul 9, 2016
This wouldn't work if .meteor/dev_bundle needed to be a true symbolic
link, but fortunately we just need to record the target path in a way that
allows us to read it later.

Fixes #7374.
@benjamn benjamn mentioned this issue Jul 9, 2016
1 of 1 task complete
@benjamn benjamn self-assigned this Jul 9, 2016
@benjamn benjamn added this to the Release 1.3.4.4 milestone Jul 9, 2016
@gjr-qm
Copy link
Author

@gjr-qm gjr-qm commented Jul 9, 2016

Great work, thanx @benjamn!

@benjamn
Copy link
Member

@benjamn benjamn commented Jul 10, 2016

This should be fixed if you meteor update --release 1.3.4.4.

@avenchen
Copy link

@avenchen avenchen commented Jul 10, 2016

in windows 10, I open dos command with administrator, then run meteor. It works.

@benjamn benjamn closed this Jul 10, 2016
@abernix abernix changed the title meteor-tool error in promise_server.js after upgrade to 1.3.4_3 (Windows 10) [1.3.4.3 + windows] Error: EPERM, symlink ... dev_bundle Jul 11, 2016
@Almaju
Copy link

@Almaju Almaju commented Aug 1, 2016

Doing meteor reset worked for me. (Meteor 1.4)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet