...Actually, I think I just found the problem. I had my terminal set to broadcast an idle character, to prevent my ssh sessions from timing out. If I disable this, it seems to work fine.
I'm guessing that perhaps the idle characters are getting prefixed to whatever I type in the password prompt, so sudo fails. The problem didn't show up when using cap restart, since that takes a fraction of the time of a full deploy, and so rarely got an idle character in the middle of it (I think it defaults to once a minute). Hmm. Guess I better go find a better way of preventing my ssh sessions from disconnecting... On Aug 7, 2:07 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > Can you paste the output from Capistrano? Somewhere in all the noise > there is probably a line indicating why the command failed. > > - Jamis > > On 8/7/07, Jonathan del Strother <[EMAIL PROTECTED]> wrote: > > > > > cap deploy works fine up to the point where it restarts mongrel, at > > which point it complains that 'command "sudo /usr/bin/monit restart > > all -g mongrel" failed on xxxxxxxx' > > > Oddly, if I run the restart task separately (cap > > restart_mongrel_cluster), it works great, as does that same command > > via ssh. It's only when run in conjuction with deploy that it fails. > > Monit & mongrel files show no change during the deployment. > > > Any bright ideas what the problem might be? > > > Jon --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
