Sorry for the noise, it's issue #4602. Looks like the solution is to re-create the storeconfig DB or at least truncate the tables.
Thanks, Andrew On Sep 24, 10:21 am, Andrew Forgue <[email protected]> wrote: > Hello, > > I am testing out 2.6.1 since 2.6.0 seemed to have a ton of problems > (as any .0 release does I suppose). I am recieving the following > error on my client and server. The client is 0.25.5 and server is > 2.6.1: > > Client Side: > > /usr/local/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in > `deserialize' > /usr/local/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in > `find' > /usr/local/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb: > 202:in `find' > /usr/local/lib/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find' > /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:208:in > `retrieve_new_catalog' > /usr/local/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark' > /usr/local/lib/ruby/1.8/benchmark.rb:308:in `realtime' > /usr/local/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark' > /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:207:in > `retrieve_new_catalog' > /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:104:in > `retrieve_catalog' > /usr/local/lib/ruby/site_ruby/1.8/puppet/configurer.rb:142:in `run' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > /usr/local/lib/ruby/1.8/sync.rb:229:in `synchronize' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client' > /usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in > `onetime' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in > `run_command' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in > `exit_on_fail' > /usr/local/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > /usr/local/sbin/puppetd:160 > err: Could not retrieve catalog from remote server: Error 400 on > SERVER: wrong argument type String (expected Data) > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > Server side output: > > ... > notice: Compiled catalog for server.domain.com in environment > production in 5.56 seconds > ... > Followed by:http://pastebin.com/1Axnbtm6 > > So it appears the catalog is being compiled just fine, but I guess it > doesn't sent it to the client properly? > > Should I open a bug on the tracker or is there a known fix for this? > I didn't see anything in redmine nor with a google search. > > Thanks, > > Andrew -- 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.
