Problem launching Rails application

christer

After creating a Rails app, configuring domain, configuring the site route and testing that I can start and access the demo application, I have uploaded my own rails application, following the guides.

I have added puma to the Gemfile and after bundle install the puma gem appears as an installed gem.

However running the modified start script does not seem to launch puma: no puma process appearing with ps -aux (whereas starting the demo application launches a puma process).

There are no error messages from the start script, which produces the folloing output:

Puma starting in single mode...
* Version 4.3.6 (ruby 2.6.5-p114), codename: Mysterious Traveller
* Min threads: 0, max threads: 16
* Environment: development
* Daemonizing...
Started Rails for addruiad

Any ideas?

EDIT:
Forgot to say that the browser shows Error 502 Bad Gateway
I'm using mysql and the mysql2 gem
I noticed that I had forgotten to migrate the database and when I did, using rake db:migrate, I got the following error message:

NoMethodError: undefined methodhosts' for #<Rails::Application::Configuration:0x0000000002e114a8>
`
This comes from the statement added as per "Post installation steps" 2 in your guide. Could it be that my application runs under Rails 4.2.5 ??!!

sean

I think there's a bug in the current Rails installer, I should have it sorted out in the next day or so. Sorry about this!

christer

Hi Sean,
I upgraded my application to Rails 6 and now it works (after some effort...).

1) I noticed that your start script does not store the pid in tmp/pids so the stop script won't work (you need to kill the process by hand to stop rails).

2) Also, I can't see how to start puma in another rails environment than development. I looked in the puma readme, where it says that puma will read the RAILS_ENV environment variable. I could not get this to work. What I tried was:

copy the conf/environments/development.rb to conf/environments/opalstack.rb
copy the conf/webpack/development.js to conf/webpack/opalstack.js (modifying the line with 'development'
created an entry for opalstack in database.yml with the same info as for development
copied the start script to set RAILS_ENV, something like:
LD_LIBRARY_PATH=/opt/lib GEM_HOME=/home/xxxx/apps/xxxx/env RAILS_ENV=opalstack $PROJECTDIR/bin/bundle exec puma -p 12284 -d

When I launch the script it comes up with the message that it starts in development:

Puma starting in single mode...

Version 4.3.6 (ruby 2.6.5-p114), codename: Mysterious Traveller
Min threads: 0, max threads: 16
Environment: development
Daemonizing...
Started Rails for xxxx.

But the puma process is not launched

If I change the lauch statement in the start script to:

LD_LIBRARY_PATH=/opt/lib GEM_HOME=/home/xxxx/apps/xxxx/env $PROJECTDIR/bin/bundle exec puma -p 12284 -d -e ${RAILS_ENV=opalstack}

then the puma startup message says "Environment: opalstack", but the puma process is still not started

sean

christer FYI I've redacted your shell user name and app name from your example there.

I'm still trying to bang out the fixes for the Rails installer. Once I have that done, I'll have a look at how to get the environment configured the way you've described.

Thanks for your patience!

sean

christer I've just pushed an updated Rails installer that should fix the problems you've had.

The changes are:

The generated start script now runs puma daemonized via via rails s, with its PID file in the correct location
The generated README file had some paths in the wrong order in the section regarding setting up your own project. That same issue was present in our Rails docs in the help center, and has been corrected there as well.

If you want to use the new start script in one of your existing apps, feel free to adapt this example, just update the paths and change the port 55555 to match your what's in your current start script:

#!/bin/bash

# change the next line to your Rails project directory
PROJECTDIR='/home/myuser/apps/myapp/myproject'

# set your rails env, eg development or production
RAILS_ENV=development

APP_PORT=55555
PATH=/opt/bin:$PROJECTDIR/bin:/home/myuser/apps/myapp/env/bin:$PATH
PIDFILE="$PROJECTDIR/tmp/pids/server.pid"

if [ -e "$PIDFILE" ] && (pgrep -u myuser | grep -x -f $PIDFILE &> /dev/null); then
  echo "Rails for myapp already running."
  exit 99
fi

cd $PROJECTDIR
LD_LIBRARY_PATH=/opt/lib GEM_HOME=/home/myuser/apps/myapp/env $PROJECTDIR/bin/bundle exec rails s -e $RAILS_ENV -p $APP_PORT -d -P $PIDFILE

echo "Started Rails for myapp."