Hi Puppet-Team, first thanks for this great configuration management tool ! My name is Matt and i am on creating a puppet plugin for openQRM. The basic framework is already existing and working well so far. Now, after having it working ok once i now ran into a problem that my puppet-clients do not get their configuration any more from the puppetmasterd. What i saw on the puppetmasterd logs is : .. Mar 19 11:52:54 demo puppetmasterd[27506]: Host puppetclient.juggle has a waiting certificate req uest .. Then i signed the certificate for this client and got : .. Mar 19 11:55:01 demo puppetmasterd[27506]: Allowing 192.168.88.148(192.168.88.148) untrusted acce ss to CA methods .. When restarting puppet on the client i got : .. Mar 19 11:54:56 puppetclient puppetd[2757]: Reopening log files Mar 19 11:54:59 puppetclient puppetd[2757]: Starting Puppet client version 0.22.1 Mar 19 11:54:59 puppetclient puppetd[2757]: Could not load cached configuration: undefined method `to_type'' for false:FalseClass .. I am running the puppetmasterd with --manifest .../site.pp and also noticed that when i change the site.pp config somehow this update does not get applied to the client. The client still (somehow) receives the cached config from the puppetmasterd. -> even when removing the node config from the site.pp and restarting the puppetmasterd the client still gets its previous, default configuration. Where does puppet keeps/caches its configuration on the server and/or client ? -> i tried to completely remove the puppet installation on the server and client and re-installed it from the scratch with the same symptoms. btw: using the latest puppet + facter sources. Maybe i am doing something wrong ? many thanks + have a great day, Matt -- www.openQRM.org - Keeps your Data-Center Up and Running
On Mar 19, 2007, at 7:13 AM, Matt Rechenburg wrote:> When restarting puppet on the client i got : > .. > Mar 19 11:54:56 puppetclient puppetd[2757]: Reopening log files > Mar 19 11:54:59 puppetclient puppetd[2757]: Starting Puppet client > version 0.22.1 > Mar 19 11:54:59 puppetclient puppetd[2757]: Could not load cached > configuration: undefined method > `to_type'' for false:FalseClassThis is a bug I caused last night but should be fixed now.> I am running the puppetmasterd with --manifest .../site.pp and also > noticed > that when i change the site.pp config somehow this update does not get > applied > to the client. The client still (somehow) receives the cached > config from > the puppetmasterd. > -> even when removing the node config from the site.pp and restarting > the puppetmasterd > the client still gets its previous, default configuration. > Where does puppet keeps/caches its configuration on the server and/or > client ?The server does not cache client configs, but the client caches them. The current release caches them in the config directory, but the next release will cache them in the state directory (usually /var/ puppet/state, but check ''puppetd --configprint statedir'' on your machine).> -> i tried to completely remove the puppet installation on the server > and client > and re-installed it from the scratch with the same symptoms. > > btw: using the latest puppet + facter sources.This is *probably* the problem. If you could try the current svn sources, I''d appreciate it. I think I committed something broken yesterday but it should be working now. -- A great many people think they are thinking when they are merely rearranging their prejudices. -- William James --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies wrote:> On Mar 19, 2007, at 7:13 AM, Matt Rechenburg wrote: > >> When restarting puppet on the client i got : >> .. >> Mar 19 11:54:56 puppetclient puppetd[2757]: Reopening log files >> Mar 19 11:54:59 puppetclient puppetd[2757]: Starting Puppet client >> version 0.22.1 >> Mar 19 11:54:59 puppetclient puppetd[2757]: Could not load cached >> configuration: undefined method >> `to_type'' for false:FalseClass >> > > This is a bug I caused last night but should be fixed now. >;) cool> >> I am running the puppetmasterd with --manifest .../site.pp and also >> noticed >> that when i change the site.pp config somehow this update does not get >> applied >> to the client. The client still (somehow) receives the cached >> config from >> the puppetmasterd. >> -> even when removing the node config from the site.pp and restarting >> the puppetmasterd >> the client still gets its previous, default configuration. >> Where does puppet keeps/caches its configuration on the server and/or >> client ? >> > > The server does not cache client configs, but the client caches > them. The current release caches them in the config directory, but > the next release will cache them in the state directory (usually /var/ > puppet/state, but check ''puppetd --configprint statedir'' on your > machine). >ok, will do> >> -> i tried to completely remove the puppet installation on the server >> and client >> and re-installed it from the scratch with the same symptoms. >> >> btw: using the latest puppet + facter sources. >> > > This is *probably* the problem. If you could try the current svn > sources, I''d appreciate it. I think I committed something broken > yesterday but it should be working now. >ok, on my todo, will let you know Thanks Luke ! have a great day, Matt> -- > A great many people think they are thinking when they are merely > rearranging their prejudices. -- William James > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users > >-- www.openQRM.org - Keeps your Data-Center Up and Running
Hi Luke, sorry for the late response. Just re-tested it here with the latest puppet 0.22.4 and it is working fine for me now :) many thanks + all the best, Matt Luke Kanies wrote:> On Mar 19, 2007, at 7:13 AM, Matt Rechenburg wrote: > >> When restarting puppet on the client i got : >> .. >> Mar 19 11:54:56 puppetclient puppetd[2757]: Reopening log files >> Mar 19 11:54:59 puppetclient puppetd[2757]: Starting Puppet client >> version 0.22.1 >> Mar 19 11:54:59 puppetclient puppetd[2757]: Could not load cached >> configuration: undefined method >> `to_type'' for false:FalseClass >> > > This is a bug I caused last night but should be fixed now. > > >> I am running the puppetmasterd with --manifest .../site.pp and also >> noticed >> that when i change the site.pp config somehow this update does not get >> applied >> to the client. The client still (somehow) receives the cached >> config from >> the puppetmasterd. >> -> even when removing the node config from the site.pp and restarting >> the puppetmasterd >> the client still gets its previous, default configuration. >> Where does puppet keeps/caches its configuration on the server and/or >> client ? >> > > The server does not cache client configs, but the client caches > them. The current release caches them in the config directory, but > the next release will cache them in the state directory (usually /var/ > puppet/state, but check ''puppetd --configprint statedir'' on your > machine). > > >> -> i tried to completely remove the puppet installation on the server >> and client >> and re-installed it from the scratch with the same symptoms. >> >> btw: using the latest puppet + facter sources. >> > > This is *probably* the problem. If you could try the current svn > sources, I''d appreciate it. I think I committed something broken > yesterday but it should be working now. > > -- > A great many people think they are thinking when they are merely > rearranging their prejudices. -- William James > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users > >-- www.openQRM.org - Keeps your Data-Center Up and Running Matt''s blog - http://mattinaction.blogspot.com/