# Capistrano deployment failing on db:migrate

**URL:** <https://www.ruby-forum.com/t/capistrano-deployment-failing-on-db-migrate/134225>\
**Category:** Deployment\
**Created:** [April 9, 2008, 3:41am UTC](https://www.ruby-forum.com/t/capistrano-deployment-failing-on-db-migrate/134225 "2008-04-09T03:41:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [April 9, 2008, 3:41am UTC](https://www.ruby-forum.com/t/capistrano-deployment-failing-on-db-migrate/134225/1 "2008-04-09T03:41:05Z")

</div>

From the error message I would assume that it is just a password issue,  
but for some reason the part of the deploy script that contains the  
method that normally prompts me for my password is not being run.

Here is the error message:  
command “cd /var/rails/my\_app/releases/20080409012418; rake  
RAILS\_ENV=production db:migrate” failed on the\_server.com

I am using the script that Bryan L. used in his linode deployment  
with some modifications to talk to a Git repository.

Thanks for any help.

---

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [April 9, 2008, 6:53am UTC](https://www.ruby-forum.com/t/capistrano-deployment-failing-on-db-migrate/134225/2 "2008-04-09T06:53:17Z")

</div>

Turns out the reason was that the Haml gem wasn’t yet installed on the  
server.

Problem solved.