[Puppet Users] Intermittent freeze on select when running standalone
I have a new Ubuntu LTS VM running a simple manifest directly with puppet apply. About one time in 5 strace reports that puppet is sat there waiting on a select operation with low cpu usage. I'm wondering if this implies it's somehow gone into agent/deamon mode. Also just wondering if this is a puppet or a ruby/OS/VM issue. And why I cannot find anyone else with the same issue. I cannot imagine it's the manifest. It does one file check and two notifies. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/6sOuZGKUncUJ. 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.
Re: [Puppet Users] Intermittent freeze on select when running standalone
So it looks (without an in depth comparison) to be this bug in the bug tracking tool. http://projects.puppetlabs.com/issues/13038 So maybe this is already solved. Just need to wait* for the 2.7.12 or later version of pupet to make it to the debian packages for Ubuntu then I should be able to test. *yes, I'm being lazy. Though it looks like it's quite a few versions behind, with current latest being 2.7.18, so maybe I'll have to install it the hard way, or work out how to install the previous package, or keep on with "kill -9" for now... sigh. On Thursday, July 26, 2012 10:46:00 PM UTC+1, Joe wrote: > > And why I cannot find anyone else with the same issue. >> > > This sounds very similar, if not the same issue, that I have run into many > times before. > > It happens during a simple "puppet apply". I always run apply with > --verbose, and since there is no output at all, I figure the command has > just hung. > > Similarly, running strace on the process results in an infinite output of > select. > > ctrl-c does not kill the process - I have to kill the PID from another > terminal. > > I cannot reproduce this issue at will -- it seems to happen randomly. > > Thanks, > Joe > > -- > Joe Topjian > Systems Administrator > Cybera Inc. > > www.cybera.ca > > Cybera is a not-for-profit organization that works to spur and support > innovation, for the economic benefit of Alberta, through the use > of cyberinfrastructure. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/LeFn_U-RFkEJ. 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.
Re: [Puppet Users] Intermittent freeze on select when running standalone
Well working round the issue turned out to be quite painless really. To use the latest release: *wget http://apt.puppetlabs.com/puppetlabs-release-precise.deb sudo dpkg -i puppetlabs-release-precise.deb sudo apt-get update sudo apt-get install puppet* With similar for the puppet master node too. *wget http://apt.puppetlabs.com/puppetlabs-release-precise.deb sudo dpkg -i puppetlabs-release-precise.deb sudo apt-get update sudo apt-get install puppetmaster* David. On 30 July 2012 01:17, Joe Topjian wrote: > Hi Christopher, > > >> I didn't have any difficulty replacing the version in Ubuntu 10.04 with >> the version in Debian Squeeze. (Albeit that I rebuilt the package from the >> source deb.) It helped me get "puppet kick" going everywhere. > > > Right. I did not mean that it's difficult to replace the stock package. > I'm more frustrated at the extra step needed to upgrade the stock package > given that 12.04 is the latest version of Ubuntu + it's an LTS release. > > This means that administrators will either have a special step to upgrade > the stock version of puppet (and then maintain that non-stock version from > there on out) or will have to put up with the bug mentioned in this thread > as well as miss out on built-in puppet module support. > > All of which would not be necessary if 12.04 just shipped with 2.7.12+. > > The comment was more whining on my part. > > Thanks, > Joe > > -- > Joe Topjian > Systems Administrator > Cybera Inc. > > www.cybera.ca > > Cybera is a not-for-profit organization that works to spur and support > innovation, for the economic benefit of Alberta, through the use > of cyberinfrastructure. > > -- > 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. > -- 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.
