OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its own puppetd.conf file. It seemed to re-parse it, but I then started getting bizarre errors about being unable to determine resource states: Oct 27 22:35:46 svn puppetd[79458]: (//basenode/puppet/File[/usr/local/etc/puppet]) Failed to retrieve current state of resource: can''t convert nil into String Oct 27 22:35:47 svn puppetd[79458]: (//basenode/puppet/File[/usr/local/etc/puppet/puppetd.conf]) Failed to ret rieve current state of resource: can''t convert nil into String Oct 27 22:35:47 svn puppetd[79458]: (//basenode/puppet/File[/var/puppet]) Failed to retrieve current state of resource: can''t convert nil into String Oct 27 22:35:47 svn puppetd[79458]: (//basenode/puppet/File[/usr/local/etc/puppet/namespaceauth.conf]) Failed to retrieve current state of resource: can''t convert nil into String All the mentioned files were present. There does seem to be some correlation between these errors and what I changed in puppetd.conf. Before, puppetd didn''t set confdir and vardir. The new puppetd.conf did set them to the above mentioned paths; however, these were the same paths that were being used before set on the command line. Restarting puppetd by hand cleared up the problem. I haven''t tried reproducing the problem. Having to login to all the servers "by hand" to restart puppetd sure wasn''t fun. I guess I''m getting spoiled already. -- Russell A. Jackson <raj@csub.edu> Network Analyst California State University, Bakersfield "Reflections on Ice-Breaking" Candy Is dandy But liquor Is quicker. -- Ogden Nash _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Russell Jackson wrote:> OS: FreeBSD 6.2-RELEASE > Puppet: 0.22.4 > > OS: CentOS 5.0 > Puppet: 0.23.2 > > Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, > and when puppetd attempted to restart itself (using the init provider), it failed to start > back up. Perhaps the init provider needs to close all file handles before executing the > rc.d scripts? > > Additionally, I had puppetd update its own puppetd.conf file. It seemed to re-parse it, > but I then started getting bizarre errors about being unable to determine resource states: > > Oct 27 22:35:46 svn puppetd[79458]: (//basenode/puppet/File[/usr/local/etc/puppet]) Failed > to retrieve current state of resource: can''t convert nil into String > Oct 27 22:35:47 svn puppetd[79458]: > (//basenode/puppet/File[/usr/local/etc/puppet/puppetd.conf]) Failed to ret > rieve current state of resource: can''t convert nil into String > Oct 27 22:35:47 svn puppetd[79458]: (//basenode/puppet/File[/var/puppet]) Failed to > retrieve current state of resource: can''t convert nil into String > Oct 27 22:35:47 svn puppetd[79458]: > (//basenode/puppet/File[/usr/local/etc/puppet/namespaceauth.conf]) Failed > to retrieve current state of resource: can''t convert nil into String > > All the mentioned files were present. There does seem to be some correlation between these > errors and what I changed in puppetd.conf. Before, puppetd didn''t set confdir and vardir. > The new puppetd.conf did set them to the above mentioned paths; however, these were the > same paths that were being used before set on the command line. > > Restarting puppetd by hand cleared up the problem. I haven''t tried reproducing the > problem. Having to login to all the servers "by hand" to restart puppetd sure wasn''t fun. > I guess I''m getting spoiled already. >I found a few bug reports with similar problems regarding puppet restarting itself with the init provider. There didn''t seem to be any solutions though. The problem with the configuration changing is only present in 0.22.4. I can''t reproduce it with 0.23.2. I guess I just need to hurry up and get all my nodes upgraded. -- Russell A. Jackson <raj@csub.edu> Network Analyst California State University, Bakersfield Always think of something new; this helps you forget your last rotten idea. -- Seth Frankel _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Oct 30, 2007, at 2:08 PM, Russell Jackson wrote:> I found a few bug reports with similar problems regarding puppet > restarting itself with > the init provider. There didn''t seem to be any solutions though.Yeah, there appear to be a couple of issues with it. I''m trying.> The problem with the configuration changing is only present in > 0.22.4. I can''t reproduce > it with 0.23.2. I guess I just need to hurry up and get all my > nodes upgraded.That''s good to hear. -- The great thing about television is that if something important happens anywhere in the world, day or night, you can always change the channel. -- From "Taxi" --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com