App crashed for Node too many files open
bowtiedpickle
PROOP

a year ago

My app which had been running stably for several days just crashed.

In the past, when I've seen this, the only fix is redeploying the server a bunch until it lands on a host which is not fully occupied. No code or config changes are requirec to achieve this. This is a known issue and fix for others in my community of app builders.

Example trace, this will be triggered for every file in the project.

Triggering a new deployment of my app will trigger a lengthy (multi-day) processing event, which I really want to avoid. Restarting the existing deployment will not cause this to occur, but restarting also does not fix the too many files issue. Can support please assist?

```
Error: EMFILE: too many open files, watch '/app/src/MetadataRegistry.ts'

Sep 25 16:46:46

at FSWatcher.<computed> (node:internal/fs/watchers:247:19)

Sep 25 16:46:46

at Object.watch (node:fs:2471:36)

Sep 25 16:46:46

at createFsWatchInstance (file:///app/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:43327:17)

Sep 25 16:46:46

at setFsWatchListener (file:///app/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:43374:15)

Sep 25 16:46:46

at NodeFsHandler._watchWithNodeFs (file:///app/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:43529:14)

Sep 25 16:46:46

at NodeFsHandler._handleFile (file:///app/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:43593:23)

Sep 25 16:46:46

at NodeFsHandler._addToNodeFs (file:///app/node_modules/vite/dist/node/chunks/dep-D8YhmIY-.js:43835:21)
```

Solved

5 Replies

Hey there BowTied,

(Long time no talk!)

It seems that you are deploying a dev server to production - can you share your package.json so we can dig into your start command and why it's deploying a dev server?

Thanks,
Angelo


Status changed to Awaiting User Response Railway over 1 year ago


bowtiedpickle
PROOP

a year ago

This is invoked with start command bun ponder start , which is the canonical way to start the app. It is not a dev build, that is invoked with ponder dev. The start command is specified via railway settings.


Status changed to Awaiting Railway Response Railway over 1 year ago


Ponder seems to be shipping a dev server... you aren't the first Ponder user to report this. I might jump on TG to see what's up. However, you are going to have to trust me that open file counts isn't something our platform does.

Thanks,
Angelo


Status changed to Awaiting User Response Railway over 1 year ago


bowtiedpickle
PROOP

a year ago

I'd appreciate it if you can discuss with the ponder team, I know this continues to be an issue for the community. As an end user, the only way I've found to resolve this issue once it occurs is to redeploy. Restarting the deploy doesn't work. You can observe that I had to do that earlier.


Status changed to Awaiting Railway Response Railway over 1 year ago


Updating here- going to open an issue in GH and see where it goes.


Status changed to Awaiting User Response Railway over 1 year ago


Railway
BOT

7 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 7 months ago


Loading...