Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why this error happend? nodejs Error: write EIO

I made a webApp with nodejs + mongodb + Backbone on window7-32bit, everything goes fine until yestoday. but I got this error this morning:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: write EIO
    at errnoException (net.js:883:11)
    at Object.afterWrite (net.js:700:19)

I googled around but no luck, I tried update node, and then got this error:

npm ERR! Error: write EIO
npm ERR!     at errnoException (net.js:883:11)
npm ERR!     at Object.afterWrite (net.js:700:19)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "update"
npm ERR! cwd C:\work\selink
npm ERR! node -v v0.10.4
npm ERR! npm -v 1.2.18
npm ERR! syscall write
npm ERR! code EIO
npm ERR! errno EIO

why this error happened suddenly? any hint about it?

Thanks for any ideas.

like image 593
Hetfield Joe Avatar asked Jun 11 '13 01:06

Hetfield Joe


People also ask

What is EIO error?

An I/O error occurred while reading from or writing to a file system. . EIO errors are serious errors reported from the underlying filesystem. They are not caused by MQ, other than MQ making use of calls provided by the operating system.

Why is npm start giving error?

If you try to run the command from a different directory, it won't find your package. json file and the Missing script: "start" npm error is caused. If you don't have a package. json file, create one by opening your terminal in your project's root directory and running the command npm init -y .


1 Answers

I have just been playing with Unicode support in Windows command prompt, using the code-page 65001 I can't get npm to install, giving me the above error. Changing the code-page to 850 chcp 850 and running the exact same npm command it then works fine.

Thus your problem could very well be related to the encoding your environment is in.

like image 69
serverdude Avatar answered Sep 21 '22 08:09

serverdude