Ruby on Rails application does not go up with Foreman

1

I’m trying to upload an application using the foreman, as it is necessary to upload the Rails and Tailwind process:

web: bundle exec puma -t 5:5 -p ${PORT:-3000} -e ${RACK_ENV:-development}
css: bin/rails tailwindcss:watch

But trying to upload for some reason the CSS process is killed, as in the log below.

Aug 22 02:18:23 PM  17:18:23 web.1  | /opt/render/project/rubies/ruby-2.7.5/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
Aug 22 02:18:23 PM  17:18:23 web.1  | /opt/render/project/.gems/ruby/2.7.0/gems/net-protocol-0.2.1/lib/net/protocol.rb:541: warning: previous definition of Socket was here
Aug 22 02:18:23 PM  17:18:23 web.1  | To use retry middleware with Faraday v2.0+, install `faraday-retry` gem
Aug 22 02:18:28 PM  17:18:28 web.1  | * Listening on http://0.0.0.0:10000
Aug 22 02:18:28 PM  17:18:28 web.1  | Use Ctrl-C to stop
Aug 22 02:18:31 PM  17:18:31 css.1  | exited with code 0
Aug 22 02:18:31 PM  17:18:31 system | sending SIGTERM to all processes
Aug 22 02:18:31 PM  17:18:31 web.1  | terminated by SIGTERM

Does anyone know what could be the reason?

2

Hi there,

One issue I can see that would potentially cause this is the Linux OOM killer is killing the css process. Should you not be compiling your CSS at build time and then just run rails/puma for you service?

Regards,

Keith
Render Support, UTC+10 :australia:

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.