On Mon, Nov 1, 2010 at 11:19 PM, Micah Anderson <[email protected]> wrote: > > I just upgraded master and clients to 2.6.2, i'm on a passenger setup, > and I'm seeing some odd things with puppet runs. Sometimes runs are > relatively fast, and they say they finish, I see this printed out: > > notice: Finished catalog run in 81.08 seconds > > but, i'm not dropped back to the command prompt, it hangs here for a > long time, and then after some time I see: > > err: Could not run Puppet configuration client: execution expired > > What is happening at this stage that is failing?
I'd love to see more info on this. I was seeing this problem every so often but only when bootstrapping, and wasn't able to work out what the underlying problem was as it simply took too long to reproduce each time. > > I'm running passenger 2.2.11, libactiverecord-ruby1.8 2.3.5, > libactivesupport-ruby1.8 2.3.5 and storedconfigs on mysql. This wasn't > happening when I was running on 0.25.5. > > passenger-status tells me: > > ----------- General information ----------- > max = 6 > count = 6 > active = 6 > inactive = 0 > Waiting on global queue: 13 > > ----------- Domains ----------- > /usr/share/puppet/rack/puppetmasterd: > PID: 1988 Sessions: 1 Processed: 70 Uptime: 16m 14s > PID: 1934 Sessions: 1 Processed: 297 Uptime: 18m 22s > PID: 2951 Sessions: 1 Processed: 134 Uptime: 15m 55s > PID: 1801 Sessions: 1 Processed: 228 Uptime: 20m 25s > PID: 1788 Sessions: 1 Processed: 165 Uptime: 20m 32s > PID: 1818 Sessions: 1 Processed: 139 Uptime: 20m 18s > > > and I am seeing 6 spawned processes which are each eating 32% of the > cpu, running quite hard. > > I've run the client and the master in debug verbose mode to try and > track down anything interesting, but its not that revealing. This is > what I see: > > on master: > > ... > > debug: File[/etc/munin/plugin-conf.d/passenger_stats.conf]: Adding default > for ignore > notice: Compiled catalog for foo.bar in environment production in 206.49 > seconds > info: Caching catalog for foo.bar > info: Queued catalog for foo.bar in 44.29 seconds > info: Could not find filesystem info for file 'modules/apt/modules_dir' in > environment production > info: Could not find filesystem info for file > 'modules/munin/plugins/modules_dir' in environment production > info: Could not find filesystem info for file > 'modules/munin/nodes/modules_dir' in environment production > info: Could not find filesystem info for file 'modules/shorewall/modules_dir' > in environment production > info: Could not find filesystem info for file 'modules/virtual/modules_dir' > in environment production > info: Could not find filesystem info for file > 'modules/virtual/contexts/modules_dir' in environment production > > > on client: > > ... > > debug: Finishing transaction -622176998 > debug: Storing state > debug: Stored state in 1.68 seconds > notice: Finished catalog run in 93.40 seconds > debug: Using cached certificate for ca > debug: Using cached certificate for foo.bar > debug: Using cached certificate_revocation_list for ca > debug: Value of 'preferred_serialization_format' (pson) is invalid for > report, using default (b64_zlib_yaml) > debug: report supports formats: b64_zlib_yaml marshal raw yaml; using > b64_zlib_yaml > * long pause here * > > Any ideas of things I might look into? > > thanks! > micah > -- Nigel Kersten - Puppet Labs - http://www.puppetlabs.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
