similar to: Error dealing with type "File" and subscriptions

What''s this mean? root@gravity:/etc/puppet/manifests# puppetd -v --listen info: Starting handler for Runner info: Starting server for Puppet version 0.22.1 info: Listening on port 8139 notice: Starting Puppet client version 0.22.1 err: Could not run Puppet::Client::MasterClient: Host gravity.example.org not authorized to call puppetmaster.freshness Thanks, Kent -- "It may be true

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

xf86-input-libinput 0.24.0 is now available. A couple of new features were added this cycle: * tablets now support a configurable pressure curve * tablets now have a 'area ratio' setting to be able to match the tablet aspect ratio with that of the screen * the mouse wheel's click angle now (correctly) affects how fast the scroll wheel triggers. In particular, if you have a wheel

Hi all, Hobbeswalsh on IRC has discovered a backward compatibility issue in 0.24.0, preventing 0.23.x clients working well with 0.24.0 servers. Specifically, you can''t specify relationships to builtin resources when the client is 0.23.x, although specifying relationships to defined resources still works. The problem is that prior to 0.24.0 there was no central class

Hi, I was managing a bunch of Centos 4.5 with Puppet until the ruby security patch bit me creating ssl problems. As I''m not able/willing to patch the installed version I tried upgrading to dlutter''s 0.24.0-2.el5 version. Unfortunately this didn''t help much. So I removed the server and client installation completely (making sure to manually remove the config, ssl, ...

At long last, 0.24.0 has been released. Look for your friendly packagers to package it up in the near future, but in the meantime you can download it: http://reductivelabs.com/downloads/puppet/puppet-0.24.0.tgz I''ll be walking the different release sites (RubyForge et al) and posting it there, too. Look for a related announcement later today on changes in development practices

Hi, I''m getting a "Could not retrieve dependency" error and I can''t figure why. Someone got a cluestick for me? I''m using the following simplified configuration to ensure sshd is running and gets reloaded when the config file changes: ---- site.pp ---- import "classes/sshd.pp" node obsd42 { include ssh-server } node debian40 { include

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

I''ve now fixed all of the bugs I''m going to fix for 0.24.0/misspiggy. Please test that the current ''master'' branch in git works for you. I''ll probably release tomorrow, or maybe early on Thursday if I don''t hear of any show-stoppers. -- I don''t want any yes-men around me. I want everybody to tell me the truth even if it

Hi, I am having a problem where puppetd won''t start on one of my RHEL 5 machines with the --listen option enabled. 0.23.2 seems to run fine but 0.24.0 dies leaving the pid file still there. I installed puppet using the latest gem from reductive labs. It works fine on what is meant to be an identical system. I tried running strace and it seems to exit after trying to write to a bad

I created ticket 961 "puppetd create too many/not closing TCP connections". I''m wondering if anyone else is seeing this? Depending on the client configuration a typical puppetd run will cause hunderds of simultaneous TCP connections to be opened to the puppet master. I''m gettting over 300 established connections for a single client in some cases. If the number of

this time when I try to connect the first node: [root@qaagt20 ~]# /etc/init.d/puppet start Starting puppet: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize'': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/lib/ruby/1.8/net/http.rb:560:in `open'' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'' from

I''m seeing these in my logs on my puppetmaster: puppetmasterd[4111]: Could not store configs: SQLite3::SQLException: SQL logic error or missing database: DELETE FROM fact_values WHERE "id" = 8 currently this is 0.24.0 relect from some previously collected resource that wasn''t cleaned up? upgrade issue? nothing to worry about? that''s the only

This is particularly nasty, since it''s on the puppetmaster itself: [root@puppet tmp]# rpm -q yum puppet puppet-server yum-3.0.5-1.el5.centos.5 puppet-0.24.0-2.el5 puppet-server-0.24.0-2.el5 [root@puppet tmp]# cat /etc/issue CentOS release 5 (Final) Here''s the output of puppetd --debug: notice: Starting catalog run debug: Loaded state in 0.01 seconds debug: Prefetching rpm

so here I am trying to track down why one of my execs isn''t working properly and I notice in the wiki[1]the option on_failure for logoutput. Turns out it does''t work (in 0.23.0) err: Parameter logoutput failed: Invalid ''logoutput'' value "on_failure". Valid values are true, false, debug, info, notice, warning, err, alert, emerg, crit. err: Could not

Hi all, We''re getting close to release[1], so I''d appreciate it if people would start testing the current ''master'' branch with their repositories. I made quite a few internal changes, most of which shouldn''t even be noticed unless there are bugs, so just running a server and/or client under the current code would be a big help. I''m

Greetings, Shouldn''t puppetd -o --ignoreschedules ... imply that splay* options are ignored :-) If that''s not the intended behavior could we get a --run-now that ignores splay* and schedules? Cheers, Ryan

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all There is some discussion of doing a 0.23.3 release to backport a number of bugs fixes from 0.24.0. What do people think of this idea? Would you prefer a dot upgrade to 0.23.3 or are most planning to upgrade cleanly to 0.24.x? I understand from Luke that 0.24.1 will be released shortly and that 0.23.2 clients should cleanly connect and

Hi all, As promised, 0.24.1 is out. Here''s the changelog: Updated vim filetype detection. (#900 and #963) Default resources like schedules no longer conflict with managed resources. (#965) Removing the ability to disable http keep-alive, since it didn''t really work anyway and it should no longer be necessary. Refactored http keep-alive so

Puppeteers, One of the more ... interesting components of our configuration has been how we''re handling users. We don''t have an LDAP solution (yet), so we''re using Puppet to handle users. This isn''t overly complex, at least at first glance. We have three types of users. * System admins * Web developers * R&D developer The system admins have userids on all