-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''ve been trying out some configurations and been frustrated because they weren''t working how I would expect. After trying practically everything I could think of, I tried removing everything except the most basic elements to see what was going on. It turns out that my client is thinking that there is no configuration change, when there is. I make a change to one of my components, I stop puppetmasterd and then start it up again, it looks normal: puppetmasterd --verbose info: Starting server for Puppet version 0.22.2 info: Parsed manifest in 0.27 seconds info: Listening on port 8140 notice: Starting Puppet server version 0.22.2 info: Found tern in /etc/puppet/manifests/site.pp notice: Compiled configuration for tern.riseup.net in 1.42 seconds I stop and start the client, it looks normal too: root@penguin:/# puppetd --verbose notice: Starting Puppet client version 0.22.2 info: Config is up to date notice: Starting configuration run notice: Finished configuration run in 7.75 seconds But hey --- the config is not up to date, there should be a new config compiled for this node! The only way I could get the new config to be pulled in was to remove every piece of puppet on the node, clean out the cert on the puppetmaster, reinstall the client, start it up, sign the cert, start the client and get this error: /usr/sbin/puppetd:349: undefined method `readcert'' for #<Puppet::Network::Client::Master:0xf79691a8> (NoMethodError) Then I remember that I read http://mail.madstop.com/pipermail/puppet-users/2007-March/001976.html and this is a known issue, and then start the client up again and it reads the new config file. All of this was with 0.22.2 on the client and the server, running with facter 1.3.7. I tried reverting the client and server to 0.22.1, with facter 1.3.5 but same results. Reverting to 0.20.1 and now everything works as I expect - I change something on the master and the client picks it up on the next run. Micah -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGHxxN9n4qXRzy1ioRAkMIAJ4lSnBmjZ/sgfyE0zHD41JPrZs+aQCeMB02 hxxIF4wCTKtcbS4FrUhlq3M=pzYC -----END PGP SIGNATURE-----
* Micah Anderson <micah@riseup.net> [070412 23:23]:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > But hey --- the config is not up to date, there should be a new config > compiled for this node! The only way I could get the new config to be > pulled in was to remove every piece of puppet on the node, clean out the > cert on the puppetmaster, reinstall the client, start it up, sign the > cert, start the client and get this error:I now know about puppetd --test, which resolves this. Micah
On Apr 16, 2007, at 11:00 AM, Micah Anderson wrote:> * Micah Anderson <micah@riseup.net> [070412 23:23]: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> But hey --- the config is not up to date, there should be a new >> config >> compiled for this node! The only way I could get the new config to be >> pulled in was to remove every piece of puppet on the node, clean >> out the >> cert on the puppetmaster, reinstall the client, start it up, sign the >> cert, start the client and get this error: > > I now know about puppetd --test, which resolves this.Note that --test uses --ignorecache, so you can just use this instead. Is there something funny about the time difference between the client and server? That could explain why you''re having this trouble. -- The great aim of education is not knowledge but action. -- Herbert Spencer --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
* Luke Kanies <luke@madstop.com> [070416 09:44]:> On Apr 16, 2007, at 11:00 AM, Micah Anderson wrote: > > > * Micah Anderson <micah@riseup.net> [070412 23:23]: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> But hey --- the config is not up to date, there should be a new > >> config > >> compiled for this node! The only way I could get the new config to be > >> pulled in was to remove every piece of puppet on the node, clean > >> out the > >> cert on the puppetmaster, reinstall the client, start it up, sign the > >> cert, start the client and get this error: > > > > I now know about puppetd --test, which resolves this. > > Note that --test uses --ignorecache, so you can just use this instead.Thanks, thats good to know.> Is there something funny about the time difference between the client > and server? That could explain why you''re having this trouble.Uff, ntp died and clock was skewed forwards by a significant amount. That explains it. Micah