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

Error: EBADF: bad file descriptor on Fuge run #79

Closed
tfoutrein opened this issue Apr 20, 2016 · 7 comments
Closed

Error: EBADF: bad file descriptor on Fuge run #79

tfoutrein opened this issue Apr 20, 2016 · 7 comments
Assignees
Labels

Comments

@tfoutrein
Copy link

After installing fuge et generate the system on windows 10, i've tried to run it with fuge run .\fuge\compose-dev.yml
and i obtain this result :

D:\Projets\R&D\MicoServices\fuge\INMsSystem>fuge run .\fuge\compose-dev.yml
compiling...
starting proxy...
proxy frontend 10000 -> 172.16.152.117:20000
proxy api 10001 -> 172.16.152.117:20001
proxy service1 10002 -> 172.16.152.117:20002
proxy service2 10003 -> 172.16.152.117:20003
running: frontend
running: set PROXY_HOST=127.0.0.1&&set SERVICE_HOST=0.0.0.0&&set frontend_PORT=10000&&set api_PORT=10001&&set service1_PORT=10002&&set service2_PORT=10003&&set SERVICE_PORT=20000&& C:\nodejs\node.exe -r C:\Users\thomas_2\AppData\Roaming\npm\node_modules\fuge\fuge.js index.js
running: api
running: set PROXY_HOST=127.0.0.1&&set SERVICE_HOST=0.0.0.0&&set frontend_PORT=10000&&set api_PORT=10001&&set service1_PORT=10002&&set service2_PORT=10003&&set SERVICE_PORT=20001&& C:\nodejs\node.exe -r C:\Users\thomas_2\AppData\Roaming\npm\node_modules\fuge\fuge.js index.js
running: service1
running: set PROXY_HOST=127.0.0.1&&set SERVICE_HOST=0.0.0.0&&set frontend_PORT=10000&&set api_PORT=10001&&set service1_PORT=10002&&set service2_PORT=10003&&set SERVICE_PORT=20002&& C:\nodejs\node.exe -r C:\Users\thomas_2\AppData\Roaming\npm\node_modules\fuge\fuge.js service.js
running: service2
running: set PROXY_HOST=127.0.0.1&&set SERVICE_HOST=0.0.0.0&&set frontend_PORT=10000&&set api_PORT=10001&&set service1_PORT=10002&&set service2_PORT=10003&&set SERVICE_PORT=20003&& C:\nodejs\node.exe -r C:\Users\thomas_2\AppData\Roaming\npm\node_modules\fuge\fuge.js service.js
running: __proxy
_[frontend - 5924]: child_process.js:61
p.open(fd);
^

Error: EBADF: bad file descriptor, uv_pipe_open
at Error (native)
at Object.exports._forkChild (child_process.js:61:5)
at Object.setupChannel (internal/process.js:174:8)
at startup (node.js:50:16)
at node.js:404:3
process exit [5924]: frontend

p.open(fd);
^

Error: EBADF: bad file descriptor, uv_pipe_open
at Error (native)
at Object.exports._forkChild (child_process.js:61:5)
at Object.setupChannel (internal/process.js:174:8)
at startup (node.js:50:16)
at node.js:404:3

p.open(fd);
^

Error: EBADF: bad file descriptor, uv_pipe_open
at Error (native)
at Object.exports._forkChild (child_process.js:61:5)
at Object.setupChannel (internal/process.js:174:8)
at startup (node.js:50:16)
at node.js:404:3
process exit [10528]: api
process exit [9520]: service2

p.open(fd);
^

Error: EBADF: bad file descriptor, uv_pipe_open
at Error (native)
at Object.exports.forkChild (child_process.js:61:5)
at Object.setupChannel (internal/process.js:174:8)
at startup (node.js:50:16)
at node.js:404:3
process exit [11640]: service1

Could you help me please ?

@tfoutrein
Copy link
Author

Hello, do you have a solution or just an hint ?

@mcdonnelldean
Copy link
Contributor

@AdrianRossouw Has anyone tested fuge with Windows?

@tfoutrein
Copy link
Author

Am i the only one to try to use fuge on Windows 10 ?

@vastest
Copy link

vastest commented Jun 3, 2016

Have you got any workaround?

@StarpTech
Copy link

Run into the same issue Windows 10

@StarpTech
Copy link

Fixed this temporary by removing the IPC channel paramater when a process is spawned.
https://github.com/apparatus/fuge-runner/blob/master/lib/processRunner.js#L103

@mcdonnelldean
Copy link
Contributor

The issues was in Fuge Runner (cheers @StarpTech) This has now been resolved. You will need to npm link fuge runner until a release of fuge goes out but it won't be long.

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

No branches or pull requests

5 participants