Try this: default_run_options[:pty] = true
Throw that in your deploy.rb and see what happens. - Jamis On Oct 16, 2007, at 6:56 PM, Justin wrote:
Problem doesn't occur with version 2.0. Bug in 2.1? On Oct 16, 5:24 pm, Justin <[EMAIL PROTECTED]> wrote:It seems to have something to do with sudo's timeout (of about 5 minutes). Any ideas? On Oct 15, 10:25 pm, Justin <[EMAIL PROTECTED]> wrote:Yes, it is. No errors in the log.To add, as long as I restart for a period soon after the first, itworks just fine. However, if I wait for at least about 15 minutes, itwill again error. Another attempt will complete successfully.On Oct 15, 10:29 pm, Philip Hallstrom <[EMAIL PROTECTED]> wrote:I have overridden 'deploy:restart' for Litespeed. The restart task fails the first time it is run, but is successful when run for a period of time immediately after.First run: (failure?)executing "sudo -p 'sudo password: ' /opt/lsws/bin/lswsctrl restart"servers: ["test.local"] *** [err :: test.local:2222] executing commandSecond run: (success)executing "sudo -p 'sudo password: ' /opt/lsws/bin/lswsctrl restart"servers: ["test.local"] [test.local:2222] executing commandAny ideas what is causing this error? Or, any suggestions on how toextract error information besides just "err"?Is litespeed running before that first run? Check /opt/lsws/ logs in theerror/stderr log files... those typically have more information.-philip--~--~---------~--~----~------------~-------~--~----~To unsubscribe from this group, send email to capistrano- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/capistrano-~----------~----~----~----~------~----~------~--~---
smime.p7s
Description: S/MIME cryptographic signature
