Capistrano deployment failing with 'rbenv: /home/alexander/.rvm/bin/rvm: command not found'

Open
#71 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
devops

Research direction

Start with the reported Capistrano trace, especially the deploy:updated to bundler:install task chain and the SSHKit command failure. Reproduce the deployment with --trace and investigate why rbenv is looking for /home/alexander/.rvm/bin/rvm. Done means the bundle step completes without exit status 127.

Written by the indexing model from the issue text.

Description

I won't show the whole log but here's the error message:

    (Backtrace restricted to imported tasks)
    cap aborted!
    SSHKit::Runner::ExecuteError: Exception while executing as [email protected]: bundle exit status: 127
    bundle stdout: rbenv: /home/alexander/.rvm/bin/rvm: command not found
    bundle stderr: Nothing written

    SSHKit::Command::Failed: bundle exit status: 127
    bundle stdout: rbenv: /home/alexander/.rvm/bin/rvm: command not found
    bundle stderr: Nothing written

    Tasks: TOP => deploy:updated => bundler:install
    (See full trace by running task with --trace)
    The deploy has failed with an error: Exception while executing as [email protected]: bundle exit status: 127
    bundle stdout: rbenv: /home/alexander/.rvm/bin/rvm: command not found
    bundle stderr: Nothing written

I have no idea what this means. Ideas?

Dominant language
Ruby
Stars
140
Forks
44
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from capistrano/rvm

All issues in capistrano/rvm

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.