I install puppet as part of a Fedora and CentOS kickstart install and
this use to provide a nicely configured client immediately after the
first reboot from the kickstart completion. However with 0.22.3 i now
see the following error on puppets 1st run, as a result the client is
not configured.
The problem is easily rectified by connecting to each client and
restarting puppet.
I have also left puppet out of the kickstart process and installed it by
hand after the install is complete and the same thing. It takes two
starts for things to start working.
Any idea?
Ben
Error:
Mon Apr 16 15:03:09 +1000 2007 Puppet (notice): Reopening log files
Mon Apr 16 15:03:10 +1000 2007 Puppet (notice): Starting Puppet
client version 0.22.3
Mon Apr 16 15:03:11 +1000 2007 Puppet (err): Could not call
puppetmaster.getconfig: #<NoMethodError: private method `split''
called for nil:NilClass>
Mon Apr 16 15:03:11 +1000 2007 Puppet (err): Could not retrieve
configuration: private method `split'' called for nil:NilClass
Mon Apr 16 15:03:11 +1000 2007 Puppet (err): Could not run
Puppet::Network::Client::Master: Cannot connect to server and there
is no cached configuration
Ben, This works for me currently with Kickstarting RHEL4/5 and Jumpstarting Solaris. I have had this exact error in the past, (as have others on the mailing list), but do not seem to be currently. I use 0.22.3. Couple of things people have reported recently you may want to take a look at. 1) Some people have had problems with the client having the time too far out on the client, and if your bootstrapping with Puppet then you presumably don''t have NTP configured yet. You could try an ntpdate during the post install or first boot. The code in CVS is less stringent. 2) Luke has fixed a bug in the certificate initialization code on 30th March that caused the second run (the one that retrieves the signed cert) to fail with this error, it is in CVS. I guess you are looking for 0.22.4 or you can role your own RPMs Rgds Scott On Mon, 2007-04-16 at 15:25 +1000, Ben wrote:> I install puppet as part of a Fedora and CentOS kickstart install and > this use to provide a nicely configured client immediately after the > first reboot from the kickstart completion. However with 0.22.3 i now > see the following error on puppets 1st run, as a result the client is > not configured. > > The problem is easily rectified by connecting to each client and > restarting puppet. > > I have also left puppet out of the kickstart process and installed it by > hand after the install is complete and the same thing. It takes two > starts for things to start working. > > Any idea? > > Ben > > Error: > > Mon Apr 16 15:03:09 +1000 2007 Puppet (notice): Reopening log files > Mon Apr 16 15:03:10 +1000 2007 Puppet (notice): Starting Puppet > client version 0.22.3 > Mon Apr 16 15:03:11 +1000 2007 Puppet (err): Could not call > puppetmaster.getconfig: #<NoMethodError: private method `split'' > called for nil:NilClass> > Mon Apr 16 15:03:11 +1000 2007 Puppet (err): Could not retrieve > configuration: private method `split'' called for nil:NilClass > Mon Apr 16 15:03:11 +1000 2007 Puppet (err): Could not run > Puppet::Network::Client::Master: Cannot connect to server and there > is no cached configuration > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users
On 4/16/07, Ben <abnormaliti@clivepeeters.com.au> wrote:> I install puppet as part of a Fedora and CentOS kickstart install and > this use to provide a nicely configured client immediately after the > first reboot from the kickstart completion. However with 0.22.3 i now > see the following error on puppets 1st run, as a result the client is > not configured. > > The problem is easily rectified by connecting to each client and > restarting puppet. > > I have also left puppet out of the kickstart process and installed it by > hand after the install is complete and the same thing. It takes two > starts for things to start working. > > Any idea?I have this problem with the clients the puppetmaster is auto signing. The way I''ve worked around this is have puppet installed during the kickstart phase and then in the post section of kickstart "echo" commands into /etc/rc.local, so they are run on first boot. I run the puppetd command twice. This is from memory but something like this: echo "ntpdate time.example.com" >> /etc/rc.local echo "puppetd -v -o --server puppet.example.com" >> /etc/rc.local echo "sleep 2" >> /etc/rc.local echo "puppetd -v -o --server puppet.example.com" >> /etc/rc.local When this run kicks off on first boot, it also replaces the original rc.local file. hth, Kent
On Apr 16, 2007, at 12:25 AM, Ben wrote:> I install puppet as part of a Fedora and CentOS kickstart install and > this use to provide a nicely configured client immediately after the > first reboot from the kickstart completion. However with 0.22.3 i now > see the following error on puppets 1st run, as a result the client is > not configured.As Scott White mentioned, this is a bug in 0.22.3, and I''ll be releasing a fix as soon as I can, likely this week. -- The most incomprehensible thing about the world is that it is at all comprehensible. --Albert Einstein --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies wrote:> On Apr 16, 2007, at 12:25 AM, Ben wrote: > > >> I install puppet as part of a Fedora and CentOS kickstart install and >> this use to provide a nicely configured client immediately after the >> first reboot from the kickstart completion. However with 0.22.3 i now >> see the following error on puppets 1st run, as a result the client is >> not configured. >> > > As Scott White mentioned, this is a bug in 0.22.3, and I''ll be > releasing a fix as soon as I can, likely this week. > >Thanks for all your responses. While waiting for the next release i will add a the following to the kickstart %post and see if that helps. /sbin/chkconfig --level 345 puppet on hostname my.host.name.com echo "PUPPET_SERVER=puppet.domain.com PUPPET_LOG=/var/log/puppet/puppet.log PUPPET_EXTRA_OPTS=\"--autoflush\" " >> /etc/sysconfig/puppet /usr/sbin/ntpdate time /etc/init.d/puppet once -v --tag no_such_tag Ben.