Re: [Puppet Users] Re: missing msgpack gem following puppet 3.4.0 upgrade
Thanks for the confirmation Adrien, and for the tip on the puppet master
compile command. I don't do much administration so I'm not terribly
familiar with some of those common commands. I've got some more questions
you or others might be able to shed light on, but they're well beyond the
scope of my original question so I'll post a new thread.
Thanks!
On Monday, December 23, 2013 2:12:57 PM UTC-5, Adrien Thebo wrote:
>
> Puppet 3.4.0 adds experimental support for the msgpack protocol (
> http://docs.puppetlabs.com/puppet/3/reference/experiments_msgpack.html),
> but doesn't depend on it being present. To enable it you need to install
> the msgpack gem and set the preferred serialization format, so unless
> you're explicitly enabling it then it shouldn't be a concern. Since it's
> only experimental we aren't planning on moving to it in the near future,
> but it's available so that people can try it for themselves.
>
> With respect to your puppet runs being empty, you'll probably want to
> ensure that the puppet master is generating the catalogs that you expected.
> You can do `puppet master --compile nodename` to directly generate a
> catalog; if that returns an empty catalog then it is probably an issue with
> how the master is configured.
>
>
> On Mon, Dec 23, 2013 at 9:54 AM, Luke Alford
> > wrote:
>
>> Upon downgrading to 3.3.2-1 the problem still remains, so it does appear
>> that the missing msgpack gem is a red herring that is not the cause of my
>> problem. I'd still be interested in thoughts on that debug statement
>> though, particularly if we choose to move to the improved serialization in
>> the future.
>>
>>
>> On Monday, December 23, 2013 12:44:59 PM UTC-5, Luke Alford wrote:
>>>
>>> Hello all,
>>>
>>> Our puppet master and agents recently updated to 3.4.0 and all of our
>>> puppet runs are now compiling the catalog and promptly exiting happily
>>> without actually doing anything. There isn't anything unusual about what I
>>> see in the log output aside from a debug message about missing the msgpack
>>> gem. We are not attempting to use the new serialization at this time and no
>>> configurations have changed other than the package upgrade, but nonetheless
>>> puppet seems displeased about not having the library. Has anyone else
>>> encountered this? Is there something besides the package upgrade that is
>>> required for this to work?
>>>
>>> OS: CentOS 6.4
>>> Puppet: 3.4.0-1
>>>
>>> puppet.noarch 3.4.0-1.el6
>>> @PuppetLabs
>>> puppet-server.noarch 3.4.0-1.el6
>>> @PuppetLabs
>>>
>>> Some log output from an agent noop run, I am not 100% certain this is
>>> causing the problem since the missing gem is only logged at the debug
>>> level, but I'm only going off of nothing else seeming out of the ordinary.
>>> I appreciate any thoughts on the matter, in the meantime I'll trying going
>>> back to 3.3.2-1 and see if that restores proper function. Our normal runs
>>> take many minutes as puppet does quite a bit for us, but it now bows out
>>> awfully quick.
>>>
>>> ...
>>> Debug: Using settings: adding file resource 'resourcefile':
>>> 'File[/var/lib/puppet/state/resources.txt]{:loglevel=>:debug,
>>> :links=>:follow, :owner=>"root", :backup=>false, :mode=>"640",
>>> :ensure=>:file, :path=>"/var/lib/puppet/state/resources.txt"}'
>>> Debug: Using settings: adding file resource 'clientyamldir':
>>> 'File[/var/lib/puppet/client_yaml]{:loglevel=>:debug, :links=>:follow,
>>> :backup=>false, :mode=>"750", :ensure=>:directory, :path=>"/var/lib/puppet/
>>> client_yaml"}'
>>> Debug: Using settings: adding file resource 'classfile':
>>> 'File[/var/lib/puppet/classes.txt]{:loglevel=>:debug, :links=>:follow,
>>> :owner=>"root", :backup=>false, :mode=>"640", :ensure=>:file,
>>> :path=>"/var/lib/puppet/classes.txt"}'
>>> Debug: Using settings: adding file resource 'lastrunreport':
>>> 'File[/var/lib/puppet/state/last_run_report.yaml]{:loglevel=>:debug,
>>> :links=>:follow, :backup=>false, :mode=>"640", :ensure=>:file,
>>> :path=>"/var/lib/puppet/state/last_run_report.yaml"}'
>>> Debug: Using settings: adding file resource 'clientbucketdir':
>>> 'File[/var/lib/puppet/clientbucket]{:loglevel=>:debug, :links=>:follow,
>>> :backup=>false, :mode=>"750", :ensure=>:directory, :path=>"/var/lib/puppet/
>>> clientbucket"}'
>>> Debug: Using settings: adding file resource 'graphdir':
>>> 'File[/var/lib/puppet/state/graphs]{:loglevel=>:debug, :links=>:follow,
>>> :backup=>false, :ensure=>:directory, :path=>"/var/lib/puppet/state/
>>> graphs"}'
>>> Debug: Using settings: adding file resource 'statefile':
>>> 'File[/var/lib/puppet/state/state.yaml]{:loglevel=>:debug,
>>> :links=>:follow, :backup=>false, :mode=>"660", :ensure=>:file,
>>> :path=>"/var/lib/puppet/state/state.yaml"}'
>>> Debug: Using settings: adding file resource 'client_datadir':
>>> 'File[/var/lib/puppet/client_data]{:loglevel=>:
Re: [Puppet Users] Re: missing msgpack gem following puppet 3.4.0 upgrade
Puppet 3.4.0 adds experimental support for the msgpack protocol (
http://docs.puppetlabs.com/puppet/3/reference/experiments_msgpack.html),
but doesn't depend on it being present. To enable it you need to install
the msgpack gem and set the preferred serialization format, so unless
you're explicitly enabling it then it shouldn't be a concern. Since it's
only experimental we aren't planning on moving to it in the near future,
but it's available so that people can try it for themselves.
With respect to your puppet runs being empty, you'll probably want to
ensure that the puppet master is generating the catalogs that you expected.
You can do `puppet master --compile nodename` to directly generate a
catalog; if that returns an empty catalog then it is probably an issue with
how the master is configured.
On Mon, Dec 23, 2013 at 9:54 AM, Luke Alford wrote:
> Upon downgrading to 3.3.2-1 the problem still remains, so it does appear
> that the missing msgpack gem is a red herring that is not the cause of my
> problem. I'd still be interested in thoughts on that debug statement
> though, particularly if we choose to move to the improved serialization in
> the future.
>
>
> On Monday, December 23, 2013 12:44:59 PM UTC-5, Luke Alford wrote:
>>
>> Hello all,
>>
>> Our puppet master and agents recently updated to 3.4.0 and all of our
>> puppet runs are now compiling the catalog and promptly exiting happily
>> without actually doing anything. There isn't anything unusual about what I
>> see in the log output aside from a debug message about missing the msgpack
>> gem. We are not attempting to use the new serialization at this time and no
>> configurations have changed other than the package upgrade, but nonetheless
>> puppet seems displeased about not having the library. Has anyone else
>> encountered this? Is there something besides the package upgrade that is
>> required for this to work?
>>
>> OS: CentOS 6.4
>> Puppet: 3.4.0-1
>>
>> puppet.noarch 3.4.0-1.el6
>> @PuppetLabs
>> puppet-server.noarch 3.4.0-1.el6
>> @PuppetLabs
>>
>> Some log output from an agent noop run, I am not 100% certain this is
>> causing the problem since the missing gem is only logged at the debug
>> level, but I'm only going off of nothing else seeming out of the ordinary.
>> I appreciate any thoughts on the matter, in the meantime I'll trying going
>> back to 3.3.2-1 and see if that restores proper function. Our normal runs
>> take many minutes as puppet does quite a bit for us, but it now bows out
>> awfully quick.
>>
>> ...
>> Debug: Using settings: adding file resource 'resourcefile':
>> 'File[/var/lib/puppet/state/resources.txt]{:loglevel=>:debug,
>> :links=>:follow, :owner=>"root", :backup=>false, :mode=>"640",
>> :ensure=>:file, :path=>"/var/lib/puppet/state/resources.txt"}'
>> Debug: Using settings: adding file resource 'clientyamldir':
>> 'File[/var/lib/puppet/client_yaml]{:loglevel=>:debug, :links=>:follow,
>> :backup=>false, :mode=>"750", :ensure=>:directory, :path=>"/var/lib/puppet/
>> client_yaml"}'
>> Debug: Using settings: adding file resource 'classfile':
>> 'File[/var/lib/puppet/classes.txt]{:loglevel=>:debug, :links=>:follow,
>> :owner=>"root", :backup=>false, :mode=>"640", :ensure=>:file,
>> :path=>"/var/lib/puppet/classes.txt"}'
>> Debug: Using settings: adding file resource 'lastrunreport':
>> 'File[/var/lib/puppet/state/last_run_report.yaml]{:loglevel=>:debug,
>> :links=>:follow, :backup=>false, :mode=>"640", :ensure=>:file,
>> :path=>"/var/lib/puppet/state/last_run_report.yaml"}'
>> Debug: Using settings: adding file resource 'clientbucketdir':
>> 'File[/var/lib/puppet/clientbucket]{:loglevel=>:debug, :links=>:follow,
>> :backup=>false, :mode=>"750", :ensure=>:directory, :path=>"/var/lib/puppet/
>> clientbucket"}'
>> Debug: Using settings: adding file resource 'graphdir':
>> 'File[/var/lib/puppet/state/graphs]{:loglevel=>:debug, :links=>:follow,
>> :backup=>false, :ensure=>:directory, :path=>"/var/lib/puppet/state/
>> graphs"}'
>> Debug: Using settings: adding file resource 'statefile':
>> 'File[/var/lib/puppet/state/state.yaml]{:loglevel=>:debug,
>> :links=>:follow, :backup=>false, :mode=>"660", :ensure=>:file,
>> :path=>"/var/lib/puppet/state/state.yaml"}'
>> Debug: Using settings: adding file resource 'client_datadir':
>> 'File[/var/lib/puppet/client_data]{:loglevel=>:debug, :links=>:follow,
>> :backup=>false, :mode=>"750", :ensure=>:directory, :path=>"/var/lib/puppet/
>> client_data"}'
>> Debug: Using settings: adding file resource 'lastrunfile':
>> 'File[/var/lib/puppet/state/last_run_summary.yaml]{:loglevel=>:debug,
>> :links=>:follow, :backup=>false, :mode=>"644", :ensure=>:file,
>> :path=>"/var/lib/puppet/state/last_run_summary.yaml"}'
>> Debug: Finishing transaction 70160328710680
>> Debug: Loaded state in 0.06 seconds
>> *Debug: Failed to load library 'msgpack' for feature 'msgpack'*
>> Debug: node supports formats: pson b64_zlib_yaml yaml raw
>> Debug: Using cache
[Puppet Users] Re: missing msgpack gem following puppet 3.4.0 upgrade
Upon downgrading to 3.3.2-1 the problem still remains, so it does appear
that the missing msgpack gem is a red herring that is not the cause of my
problem. I'd still be interested in thoughts on that debug statement
though, particularly if we choose to move to the improved serialization in
the future.
On Monday, December 23, 2013 12:44:59 PM UTC-5, Luke Alford wrote:
>
> Hello all,
>
> Our puppet master and agents recently updated to 3.4.0 and all of our
> puppet runs are now compiling the catalog and promptly exiting happily
> without actually doing anything. There isn't anything unusual about what I
> see in the log output aside from a debug message about missing the msgpack
> gem. We are not attempting to use the new serialization at this time and no
> configurations have changed other than the package upgrade, but nonetheless
> puppet seems displeased about not having the library. Has anyone else
> encountered this? Is there something besides the package upgrade that is
> required for this to work?
>
> OS: CentOS 6.4
> Puppet: 3.4.0-1
>
> puppet.noarch 3.4.0-1.el6
> @PuppetLabs
> puppet-server.noarch 3.4.0-1.el6
> @PuppetLabs
>
> Some log output from an agent noop run, I am not 100% certain this is
> causing the problem since the missing gem is only logged at the debug
> level, but I'm only going off of nothing else seeming out of the ordinary.
> I appreciate any thoughts on the matter, in the meantime I'll trying going
> back to 3.3.2-1 and see if that restores proper function. Our normal runs
> take many minutes as puppet does quite a bit for us, but it now bows out
> awfully quick.
>
> ...
> Debug: Using settings: adding file resource 'resourcefile':
> 'File[/var/lib/puppet/state/resources.txt]{:loglevel=>:debug,
> :links=>:follow, :owner=>"root", :backup=>false, :mode=>"640",
> :ensure=>:file, :path=>"/var/lib/puppet/state/resources.txt"}'
> Debug: Using settings: adding file resource 'clientyamldir':
> 'File[/var/lib/puppet/client_yaml]{:loglevel=>:debug, :links=>:follow,
> :backup=>false, :mode=>"750", :ensure=>:directory,
> :path=>"/var/lib/puppet/client_yaml"}'
> Debug: Using settings: adding file resource 'classfile':
> 'File[/var/lib/puppet/classes.txt]{:loglevel=>:debug, :links=>:follow,
> :owner=>"root", :backup=>false, :mode=>"640", :ensure=>:file,
> :path=>"/var/lib/puppet/classes.txt"}'
> Debug: Using settings: adding file resource 'lastrunreport':
> 'File[/var/lib/puppet/state/last_run_report.yaml]{:loglevel=>:debug,
> :links=>:follow, :backup=>false, :mode=>"640", :ensure=>:file,
> :path=>"/var/lib/puppet/state/last_run_report.yaml"}'
> Debug: Using settings: adding file resource 'clientbucketdir':
> 'File[/var/lib/puppet/clientbucket]{:loglevel=>:debug, :links=>:follow,
> :backup=>false, :mode=>"750", :ensure=>:directory,
> :path=>"/var/lib/puppet/clientbucket"}'
> Debug: Using settings: adding file resource 'graphdir':
> 'File[/var/lib/puppet/state/graphs]{:loglevel=>:debug, :links=>:follow,
> :backup=>false, :ensure=>:directory, :path=>"/var/lib/puppet/state/graphs"}'
> Debug: Using settings: adding file resource 'statefile':
> 'File[/var/lib/puppet/state/state.yaml]{:loglevel=>:debug, :links=>:follow,
> :backup=>false, :mode=>"660", :ensure=>:file,
> :path=>"/var/lib/puppet/state/state.yaml"}'
> Debug: Using settings: adding file resource 'client_datadir':
> 'File[/var/lib/puppet/client_data]{:loglevel=>:debug, :links=>:follow,
> :backup=>false, :mode=>"750", :ensure=>:directory,
> :path=>"/var/lib/puppet/client_data"}'
> Debug: Using settings: adding file resource 'lastrunfile':
> 'File[/var/lib/puppet/state/last_run_summary.yaml]{:loglevel=>:debug,
> :links=>:follow, :backup=>false, :mode=>"644", :ensure=>:file,
> :path=>"/var/lib/puppet/state/last_run_summary.yaml"}'
> Debug: Finishing transaction 70160328710680
> Debug: Loaded state in 0.06 seconds
> *Debug: Failed to load library 'msgpack' for feature 'msgpack'*
> Debug: node supports formats: pson b64_zlib_yaml yaml raw
> Debug: Using cached certificate for ca
> Debug: Using cached certificate for stack01.qa.tstllc.net
> Debug: Using cached certificate_revocation_list for ca
> Info: Retrieving plugin
> *Debug: Failed to load library 'msgpack' for feature 'msgpack'*
> Debug: file_metadata supports formats: pson b64_zlib_yaml yaml raw
> Debug: Finishing transaction 70160331731520
> Info: Loading facts in /var/lib/puppet/lib/facter/fqdn_int.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/domain_int.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/datacenter.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/environment.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
> Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
>
