Sounds like an upgrade of Ruby might be called for, then. :( That, or you'll need to track down exactly what is causing the illegal instruction and see if you can work around it.

- Jamis

On Oct 16, 2007, at 9:27 AM, timgremore wrote:


Hi Jamis,

Thanks for the help.

ruby -v gets 1.8.5

and I get the same when I run rake db:migrate by hand.

On Oct 16, 9:52 am, Jamis Buck <[EMAIL PROTECTED]> wrote:
Sounds like a bug in the ruby version you have installed on the
remote machine. What version of Ruby is it, and how was it installed?
Do you get the same error if you log into the server and run rake
db:migrate by hand?

- Jamis

On Oct 16, 2007, at 8:05 AM, timgremore wrote:



I am working on deploying to TextDrive, however, when my migration
runs, it results in "Illegal instruction".  Here are the final few
lines of output when attempting 'cap deploy:cold' (or cap
deploy:migrate):

......
......
......
** transaction: commit
  * executing `deploy:migrate'
  * executing "ls -x /users/home/user/apps/admin/releases"
    servers: ["admin.online.nwtc.edu"]
    [admin.online.nwtc.edu] executing command
    command finished
* executing "cd /users/home/user/apps/admin/releases/ 20071016130739;
rake RAILS_ENV=production  db:migrate"
    servers: ["admin.online.nwtc.edu"]
    [admin.online.nwtc.edu] executing command
 ** [out :: admin.online.nwtc.edu] (in /users/home/user/apps/admin/
releases/20071016130739)
 ** [out :: admin.online.nwtc.edu] Illegal instruction
    command finished
command "cd /users/home/user/apps/admin/releases/20071016130739; rake
RAILS_ENV=production  db:migrate" failed on admin.online.nwtc.edu

Does anyone have a suggestion as to what is happening?




 smime.p7s
3KDownload


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to capistrano- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/capistrano
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to