Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deploy gets stuck and doesn't print anything #94

Open
anyelopetit opened this issue Sep 8, 2020 · 3 comments
Open

deploy gets stuck and doesn't print anything #94

anyelopetit opened this issue Sep 8, 2020 · 3 comments

Comments

@anyelopetit
Copy link

anyelopetit commented Sep 8, 2020

Steps to reproduce

cap production deploy
and that's it, just gets stuck forever until I abort it

Expected behavior

  • Continue with deploying
  • It must to print a TimeOut error log or something else

Actual behavior

When I run: cap production deploy it shows nothing, just keeps waiting
But when I run: cap production deploy --trace it shows this:

** Invoke production (first_time)
** Execute production
** Invoke load:defaults (first_time)
** Execute load:defaults
** Invoke rbenv:validate (first_time)
** Execute rbenv:validate

System configuration

https://gist.github.com/anyelopetit/7320fc8141554ea4b75ec88bb02f8132

@bobdutch
Copy link

I'm getting this with airbrake 11.0.3 and 12.0.0. Airbrake 11.0.2 works fine.

If you do cap staging rbenv:validate --trace I see that
.rbenv/versions/2.7.4/lib/ruby/gems/2.7.0/gems/airbrake-11.0.3/lib/airbrake/rake.rb:17 and
.rbenv/versions/2.7.4/lib/ruby/gems/2.7.0/gems/airbrussh-1.4.0/lib/airbrussh/rake/context.rb:61 call execute back and forth until there's a Stack Too Deep error.

@collimarco
Copy link

Have you found a solution?

Everything usually works fine, however today the deploy got stuck, without printing anything, until I aborted manually...

$ bundle exec cap production deploy
^C(Backtrace restricted to imported tasks)
cap aborted!
Interrupt: 

Tasks: TOP => rbenv:validate
(See full trace by running task with --trace)

@collimarco
Copy link

Ok in my case it was a problem with ssh.

The server was completely stuck (it had constant linear high cpu after a system reboot after an os update).

If I tried to connect to the server simply with ssh I got connection timeout.

That was the reason for the blank screen on cap deploy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants