On Mon, Apr 22, 2013 at 2:48 AM, Przemek <p.slodkiew...@gmail.com> wrote:
> Hi, > > I'm rookie puppet user and I trying to establish simple Server-Client > connection on configuration: > Server: *Fedora F18*, Puppet 3.1.1 (installed by yum), Ruby 1.8.7 > Client: *Debian 6.0.6*, Puppet 3.1.1 (installed by > guide<http://shapeshed.com/setting-up-puppet-on-ubuntu-10-04/>), > Ruby 1.8.7 > > Server sign client certificate with success but now I'm struggle with > apply simple puppet manifest site.pp. > When I run Server and Client with no--daemonize and --debug I get error > stack trace as fallow: > > Debug: Finishing transaction -615376128 > Debug: Loaded state in 0.00 seconds > Debug: node supports formats: b64_zlib_yaml pson raw yaml; using pson > Debug: Using cached certificate for ca > Debug: Using cached certificate for radkam > Debug: Using cached certificate_revocation_list for ca > Info: Retrieving plugin > Debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using > pson > Debug: Finishing transaction -615481918 > The interpreter parameter to 'setcode' is deprecated and will be removed > in a future version. > *Error: Could not retrieve local facts: undefined method `get_uptime' for > Facter::Util::Uptime:Module > Error: Failed to apply catalog: Could not retrieve local facts: undefined > method `get_uptime' for Facter::Util::Uptime:Module* > This sort of error almost always means you have multiple versions of facter installed, either as a gem, package, or from source (install.rb). > > Debug: Value of 'preferred_serialization_format' (pson) is invalid for > report, using default (yaml) > *Debug: report supports formats: b64_zlib_yaml raw yaml; using yaml > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/agent.rb:89:in `exit': > no implicit conversion from nil to integer (TypeError)* > *from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/agent.rb:89:in > `run_in_fork' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/agent.rb:86:in > `fork' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/agent.rb:86:in > `run_in_fork' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/agent.rb:41:in > `run' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application.rb:179:in > `call' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application.rb:179:in > `controlled_run' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/agent.rb:39:in > `run' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/daemon.rb:205:in > `run_event_loop' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/daemon.rb:167:in > `loop' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/daemon.rb:167:in > `run_event_loop' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/daemon.rb:145:in > `start' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application/agent.rb:357:in > `main' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application/agent.rb:313:in > `run_command' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application.rb:364:in > `run' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application.rb:456:in > `plugin_hook' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application.rb:364:in > `run' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/util.rb:504:in > `exit_on_fail' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/application.rb:364:in > `run' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/util/command_line.rb:132:in > `run' > from > /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/lib/puppet/util/command_line.rb:86:in > `execute' > from /usr/lib/ruby/gems/1.8/gems/puppet-3.1.1/bin/puppet:4 > from /usr/bin/puppet:23:in `load' > from /usr/bin/puppet:23* > * > * > I googled it but I couldn't find fix (except few info on this stackoverflow > topic<http://stackoverflow.com/questions/3798107/undefined-method-get-uptime-for-facterutiluptimemodule-nomethoderror>). > * > * > > Could you please help me with resolution? > Best Regards > > -- > 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 post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Josh Cooper Developer, Puppet Labs *Join us at PuppetConf 2013, August 22-23 in San Francisco - * http://bit.ly/pupconf13* **The first 150 tickets sold will be available at a 35% discount - register now! Offer expires April 22.* -- 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 post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
