"fatal error: all goroutines are asleep - deadlock!" #3287
Comments
|
I don't know anything about docker. But I tried anyway and couldn't get this to work. Here's what I tried: $ git clone https://github.com/epicweb-dev/web-auth
$ cd web-auth
$ git checkout ebe638c4966e0d44da0ebc88094af55dd0defcc5
$ cd scripts/deployed
$ docker build -t "test:Dockerfile" .
$ docker run -t "test:Dockerfile"
setting up swapfile...
node:internal/process/esm_loader:97
internalBinding('errors').triggerUncaughtException(
^
[Error: EROFS: read-only file system, open '/proc/sys/vm/swappiness'] {
errno: -30,
code: 'EROFS',
syscall: 'open',
path: '/proc/sys/vm/swappiness'
}
Node.js v18.17.0What commands are necessary to reproduce this with the code that you linked to? |
|
Yeah, I worried about that. I think it may only be reproducible on a lower end machine. If you want to try it locally, remove the bit about the swap file. Then the Dockerfile should work locally. But like I said it may only reproduce on a low-end machine (maybe you can simulate that in docker? I don't know). You could probably reproduce this on fly (within the free tier) if you want to try that. Create an account and install fly. You'll need to change the app name in the fly.toml to something unique, then do: fly apps create [your app name]Then you can run And it should deploy and reproduce. You can see logs in the fly dashboard. |
|
I tried making an account (with a disposable email) but then I get this: I'm not doing this, sorry. I also tried removing the swapfile stuff and then running things with |
|
Bummer. Sorry for another dead end on this. Do you have any ideas what could possibly cause this? |
|
And a follow-up question. Do you know why this would cause my server process to exit even if I add a |
|
Ok, here's an update: I realized the reason my server was crashing was due to accidentally watching a lot of files with chokidar. After adding more logging and finding the issue, I fixed it and now I'm not getting the deadlock issues. I'm not sure whether that's related or not, but the fact is I'm not getting this issue anymore so I think we can safely close it. |
|
I am also encountering the Interestingly, when I stop the Angular server and the Additionally, it's worth noting that my setup involves building the Angular application (version 17.1.3) inside a Docker container based on the I am looking for any guidance or suggestions on how to resolve or work around this issue. Has anyone else experienced something similar in a Dockerized environment, particularly with the mentioned versions of Node.js and Angular, on a Mac M1 Pro Max? Any insights or recommendations would be greatly appreciated. Thank you in advance for your assistance. |
Hello! I know you've received a few reports like in the past and they weren't actionable because they were not reproducible. I think I can reproduce this though.
So my case is kinda unique. I'm using
mdx-bundlerwhich usesesbuildunder the hood to compile over a hundred mdx files when I startup my app (and then I call it during runtime as well, but my issues happen during startup). I have only successfully reproduced this issue when trying to deploy to Fly. Here are the logs:You might be able to reproduce it locally with the same Dockerfile. You'll find the Dockerfile and relevant files here: https://github.com/epicweb-dev/web-auth/tree/ebe638c4966e0d44da0ebc88094af55dd0defcc5/scripts/deployed
It's not much, so I'll just stick it here
Dockerfile
setup-swap.js
package.json
{ "name": "deployed-web-auth", "private": true, "type": "module", "scripts": { "start": "kcdshop start" }, "author": "Kent C. Dodds <me@kentcdodds.com> (https://kentcdodds.com/)", "license": "GPL-3.0-only", "dependencies": { "@kentcdodds/workshop-app": "^2.12.3", "execa": "^7.2.0" }, "engines": { "node": ">=18", "npm": ">=8.16.0" } }fly.toml
When I last reported this issue (#1608), it was solved by adding queuing around where I call
bundleMDX(which is what callsesbuild) to ensure it's only called one at a time. I've added that same queuing to this, but that has not affected the outcome at all. The error I pasted above has been consistent through all the things I've tried.I hope this report helps to identify what's causing this issue (#1608, #1842, #2485, #2727) for once and for all!
The text was updated successfully, but these errors were encountered: