sshkit | deploying code and assets to servers | Continous Integration library

A wild guess: I had a similar problem and I could solve it by upgrading capistrano-passenger to >= 0.2.1

Looks like the version change of passenger from 6.0.7 to 6.0.8 has introduces a problem. I see you are also on 6.0.8, so it might affect you, too!

Link to the capistrano-passenger issue

I was able to get past this blocker. The ultimate issue is that I had to log into the correct shell and run gem install bundler:1.16.1.

In order to log into the bash I used this command: /bin/bash --login

Then run gem install: gem install bundler:1.16.1

Try add the allowed ssh keys to your production machine/ server. That is:

1. run cat ~/.ssh/id_rsa.pub on your local machine
2. Then run ~/.ssh/authorized_keys on your server/production machine
3. Copypaste the result of step 1 above in your authorized_keys file on your server
4. then run cap production deploy command again

Incase you don't see authorized_keys file when run ~/.ssh/authorized_keys you can combine all the above commands that is 1 to 3 by running cat ~/.ssh/id_rsa.pub | ssh USER@HOST "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys".

How I solved it:

1. Go to server command line
2. As we can see in error log, the last command before error appears was:

Command: cd /home/deploy/project/releases/20201018151933 && ( export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check )

So we go to our folder:

cd /home/deploy/project/releases/20201018151933

and run there command:

export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check

After that we see same error:

Could not find concurrent-ruby-1.1.7 in any of the sources. Run 'bundle install' to install missing gems.

1. In same folder run bundle install and after gem installed we can out of server command line.
2. Run cap production deploy and everything is gonna be fine.

I still don't know what is the root problem of this error, and how to fix it permanently, but this works for me. I hope it will be useful for anyone else.

AWS ec2 instance require pem key to connect to it, so you must tell capistrano what key is use, I think you need add this config to your deploy file:

I had endless problems deploying this app. Credentials problems, sassc nightmares and more. In the end, I started a new 5.2.2 project, copied in the controllers, models, migrations, views, routes, etc., and changed a few instances of [6.0] to [5.2]. First try deployed perfectly and the app is now live. I can only assume there is something not fully working with my rails 6 install. Thanks for your replies, guys.

I think I see what's going on. In your Dockerfile, change your DB_URL from: mysql:// to mysql2://

You are loading the mysql2 gem, but indicating to ActiveRecord that you want to use a connection via the mysql gem.

I had similar issues in the past deploying apps in small servers (5usd DO droplets, nano EC2). Those servers have little resources, and some heavy operations (installing nodejs, running bundle install) hit some problems. Try adding swap space to your droplet. https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04

The error tells you pretty much what's wrong. Neither Yarn or Node can be found on the server. Your installation might be incorrect.

Follow instructions to install both here:

https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

and here:

https://yarnpkg.com/lang/en/docs/install/#linux-tab

Then make sure you can call: