Sudo version 1.6.7p5 CentOS release 4.5 (Final) Linux 2.6.9-55.0.2.plus.c4smp
On Oct 17, 2:28 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > I'll bet it is sudo. What OS is the remote server? I wonder if the > sudo implementation is non-standard. > > - Jamis > > On Oct 17, 2007, at 2:04 PM, Justin wrote: > > > > > I don't see any output after either 'err' or 'out'. I think it's just > > returning a blank line. (?) > > > I ran the command manually using ssh, this is what I got: > > > 12:58:32 apps ~/Rails/test % ssh [EMAIL PROTECTED] -p 2222 "sudo -p > > 'sudo password: ' /opt/lsws/bin/lswsctrl restart" > > [EMAIL PROTECTED]'s password: > > sudo password: test > > <blank line> > > 12:58:54 apps ~/Rails/test % ssh [EMAIL PROTECTED] -p 2222 "sudo -p > > 'sudo password: ' /opt/lsws/bin/lswsctrl restart" > > [EMAIL PROTECTED]'s password: > > 12:59:07 apps ~/Rails/test % > > > The first run returns a blank line, and the second doesn't. Repeated > > restarts for the next few minutes returned without a blank line. After > > 5 minutes, it again returned a blank line. > > > Sudo's timeout is 5 minutes I believe. Could sudo be responsible for > > the initial blank line? > > > On Oct 16, 9:46 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > >> Note that the "err" prefix just means the text that follows was > >> printed by the remote process to stderr. (Similarly, "out" means the > >> text was printed to stdout.) It doesn't necessarily connote an actual > >> error. > > >> Another thing to try: > > >> default_run_options[:shell] = false > > >> That will cause all commands to be executed "bare", rather than via > >> "sh -c command". > > >> As for how to troubleshoot it--you might see how things pan out if > >> you execute the command via ssh directly: > > >> ssh [EMAIL PROTECTED] "command to execute" > > >> - Jamis > > >> On Oct 16, 2007, at 10:25 PM, Justin wrote: > > >>> I added the line, but it didn't resolve the issue. First run returns > >>> the "*** [err ::" and the following attempts within about a 5 minute > >>> period are successful. (sudo timeout?) > > >>> Also, I made a mistake and didn't realize that the issue does (seem) > >>> to occur with 2.0.0. However, it instead of "*** [err ::", it > >>> returns > >>> "*** [out ::" on the first run. > > >>> Could this be an issue caused by the return value from > >>> 'lswsctrl'. How > >>> can I debug the return value? > > >>> On Oct 16, 6:33 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > >>>> 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, it > >>>>>>> works just fine. However, if I wait for at least about 15 > >>>>>>> minutes, it > >>>>>>> will 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 command > > >>>>>>>>> Second run: (success) > >>>>>>>>> executing "sudo -p 'sudo password: ' /opt/lsws/bin/lswsctrl > >>>>>>>>> restart" > >>>>>>>>> servers: ["test.local"] > >>>>>>>>> [test.local:2222] executing command > > >>>>>>>>> Any ideas what is causing this error? Or, any suggestions on > >>>>>>>>> how to > >>>>>>>>> extract error information besides just "err"? > > >>>>>>>> Is litespeed running before that first run? Check /opt/lsws/ > >>>>>>>> logs in the > >>>>>>>> error/stderr log files... those typically have more > >>>>>>>> information. > > >>>>>>>> -philip > > >>>> smime.p7s > >>>> 3KDownload > > >> smime.p7s > >> 3KDownload > > > > > > > smime.p7s > 3KDownload --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
