ha! right you are... my yaml files were actually full of errors instead of yaml... looked like thread dumps or something. I removed them and it looks like all is well.
thanks! maybe I can get back to my weekend now. ;) On Oct 7, 2:33 am, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote: > On 10/07/2010 12:43 AM, Steve (steev) Neuharth wrote: > > > > > > > Anyone know what this is? It doesn't seem related to puppet but I'm stumped. > > > info: Loading facts in dmidecode > > info: Loading facts in cpuinfo > > debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml; using > > pson > > /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in `deserialize' > > /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in `find' > > /usr/lib64/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:202:in `find' > > /usr/lib64/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find' > > /usr/lib64/ruby/site_ruby/1.8/puppet/configurer.rb:208:in > > `retrieve_new_catalog' > > /usr/lib64/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark' > > /usr/lib64/ruby/1.8/benchmark.rb:308:in `realtime' > > /usr/lib64/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark' > > /usr/lib64/ruby/site_ruby/1.8/puppet/configurer.rb:207:in > > `retrieve_new_catalog' > > /usr/lib64/ruby/site_ruby/1.8/puppet/configurer.rb:104:in `retrieve_catalog' > > /usr/lib64/ruby/site_ruby/1.8/puppet/configurer.rb:142:in `run' > > /usr/lib64/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > > /usr/lib64/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock' > > /usr/lib64/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > > /usr/lib64/ruby/1.8/sync.rb:230:in `synchronize' > > /usr/lib64/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > > /usr/lib64/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client' > > /usr/lib64/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run' > > /usr/lib64/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in `onetime' > > /usr/lib64/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' > > /usr/lib64/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' > > /usr/lib64/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > > /usr/lib64/ruby/site_ruby/1.8/puppet/application.rb:306:in `exit_on_fail' > > /usr/lib64/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > > /usr/sbin/puppetd:160 > > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > > undefined method `name' for "\177ELF\002\001\001":String > > warning: Not using cache on failed catalog > > err: Could not retrieve catalog; skipping run > > > I've tried recompiling everything on the client side to no avail. Only a > > few clients exhibit this behavior. I'm running 0.25.5 on both client and > > server. > > Hi, > > seeing as the puppetmaster spits the error, you should rather look at > the master log. > > As only some clients are afflicted, could this be caused by their > specific manifests? > > FWIW, it looks as if puppet is loading a binary file at some point where > text is expected or something like that. > > HTH, > Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
