On Monday, 2 December 2013 17:22:53 UTC-5, dbray wrote:
>
> That's a peculiar invocation, use a debugger to make sure :scm_password is
> set the way you think it is.
>
> Or try:
>
> set(:scm_password) {
> Capistrano::CLI.password_prompt("#{scm_user}@#{scm_server}
> password: ")}
>
> The form you suggested gives exactly the same behaviour as the one we were
already using.
I have also verified that the contents of scm_password is indeed the same
as what is input. I even replaced the block prompt assignment with a
string literal:
set( :scm_password, "the_actual_password" )
and got exactly the same results.
The error string looks like this:
failed: "env HLL_DB_ENV=production
PATH=$HOME/.rbenv/shims:$HOME/.rbenv/bin:$PATH RAILS_ENV=production sh -c
'git clone -q -b ForEx-Deploy-V.04.000.0000rc1
ssh://[email protected]/var/data/vcs-git/hll/hll_th_forex_rss.git
/var/data/hll_th_test/hll_th_forex_rss/releases/20131203013423 && cd
/var/data/hll_th_test/hll_th_forex_rss/releases/20131203013423 && git
checkout -q -b deploy 4a2be6f366c5bb31205713cc73a04a5996c8ed11 && (echo
4a2be6f366c5bb31205713cc73a04a5996c8ed11 >
/var/data/hll_th_test/hll_th_forex_rss/releases/20131203013423/REVISION)'"
on xnet241.hamilton.harte-lyne.ca
If I run the sh -c command directly on the host that I am running cap
deploy from I get no error and everything is created as expected:
sh -c 'git clone -q -b ForEx-Deploy-V.04.000.0000rc1
ssh://[email protected]/var/data/vcs-git/hll/hll_th_forex_rss.git
/var/data/hll_th_test/hll_th_forex_rss/releases/20131203013423 && cd
/var/data/hll_th_test/hll_th_forex_rss/releases/20131203013423 && git
checkout -q -b deploy 4a2be6f366c5bb31205713cc73a04a5996c8ed11 && (echo
4a2be6f366c5bb31205713cc73a04a5996c8ed11 >
/var/data/hll_th_test/hll_th_forex_rss/releases/20131203013423/REVISION)'
I have tried this with set( :deploy_via, "checkout" ) and set(
:deploy_via, "remote_cache" ) and both generate the same logon errors. The
failed instructions for both, although different from each other, work
perfectly when executed from the user shell on the deployment host.
This has to be an ssh issue of some sort. Is there any way to get the -v
switch passed to ssh as used by Capistrano?
--
You received this message because you are subscribed to the Google Groups
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web, visit
https://groups.google.com/d/msgid/capistrano/7efb9ac8-35b4-41d8-8122-90644419508e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
