On Apr 1, 4:37 pm, James Turnbull <[email protected]> wrote: > Scott Frazer wrote: > > I saw something similar when I tried to preseed the installation of > > puppet using "d-i pkgsel/include string puppet" > > > The preseed installation used different directory paths than the "apt- > > get install puppet" installs I had done previously. When my > > centralized puppet.conf file would get written to the client, the next > > run through consistently produced a bunch of 500 errors as the > > certificates no longer matched. So you might check that your certs > > are where you think they should be. Maybe with "puppetd --genconfig" ? > > Whilst I am not preseed best friend I don't see how this is possible. > > Why would preseed do installation any differently? d-i pkgsel/include > should use Debian standard package tool - in this case aptitude - to > install.
I'd love to know myself. All I know is that I spent a weekend trying to figure out why my new installs were constantly generating 500 messages. Then I discovered that Ubuntu also broke apt-get in such a way as to prevent it from doing an install on first boot through an init.d script. For now, I've got a manual process in setting up the puppet client software, but then everything else gets set up for me, so it's still a time saver. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
