running bun server in pm2 now crashes: ENXIO: No such device or address, SIGHUP

[CodeFromAnywhere]

What version of Bun is running?

0.8.1

What platform is your computer?

Linux 5.15.0-79-generic x86_64 x86_64

What steps can reproduce the bug?

• run a bun server via pm2 (like NODE_ENV=production pm2 start bun --name \"bun-server\" -- start)
• bun run start, which is called here by pm2, would run this: NODE_ENV=production bun src/server.cli.ts ,which in turn would launch a server using Bun.serve

What is the expected behavior?

pm2 works

What do you see instead?

it crashes (see screenshot)

Additional information

I don't know how to make it easy to reproduce, as this is my entire server. But maybe it also happens on a smaller server? Anyway, the server worked fine before on bun 0.7.3

[CodeFromAnywhere]

Can confirm that it runs on 0.7.3 so it's a regression happening in 0.8.1

PS: also got some weird looking errors related to https://www.npmjs.com/package/@swc/core (binding errors) and also a (maybe unrelated) SIGSEGV error. As a temporary solution I have downgraded bun back to 0.7.3 in production, using curl -fsSL https://bun.sh/install | bash -s -- bun-v0.7.3.

[bnussman]

I am experiencing this when running my server with concurrently.

Edit: I actually was able to bypass this issue by running concurrently with bun by doing bun --bun concurrently

[CodeFromAnywhere]

Not sure if 0.8.1 changed in the meantime (I've downgraded to 0.7.3 and upgraded again just now) but now I'm getting error: script "start" exited with code 11 (SIGSEGV) without changing anything.

The curious thing is:

• when I run bun start without pm2, it runs without segfault
• when pm2 uses bun to run the start script, it gets this segfault.
• on macOS I have no trouble at all, only on linux

Conclusion: Still have no idea how to fix and thus I'm stuck at 0.7.3

[Jarred-Sumner]

We will fix this in Bun v0.8.2

In the meantime, make sure your linux distro has /dev/ mounted. On alpine, it might not be mounted by default

[jakebailey]

This is fixed by #4378, right?

[jdgriffith]

I'm still experiencing this issue on 1.0 and on a ubuntu box. Reverting to 7.3 gives me a stable runtime again though.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"