My first deployed app crushing
arthurmaxwj
FREEOP

a year ago

Hello,

It have a free trial version (which I can upgrade) that I almost made work with this small Rails app. I'm new to deploying, tho this repo works perfectly fine on Render hosting. I managed t make it work until it crashed after 10 minutes and now keeps crushing on each restart. I don't know what the issue might be.

I have the following Deploy log:


[289] ! Detected parent died, dying
[530] ! Detected parent died, dying
[420] ! Detected parent died, dying
[455] ! Detected parent died, dying
=> Booting Puma
=> Rails 7.1.3.4 application starting in production 
=> Run `bin/rails server --help` for more startup options
A server is already running (pid: 1, file: /rails/tmp/pids/server.pid).
Exiting
=> Booting Puma
=> Rails 7.1.3.4 application starting in production 
=> Run `bin/rails server --help` for more startup options
Exiting




Another part:

#<Thread:0x00007f6cbcfcc648@puma stat pld /usr/local/bundle/ruby/3.2.0/gems/puma-6.4.2/lib/puma/cluster/worker.rb:123 run> terminated with exception (report_on_exception is true):

/usr/local/bundle/ruby/3.2.0/gems/puma-6.4.2/lib/puma/cluster/worker.rb:135:in `write': Broken pipe (Errno::EPIPE)

	from /usr/local/bundle/ruby/3.2.0/gems/puma-6.4.2/lib/puma/cluster/worker.rb:135:in `<<'

	from /usr/local/bundle/ruby/3.2.0/gems/puma-6.4.2/lib/puma/cluster/worker.rb:135:in `block in run'
Solved

1 Replies

arthurmaxwj
FREEOP

a year ago

The solution was to add this to the end of Gemfile. No idea why, but now process booting works.

CMD rm -f tmp/pids/server.pid && ./bin/rails server -p 8080

Status changed to Solved itsrems • 11 months ago

Loading...