Hi Jason, On Mon, 2010-09-27 at 18:02 -0700, Jason Wright wrote: > On Fri, Sep 24, 2010 at 1:36 AM, Brice Figureau > <[email protected]> wrote: > > First, I'm very glad and pleased someone is using puppet-load :) > > The codebase is still very new and rough and any fix or new feature (or > > even comments/ideas) are welcome. > > Once I get it working, I'll be happy to provide a diff of my modifications.
Thanks! > > We fixed a bunch of concurrency issues (spotted with puppet-load) in > > 2.6. Any chance you can try with a 2.6.1 to see if you get the same > > issue? > > I tried 0.26.1 today and am still seeing 400s. > > > It would be interesting to run your master with --trace so that we can > > see where this error is generated (and possibly with --debug). > > Example log with --trace --debug --evaltrace, which unfortunately > doesn't seem to contain much new information: > > Sep 27 17:47:41 SERVER puppet-master[12434]: Handling request: GET > /monitoring/ca > talog/thiscert-isss-forr-thee-healthchecks?facts_format=b64_zlib_yaml&facts=eNqVjsENwjAMAP%252BZwgxg8fcAP > BErpImLA41dYrdSt4cRyvvupENEuIxtOq42%250AvbgEPbZ15SC6W2WiWy7hkDR3JghpXngENnfH2cbAEGYUzktIES5vT3teNnaC%250A > BDB%252Fqp6sAKr13M7rrHsbpp01CLppCxtNnz8i5vHH7xcaHVz%252B%250A > Sep 27 17:47:41 SERVER puppet-master[12434]: Expiring the node cache > of thiscert- > isss-forr-thee-healthchecks > Sep 27 17:47:41 SERVER puppet-master[12434]: Using cached node for > thiscert-isss- > forr-thee-healthchecks > Sep 27 17:47:41 SERVER puppet-master[12434]: Could not find class base > for thiscert-isss-forr-thee-healthchecks This looks different from the previous error you had. Are you still using your external node tool and 0.25.4/5? > Sep 27 17:47:41 SERVER puppet-master[12434]: Compiled catalog for > thiscert-isss-forr-thee-healthchecks in environment production in 0.06 > seconds Hmm, apparently your master is not running in debug mode, nor in trace mode. Can you check? You should have a long stacktrace for the 400 error in the master log (wherever it is when running with passenger). > For the run that produced the log above I used concurrency 25 and > repeat 100, producing 33 400 errors. > > >> Sep 14 11:44:24 [SERVER] puppetmasterd[432]: Cached node for > >> thiscert-isss-forr-thee-healthchecks failed: Could not parse YAML data > >> for node thiscert-isss-forr-thee-healthchecks: syntax error on line > >> 10, col 2: ` domain: thiscert-isss-forr-thee-healthchecks' > > > > If I understand correctly, are you saying that this error is not present > > with a master running 0.25.5? > > If yes, then I'm not surprised since we stopped using the ruby lib YAML > > extension in favor of a pure ruby internal one (ZAML) in 0.25.5, which > > IMHO is way better :) > > Correct. I haven't seen it with 0.26.1 either. > > > Will you be at puppetcamp? > > Maybe we can discuss/debug this lively there? > > I'm actually going to be presenting at puppetcamp on our load > balancing rollout and how we monitor the service. I'm also hoping to > include some performance results, if I can get puppet-load working. Puppet-load is not the culprit here, it is working fine :) It just exercises the puppetmaster a little bit too much for it. Certainly due to a threading issue somewhere (which might well be outside of the master (ie rack/passenger or maybe even your external node tool). Anyway, I'd be happy to discuss puppet-load future with anyone at Puppetcamp :) -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
