Advertisement
Guest User

timeout

a guest
Aug 25th, 2014
230
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.15 KB | None | 0 0
  1. [18:36:34] Miroslav Anashkin: On the master node
  2. Open `/opt/rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/astute-0.0.2/lib/astute/config.rb`
  3.  
  4. There is Vim installed on 4.1.1 master node.
  5. Change the following parameters:
  6. 1.
  7. conf[:PUPPET_TIMEOUT] = 90 * 60 # maximum time it waits for the whole deployment
  8.  
  9. Default timeout for the deployment is 90 minutes, it is set in seconds.
  10. Please increase it to, say , 150 * 60 (150 minutes) as following or to any reasonable value.
  11.  
  12. conf[:PUPPET_TIMEOUT] = 150 * 60 # maximum time it waits for the whole deployment
  13.  
  14. 2.
  15. conf[:REBOOT_TIMEOUT] = 120 # how long it can take for node to reboot
  16. I would recommend to increase it to 300, or to the number of seconds, enough to reboot your current servers.
  17.  
  18. Save the config file.
  19.  
  20. Then either reboot the whole master node or run the following commands to make changes effective:
  21. `supervisorctl restart nailgun`
  22. `ps -ef | grep naily`
  23. Check the naily* processed PIDs
  24. Kill "naily master" process
  25. Run `ps -ef | grep naily` one more time and check all the "naily*" processes have been restarted automatically (have new PIDs)
  26.  
  27. After that you may proceed with re-deploy.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement