Search code examples
ruby-on-railsdaemonpumamacos-ventura

Puma Rails server won't start in daemon mode on MacOS 13 Ventura after update from MacOS 12

I just updated from MacOS 12.x to 13.0.1

Starting a Rails app with

➜ rails s

works fine

=> Booting Puma
=> Rails 5.2.8.1 application starting in development
=> Run `rails server -h` for more startup options
Puma starting in single mode...
* Version 3.12.6 (ruby 2.6.6-p146), codename: Llamas in Pajamas
* Min threads: 5, max threads: 5
* Environment: development
* Listening on tcp://localhost:3000
Use Ctrl-C to stop

But when I try with

➜ rails s -d

Output stops at

=> Booting Puma
=> Rails 5.2.8.1 application starting in development
=> Run `rails server -h` for more startup options

And no server is started

➜ ps -ef | grep puma
501 69877 51917   0  6:45   ttys000    0:00.00 grep puma

➜ ps -ef | grep rails
501 72493 51917   0  6:49   ttys000    0:00.00 grep rails
Solution

  • Well, I found a workaround. This is by no means perfect but if it helps anyone with the same problem:

    nohup rails s </dev/null >/dev/null 2>&1 &

    The & at the end will make it run in the background. All output/input goes to/from /dev/null and nohup makes sure it will run even after you quit the session.