On Jun 8, 2009, at 4:39 PM, Pete Emerson wrote:
> I'm using puppet 0.24.7-4. I have a situation where I have some very
> long running puppet runs in order to do upgrades (removing
> applications from load balancers gracefully, et cetera).
>
> My puppet runs triggered via puppetrun are finishing successfully:
>
> Jun 8 20:31:29 puppetd[10178]: Finished catalog run in 345.18 seconds
>
> Puppetrun itself is timing out:
>
> err: Connection timeout calling puppetrunner.run: execution expired
> Host myhost failed: Connection Timeout
> myhost finished with exit code 2
>
> I'm calling puppetrun with --foreground: puppetrun --host=myhost --
> host=myhost2 --host=myhost3 --foreground --parallel
>
> However, I don't see anything in the puppetrun doco that hints at
> setting the execution exiry time. Any suggestions?
I'd run with --no-foreground. Or, modify puppetrun to have a timeout?
--
It's impossible to foresee the consequences of being clever.
-- Christopher Strachey
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
