On Friday, February 21, 2014 10:19:10 AM UTC-6, JonY wrote: > > > On Friday, February 21, 2014 8:10:23 AM UTC-8, jcbollinger wrote: >> >> >> >> On Thursday, February 20, 2014 4:41:33 PM UTC-6, JonY wrote: >>> >>> Looks like my server updated to 3.4.2. Since then I've started seeing >>> these occasional messages like: >>> >>> Feb 20 14:19:05 puppet-master[5626]: YAML in network requests is >>> deprecated and will be removed in a future version. See >>> http://links.puppetlabs.com/deprecate_yaml_on_network >>> Feb 20 14:19:05 puppet-master[5626]: (at >>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:304:in >>> `decode_params') >>> >>> Does this mean I'll be able to start using JSON or XML in my ENC >>> scripts? >>> >>> >> >> The master is complaining about YAML in the inbound request from an >> agent. You should stop seeing the message if you update the relevant >> agents to a sufficiently recent version. >> >> The message is not related to ENC output, but inasmuch as JSON is very >> nearly a subset of YAML, you should be able to have your ENC output JSON >> now, provided that you don't tickle one of the few inconsistencies. Not so >> much XML. >> >> >> John >> >> > > > All of my agents are running 3.4.0. (or so they are told to). Is there > some way to find out where this anomalous request is coming from? A $DEBUG > setting or equivalent? >
If the name of the agent being serviced is not already logged in the context of the message (look a few lines before), then you can probably get it to be logged by enabling debug logging in the master (--debug command-line option). John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/575138a0-44f0-4011-9e0f-fc3e0507ad12%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
