Run error on Windows

[ryanbuiltthat]

I'm trying to run my app using the iron run command or just iron but I'm hitting an error.

..\npm\node_modules\iron-meteor\node_modules\fibers\future.js:278
Error: spawn Unknown system errno 193

I'm just going to go ahead and say it, I have no effin' clue what this means. :) The app seems to do ok if I cd into the app directory and just run meteor. Am I missing something here?

[cmather]

Hmm does the nodes spawn command not work the same way on windows maybe? I may have to open up a VM and try it out.

On Apr 3, 2015, at 9:39 PM, Ryan Harris notifications@github.com wrote:

I'm trying to run my app using the iron run command or just iron but I'm hitting an error.

..\npm\node_modules\iron-meteor\node_modules\fibers\future.js:278
Error: spawn Unknown system errno 193

I'm just going to go ahead and say it, I have no effin' clue what this means. :) The app seems to do ok if I cd into the app directory and just run meteor. Am I missing something here?

—
Reply to this email directly or view it on GitHub.

[ryanbuiltthat]

Starting with meteor for me is also starting with node unfortunately. I didn't get any warnings about compatibility but you gave me at least a place to look into. Thanks! Not sure how much longer I'll keep my eyes open on this tonight but if I come across anything I'll let you know.

For the record I'm using the latest meteor package 1.1.0.1 on Win8.1

[cmather]

Yeah keep me posted. Will keep a mental note to check this out on next cycle.

On Apr 3, 2015, at 9:46 PM, Ryan Harris notifications@github.com wrote:

Starting with meteor for me is also starting with node unfortunately. I didn't get any warnings about compatibility but you gave me at least a place to look into. Thanks! Not sure how much longer I'll keep my eyes open on this tonight but if I come across anything I'll let you know.

For the record I'm using the latest meteor package 1.1.0.1 on Win8.1

—
Reply to this email directly or view it on GitHub.

[trinric]

I am getting a similar error when I try to run iron run :

Running windows 7 npm version 2.7.4, node v0.12.2

C:\Users\Ryan\AppData\Roaming\npm\node_modules\iron-meteor\bin\iron:12 }).run(); ^ Error: spawn UNKNOWN at exports._errnoException (util.js:746:11) at ChildProcess.spawn (child_process.js:1162:11) at exports.spawn (child_process.js:995:9) at module.exports (C:\Users\Ryan\AppData\Roaming\npm\node_modules\iron-meteo r\node_modules\shell-source\index.js:36:14) at syncSource (C:\Users\Ryan\AppData\Roaming\npm\node_modules\iron-meteor\li b\commands\run.js:9:3) at Command.<anonymous> (C:\Users\Ryan\AppData\Roaming\npm\node_modules\iron- meteor\lib\commands\run.js:30:5) at Command.invoke (C:\Users\Ryan\AppData\Roaming\npm\node_modules\iron-meteo r\lib\command.js:111:26) at Command.run (C:\Users\Ryan\AppData\Roaming\npm\node_modules\iron-meteor\l ib\command.js:91:21) at Command.runSubCommand (C:\Users\Ryan\AppData\Roaming\npm\node_modules\iro n-meteor\lib\command.js:154:11) at Command.<anonymous> (C:\Users\Ryan\AppData\Roaming\npm\node_modules\iron- meteor\lib\iron.js:66:17)

[Danjavia]

Same here
c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\node_modules\fibers\future.js:278
throw(ex);
^
Error: spawn Unknown system errno 193
at Object.Future.wait (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\node_modules\fibers\future.js:398:15)
at syncSource (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\commands\run.js:10:17)
at Command. (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\commands\run.js:30:5)
at Command.invoke (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:111:26)
at Command.run (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:91:21)
at Command.runSubCommand (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:154:11)
at Command. (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\iron.js:66:17)
at Command.invoke (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:111:26)
at Command.run (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:91:21)
at c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\bin\iron:11:8
- - - - -
at errnoException (child_process.js:988:11)
at Process.ChildProcess._handle.onexit (child_process.js:779:34)

[Danjavia]

Occur on windows 7
Thanks!

[ryanbuiltthat]

I've been hitting a few issues with some node modules and Windows lately. re-installing those modules specifically seems to help in a few of the cases. It may be worth a try to cd into the directory and run npm instlall and the specific module having an issue.

[Danjavia]

Trying...

$ npm install
npm WARN package.json hlabs@0.0.1 No repository field.

hlabs@0.0.1 postinstall c:\Users\danjavia\Desktop\Danjavia
bower install --config.interactive=false

danjavia@DIEGOSHK /C/Users/danjavia/Desktop/Danjavia/shrmelink
$ iron run

c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\node_modules\fibers\future.js:278
throw(ex);
^
Error: spawn Unknown system errno 193
at Object.Future.wait (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\node_modules\fibers\future.js:398:15)
at syncSource (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\commands\run.js:10:17)
at Command. (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\commands\run.js:30:5)
at Command.invoke (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:111:26)
at Command.run (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:91:21)
at Command.runSubCommand (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:154:11)
at Command. (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\iron.js:66:17)
at Command.invoke (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:111:26)
at Command.run (c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\lib\command.js:91:21)
at c:\Users\danjavia\AppData\Roaming\npm\node_modules\iron-meteor\bin\iron:11:8
- - - - -
at errnoException (child_process.js:988:11)
at Process.ChildProcess._handle.onexit (child_process.js:779:34)

[panphora]

I'm getting the same error trying to run the iron command on Win7.

---

PS F:\GitHub\Artisfy> iron

C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-meteor\node_modules\fibers
\future.js:278
throw(ex);
^
Error: spawn Unknown system errno 193
at Object.Future.wait (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron
-meteor\node_modules\fibers\future.js:398:15)
at syncSource (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-meteor
lib\commands\run.js:10:17)
at Command. (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iro
n-meteor\lib\commands\run.js:30:5)
at Command.invoke (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-met
eor\lib\command.js:111:26)
at Command.run (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-meteor
\lib\command.js:91:21)
at Command.runSubCommand (C:\Users\Seeker\AppData\Roaming\npm\node_modules\i
ron-meteor\lib\command.js:154:11)
at Command. (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iro
n-meteor\lib\iron.js:66:17)
at Command.invoke (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-met
eor\lib\command.js:111:26)
at Command.run (C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-meteor
\lib\command.js:91:21)
at C:\Users\Seeker\AppData\Roaming\npm\node_modules\iron-meteor\bin\iron:11:
8
- - - - -
at errnoException (child_process.js:1001:11)
at Process.ChildProcess._handle.onexit (child_process.js:792:34)

[mcrayne]

I get the same error on Windows 8.1. (error no. 193). Running Meteor 1.1.0.2. All latest Windows patches.

[nerdy-sam]

I think this is because shell-source isn't windows compatible...
https://github.com/jessetane/shell-source#how

In addition to the default source script provided, forward slashes are hardcoded as directory separators in index.js...
https://github.com/jessetane/shell-source/blob/master/index.js#L21

[cmather]

Oops. That might be it. The purpose of that is to source the env.sh file. You can see the code in lib/commands/run.js line 29. Perhaps we should make a PR to shell-source or just do this another way.

[nerdy-sam]

I like the idea of a PR to shell-source, but then again I'm bias as I just built my own PR for iron-meteor around shell-source features... Fixing the hard coded forward slash in their index.js and using my PR to expose a way to customize how env.sh is sourced could fix the problems for windows folks.
#142

[pavan4]

Is this fixed ? I tried your fix @mitzip but it didn't work for me.

[Auryg]

Same issue here.

[Crystal2030]

Is anybody fixed this issue? I met the same issue.

[ryanbuiltthat]

I gave up a while ago and went with Flow Router. The idea of scaffolding
was nice and all but I just got better at writing generic templates I could
use repeatedly.

On Sun, Jul 5, 2015 at 9:53 PM, Crystal2030 notifications@github.com
wrote:

Is anybody fixed this issue? I met the same issue.

—
Reply to this email directly or view it on GitHub
#138 (comment)
.

[babin93]

I also get this error, anybody knows if any fix is planned ?

[chrisbutler]

@ryanbuiltthat @Crystal2030 @Auryg @pavan4 @babin93 can you guys try to update to version 1.2.2 and see if that makes a difference?

[wodCZ]

@chrisbutler installed right now and found this issue. In v1.2.2 it is same:

[chrisbutler]

hey everyone, hopefully this will fix the iron run issue, although we still need to figure out how to support sourcing env.sh on Windows

can you guys try this version and let me know if that fixes it?

npm install -g https://github.com/chrisbutler/iron-cli/tarball/32546959145ada81690b5858956efaf34544abfd

[cmather]

Nice work chris. I wonder if it's better to just have the settings.json be the primary source of info, and it can read from environment variables for production environments. Those environment variables could be set in any number of ways. This would require putting the settings.json file through a template parser. It might be something like this:

{
  database_password: <%= process.env['DATABASE_PASSWORD'] %>
}

[ghost]

@chrisbutler fixed this bug with 1 line! see it #190
@ryanbuiltthat @cmather @trinric @Danjavia @panphora @mcrayne @mitzip @pavan4 @Auryg @Crystal2030 @babin93 @wodCZ test the followings on your own windows platform, have a nice day!
#200
#190

[chrisbutler]

thanks @spyhole. this fix is released in 1.3.1

[ghost]

@chrisbutler windows bugs(#198 #199) fixed with pull request #205