FAQ
This is driving me mad.
I get this error on two OpenSuse 12.3 nodes
puppet-3.0.2-2.9.1.x86_64
facter-1.6.17-2.1.1.x86_64

I ran this command:
*sudo puppet agent -t --verbose --noop --debug --trace *

*and I get this ouput:*
Info: Retrieving plugin
Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using
pson
Debug: Finishing transaction 19305160
Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in
/var/lib/puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.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/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson
Info: Caching catalog for svteustst02.hco.hc.hctx.net
Debug: Creating default schedules
Debug: Loaded state in 0.00 seconds
Info: Applying configuration version '1395341101'
Debug: /Schedule[daily]: Skipping device resources because running on a host
Debug: /Schedule[monthly]: Skipping device resources because running on a
host
Debug: /Schedule[hourly]: Skipping device resources because running on a
host
Debug: /Schedule[never]: Skipping device resources because running on a host
Debug: /Schedule[weekly]: Skipping device resources because running on a
host
Debug: /Schedule[puppet]: Skipping device resources because running on a
host
Debug: Finishing transaction 18621940
Debug: Storing state
Debug: Stored state in 0.02 seconds
Notice: Finished catalog run in 0.09 seconds
Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
*Error: Could not send report: Error 400 on SERVER: Could not intern from
pson: undefined method `intern' for nil:NilClass*
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/indirector/rest.rb:177:in
`is_http_200?'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/indirector/rest.rb:145:in `save'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/indirector/indirection.rb:266:in
`save'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/configurer.rb:200:in `send_report'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/configurer.rb:194:in `run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:45:in `block (5 levels)
in run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent/locker.rb:20:in `lock'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:45:in `block (4 levels)
in run'
/usr/lib64/ruby/1.9.1/sync.rb:227:in `sync_synchronize'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:45:in `block (3 levels)
in run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:119:in `with_client'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:42:in `block (2 levels)
in run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:84:in `run_in_fork'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:41:in `block in run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:175:in `call'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:175:in
`controlled_run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:39:in `run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application/agent.rb:338:in
`onetime'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application/agent.rb:312:in
`run_command'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:346:in `block (2
levels) in run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:438:in `plugin_hook'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:346:in `block in
run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/util.rb:496:in `exit_on_fail'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:346:in `run'
/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/util/command_line.rb:87:in
`execute'
/usr/bin/puppet:4:in `<main>'


I'm sure its on the server, but I'm not exactly sure where to look because
i get the same error in the server logs. I checked the firewall and it goes
through, I don't know enough arout ruby to hunt down a pson error, but what
what it looks like there is a syntax error somewhere? Anyone have any ideas?

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/05afc712-5d1a-4c04-aa31-1670be3a0fe5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • Race Boyer at Mar 27, 2014 at 9:03 pm
    I have found the issue, its with the stdlib module both version 3.2.1 and
    4.x with puppet 2.6.18 and facter 1.5.2.1 on SLES 11.x. I tried both
    versions and removed them both and got normal function back to puppet 3.4.3
    after they were removed. Only took 3 days of troubleshooting.... but the
    good part is that I was able to fully setup a functioning puppet-dashboard!
    (because I thought it was a foreman 1.4 issue)
    SLES can be such a pain the buttocks.
    On Friday, March 21, 2014 1:21:09 PM UTC-5, Race Boyer wrote:

    This is driving me mad.
    I get this error on two OpenSuse 12.3 nodes
    puppet-3.0.2-2.9.1.x86_64
    facter-1.6.17-2.1.1.x86_64

    I ran this command:
    *sudo puppet agent -t --verbose --noop --debug --trace *

    *and I get this ouput:*
    Info: Retrieving plugin
    Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using
    pson
    Debug: Finishing transaction 19305160
    Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
    Info: Loading facts in
    /var/lib/puppet/lib/facter/iptables_persistent_version.rb
    Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.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/puppet_vardir.rb
    Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
    Debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using
    pson
    Info: Caching catalog for svteustst02.hco.hc.hctx.net
    Debug: Creating default schedules
    Debug: Loaded state in 0.00 seconds
    Info: Applying configuration version '1395341101'
    Debug: /Schedule[daily]: Skipping device resources because running on a
    host
    Debug: /Schedule[monthly]: Skipping device resources because running on a
    host
    Debug: /Schedule[hourly]: Skipping device resources because running on a
    host
    Debug: /Schedule[never]: Skipping device resources because running on a
    host
    Debug: /Schedule[weekly]: Skipping device resources because running on a
    host
    Debug: /Schedule[puppet]: Skipping device resources because running on a
    host
    Debug: Finishing transaction 18621940
    Debug: Storing state
    Debug: Stored state in 0.02 seconds
    Notice: Finished catalog run in 0.09 seconds
    Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
    Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
    Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson
    *Error: Could not send report: Error 400 on SERVER: Could not intern from
    pson: undefined method `intern' for nil:NilClass*
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/indirector/rest.rb:177:in
    `is_http_200?'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/indirector/rest.rb:145:in `save'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/indirector/indirection.rb:266:in
    `save'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/configurer.rb:200:in `send_report'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/configurer.rb:194:in `run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:45:in `block (5 levels)
    in run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent/locker.rb:20:in `lock'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:45:in `block (4 levels)
    in run'
    /usr/lib64/ruby/1.9.1/sync.rb:227:in `sync_synchronize'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:45:in `block (3 levels)
    in run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:119:in `with_client'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:42:in `block (2 levels)
    in run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:84:in `run_in_fork'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:41:in `block in run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:175:in `call'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:175:in
    `controlled_run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/agent.rb:39:in `run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application/agent.rb:338:in
    `onetime'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application/agent.rb:312:in
    `run_command'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:346:in `block (2
    levels) in run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:438:in
    `plugin_hook'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:346:in `block in
    run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/util.rb:496:in `exit_on_fail'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/application.rb:346:in `run'
    /usr/lib64/ruby/vendor_ruby/1.9.1/puppet/util/command_line.rb:87:in
    `execute'
    /usr/bin/puppet:4:in `<main>'


    I'm sure its on the server, but I'm not exactly sure where to look because
    i get the same error in the server logs. I checked the firewall and it goes
    through, I don't know enough arout ruby to hunt down a pson error, but what
    what it looks like there is a syntax error somewhere? Anyone have any ideas?
    --
    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+unsubscribe@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/936e6be5-0f0a-4a98-b206-f15204195bab%40googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppuppet-users @
categoriespuppet
postedMar 21, '14 at 6:21p
activeMar 27, '14 at 9:03p
posts2
users1
websitepuppetlabs.com

1 user in discussion

Race Boyer: 2 posts

People

Translate

site design / logo © 2022 Grokbase