Getting 504 and "Error: EIO: i/o error, read"


#1

My project was working fine, before I changed the title and description. As far as I know, that’s all I changed.

Now I’m getting continuous log errors and a 504 on the preview

fs.js:675

  return binding.read(fd, buffer, offset, length, position);

                 ^

Error: EIO: i/o error, read

    at Object.fs.readSync (fs.js:675:18)

    at tryReadSync (fs.js:540:20)

    at Object.fs.readFileSync (fs.js:575:19)

    at Object.Module._extensions..js (module.js:653:20)

    at Module.load (module.js:556:32)

    at tryModuleLoad (module.js:499:12)

    at Function.Module._load (module.js:491:3)

    at Module.require (module.js:587:17)

    at require (internal/module.js:11:18)

    at Object.<anonymous> (/app/node_modules/htmlparser2/lib/Parser.js:1:79)

I’ve gotten this on a few other projects that seemed to resolve it’self after some time, or after a console refresh (not sure if it was the refresh or if it actually fixed it’self) but in this case refreshing seems to do nothing.

Edit: I just checked after four hours and it seems this has again resolved it’self. Still rather frustrating though


#2

Now I’m getting similar errors in a completely different project

 DONE  Compiled successfully in 102265ms17:19:24


events.js:183

      throw er; // Unhandled 'error' event

      ^


Error: listen EADDRINUSE 127.0.0.1:3000

    at Object._errnoException (util.js:1022:11)

    at _exceptionWithHostPort (util.js:1044:20)

    at Server.setupListenHandle [as _listen2] (net.js:1351:14)

    at listenInCluster (net.js:1392:12)

    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)

    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:10)


 DONE  Compiled successfully in 43276ms17:20:59


events.js:183

      throw er; // Unhandled 'error' event

      ^


Error: listen EADDRINUSE 127.0.0.1:3000

    at Object._errnoException (util.js:1022:11)

    at _exceptionWithHostPort (util.js:1044:20)

    at Server.setupListenHandle [as _listen2] (net.js:1351:14)

    at listenInCluster (net.js:1392:12)

    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)

    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:10)


fs.js:675

  return binding.read(fd, buffer, offset, length, position);

                 ^


Error: EIO: i/o error, read

    at Object.fs.readSync (fs.js:675:18)

    at tryReadSync (fs.js:540:20)

    at Object.fs.readFileSync (fs.js:575:19)

    at Object.Module._extensions..js (module.js:653:20)

    at Module.load (module.js:556:32)

    at tryModuleLoad (module.js:499:12)

    at Function.Module._load (module.js:491:3)

    at Module.require (module.js:587:17)

    at require (internal/module.js:11:18)

    at Object.<anonymous> (/app/node_modules/webpack/lib/Compiler.js:14:30)


 DONE  Compiled successfully in 37156ms17:22:16


events.js:183

      throw er; // Unhandled 'error' event

      ^


Error: listen EADDRINUSE 127.0.0.1:3000

    at Object._errnoException (util.js:1022:11)

    at _exceptionWithHostPort (util.js:1044:20)

    at Server.setupListenHandle [as _listen2] (net.js:1351:14)

    at listenInCluster (net.js:1392:12)

    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1501:7)

    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:10)

#3

Hi @chase,

I am sorry you’re getting these errors! Unfortunately, I am not able to reproduce. If you agree, I’ll check directly on your projects when this issue shows up again. Just let me know when it happens, and if I am around I’ll give a look :slight_smile:


#4

Thanks for the reply @etamponi

I’m getting errors right now on https://glitch.com/edit/#!/nuxt-layout-transition


#5

Ouch, right now I am out, I’ll be able to check in a few hours at least :frowning:


#6

No worries! :smiley: Appreciate the help all the same


#7

Also having the 504 Gateway Time-out and not getting into console at all today. Glitch in Glitch?


#8

Hi @AmandaAtMain,

the 504s are probably caused by a crash of your application. Not getting to the console might be connected to it, but we’ll take a look :slight_smile: Thanks!

@chase, I’ve been able to start your project again. If the issue represents, let me know. I’ve added myself to the project members, so that I can immediately connect and see the logs and the terminal.


#9

Getting similar errors to this on one of my servers today, remixed my code onto another server and it runs fine!

I can get into the console fine from what I can tell, anything I can try to get it back up?


#10

im reciving the same error as well


#11

can you tell me the project name?