similar to: creation of an external node source

Hello all, I''ve tried to run ''puppetrun'', but there seems something unconfigured regarding the certificates. The reverse way (puppetd pulls the config from puppetmasterd) works fine. The namespaceauth.conf on the client (where puppetd runs) is configured as follows: [puppetrunner] allow *.abc.net (also tried the calling host: puppet1.abc.net) But when I call

Hi, We''re trying to follow the instructions at http://reductivelabs.com/trac/puppet/wiki/UsingMongrel (Just using a single puppetmaster/mongrel instance and plain mod_proxy for now, instead of balancer one) We got past the "Server is not a class" error by modifying mongrel.rb We also kind-of got past the: /opt/bin/puppetmasterd:293: undefined method `daemonize'' for

I''m about to leave town for three weeks and my home server keeps rebooting. It''s my mail server, unfortunately, so there''s a good chance you won''t get this. :/ Anyway, I''ve been meaning to do this for ages and ages, and it''s time to finally do so. I need to move all of the Puppet lists to a public, non-me provider, someone who has

Good day, After having lurked for a while I''ve decided to actually start using puppet starting on my small home network. I''ve been following : http://reductivelabs.com/trac/puppet/wiki/InstallationGuide and :- http://www.howtoforge.com/installing_puppet_on_ubuntu to test puppet on 2 hosts, librarian running the puppetmasterd and mortvm. Unfortunately, I

err: /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]: Failed to retrieve current state of resource: Could not find user puppet debug: Finishing transaction 75413780 with 2 changes since i put the last version on this test server i cannot launch puppet manualy: mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \

On Apr 30, 2007, at 4:44 AM, Frank.Munsche@izb.de wrote: > I''ve built a puppet solaris - package which is distributed via > jumpstart at installation time of a solaris 10 machine. > It''s postinstallation registers the puppetd into smf and starts > puppetd afterwards. Puppetd connects to puppetmasterd, gets ist > certificate signed (autosig on) and the

> I''ve built a puppet solaris - package which is distributed via jumpstart > at installation time of a solaris 10 machine. > It''s postinstallation registers the puppetd into smf and starts puppetd > afterwards. Puppetd connects to puppetmasterd, gets ist certificate signed > (autosig on) and the configuration stuff. > Now the interesting part: a new solaris zone

Hello folks, Im trying to migrate from static nodes-definition to external nodes definition. My script looks like this stolen from http://reductivelabs.com/trac/puppet/wiki/ExternalNodes: {{{ #!/usr/bin/perl -w use warnings; use YAML qw( Dump ); use Switch; #initialize vars our @classes; our %parameters; Function to fill @classes and %parameters with correct values .... print Dump( {

I''d like to keep some pretty granular class definitions in ldap; but I''m not sure what is the best way to turn that into a puppet manifest. Is anybody else doing something like this? For instance, a samba server might have the following classes defined (in ldap): samba, samba-bdc, samba-file-shares, samba-build-shares, etc... And I would like to do something like this: -- class

Hi, I think I''m having a similar problem to the user who raised this bug: http://reductivelabs.com/trac/puppet/ticket/733 I''m running 0.23.2 with storeconfigs. I''ve got it working to the point where my clients'' facts are being populated in the database[*] but updates don''t seem to happen unless I restart puppetmasterd. For example: 1) I run my test

So I am beginning the long process of learning puppet... and it seems that I am missing some vital things. My systems are RHEL-4, and i have installed the puppet/facter/puppetmasterd from dlutter@redhat.com''s archive. [root@canopus puppet]# rpm -qa | egrep ''puppet|facter'' | sort facter-1.3.6-1.el4 puppet-0.22.2-1.el4 puppet-server-0.22.2-1.el4 on the client I

Hi Everybody, I have 2 machines, one that running puppetmasterd and another one that running client. Both run Ubuntu. First I installed 2.25.4 (I think) version and then I have upgraded Puppet to 2.6.4 Server does not have any DNS entry, so I am trying to use IP address for the client to connect. Client generates some certificate error. root@puppet-client-ubuntu:~# puppetd --server

There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?

Hi all, I''m trying to set up puppet 0.24.5 using the packages provided for Mandriva 2009.0. After installing the packages and starting the puppetmaster service for the first time, the relevant CA certificates and keys are generated automatically and placed in subdirectories of $ssldir. However, when I then run puppetd on the same machine thus: $ puppetd --server myhost.mydomain

Hi all, I am new to puppet and also newcomer in this group. I heart good things about puppet and I decided to give it a try 2 weeks now. After reading various documentation, I began using the complete configuration collection of puppet modules (thanks to David). But I have a problem with the munin module. It works fine, except that it seems to not export virtual ressources. Let me give more detail

If you install puppet from the ubuntu 9.04 repositories (apt-get install puppet) it sets up puppet differently than the gem. The differences are obvious from the /etc/puppet/puppet.conf which looks like this [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=true [puppetmasterd]

I am having SSL difficulties setting up a new puppet client: Client: fedora (rawhide) using 0.23.2 Server: centos 4.4 using 0.22.3 After initiating contact with puppetd --test --server=puppet.myclient.com, I see the CSR on the server. After signing it, and running puppet again, I get the signed certificate, but also see: err: Could not retrieve configuration: Certificates were not trusted:

I''m trying to try out puppet and can''t seem to get to square one. I''ve been using cfengine for years and have just upgraded about 80 Debian machines to etch and wanted to try puppet. So, I have two Debian ''etch'' machines one a server and the other a client. I''m running puppet 0.23.2 installed from the unstable packages. As a first step

Hi All, I''ve installed puppet and puppetmaster on 2 separate Virtual Machines. I''ve started the puppetmasterd in Verbose debugging mode and im guetting this error on the master when I try and connect to it with the puppet client... err: Could not find puppetc.myhost.com with names puppetc.myhost.com, puppetc It seams that I''ve setup the certificate right

I recently had a working puppet server serving around 4-5 clients. One of the clients needed to be re-built and now only that client cannot connect. puppetca --clean hostname did not work So here is what I did on both the server/client I removed /var/lib/puppet/* Then I restarted the server via puppetmasterd --mkusers --verbose I then connect in via the client with /usr/bin/ruby