search for: puppet_server

...for now. I have a configuration for NTP that looks like this: class ntpd { package { "ntp": ensure => installed, } file { "/etc/ntp.conf": owner => root, group => root, mode => 0644, source => "puppet://$puppet_server/files/ntp.conf", require => Package["ntp"] } service { "ntpd": ensure => running, enable => true, hasrestart => true, hasstatus => true, require => [Package["ntp"], File["/etc/ntp.conf...

...I notice the exhaustive listing of each files properties and settings and wonder if there is a way to have a file inherit settings from other files? Ie instead of: file { "main_cvd": path => "/var/lib/clamav/main.cvd", source => "puppet://$puppet_server/files/clamav/main.cvd", ensure => present, mode => 644, owner => vscan, group => vscan, before => SERVICE["clamd"], require => PACKAGE["clamav"] } file { "daily_cvd": path...

I''ve spent the last week or two poring over the documentation and setting up my first puppet environment, and while I''ve figured out how to do most of what I want to do with it, I have some questions that I haven''t been able to find answers for... * Can I match parts of a facter fact? In particular I have hostnames that include the environment as part of the

...ected to. Trying to read documentation about ext.nodes and searching the archives I couldn''t come up with any useful results. My classifier script outputs: --- YAML --- classes: - geodns::production::backend environment: production name: z01-06-02 parameters: puppet_server: z01-06-02 This is both master and client. While debugging with --trace --debug, etc.. I noticed that: - the ext node script is invoked and produces the correct result - if I remove my "geodns::production::backend" .pp file or I put a deliberate error in it, puppet rightly complains...

Hello, When I set: source => "puppet://mypuppet.company.com/apache/httpd.conf" which directory should I put httpd.conf under the puppet server machine mypuppet.company.com? I checked the documentation but cannot find the answer. Thanks. Peter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

Hi all, I have a slightly confusing Problem with fileserving. # /etc/puppet/manifests/classes/ntp.pp class ntp { file { "ntp.conf": path => "/etc/ntp.conf", source => "puppet://$puppet_server/files/ntp.conf", ensure => present, mode => 644, owner => root, group => root, } } Creating missing Files works like a charm: notice: //workstation/ntp/File[ntp.conf]/ensure: created But if the file was locally modified, puppet is complainin...

Hello everyone, I''m a new user regarding puppet but I''m skilled with linux. I have setup a puppetmaster server and also have a puppet client for testing on a different box. /etc/sysconfig/puppet has been edited to reach puppetmaster with option PUPPET_SERVER=puppet.mydomain.cr (I''m in Costa Rica) On the puppetmaster I was able to see the client with puppetca --list. I was also able to sign the certificate with puppetca --sign schoolserver.flexi.mydomain.cr That''s as much as I have done. However, looking at the log files on the c...

Hi all, I attempted to add an EL5.1 client to our puppet server (EL5), and after signing the client cert, got the error "Certificates were not trusted: hostname not match with the server certificate" I found the mailing list discussion and the relevant page: http://www.reductivelabs.com/trac/puppet/wiki/RubySSL-2007-006 As far as I can tell, my puppermaster''s cert CN matches

...rattleresearch.com/files/cron-apt/config failed: Could not find server puppet I have defined the ''server'' parameter in my puppetd.conf on the new client and it successfully transfers files when using : file { "/etc/cron-apt/config": source => "puppet://$puppet_server/files/cron-apt/config" } Seems strange it works on one client but not this one, can anybody suggest a reason why ? Thanks, Rob

Hi, I''m trying to import a gpg key (for repository signing) for my servers root user, with something like this : file { "/etc/company/company-gpg-key": owner => root, group => root, mode => 0644, source => "puppet://$puppet_server/files/backports/company-gpg-key", } exec { "gpg --import /etc/company/company-gpg-key": unless => "gpg --list-keys | grep ''company''" } However the command is being run as the puppet user and thus not being imported into root''s gpg keyring....

...senode/os-ubuntu/Package[man]/ensure: created notice: Finished configuration run in 52.47 seconds The relevant config elements are : file { "/etc/init.d/firewall": owner => "root", group => "root", mode => 755, source => "puppet://$puppet_server/files/init.d/firewall", before => service["firewall"] } service { "firewall": ensure => true, enable => true } and ... package { "man": ensure => installed } Thanks, Rob

...and EL5) images, the kickstart process writes out a file (/etc/sysconfig/soe) that contains: SOE_VERSION="Version string" SOE_BUILD_DATE="2009-03-06" I then have /etc/profile.d/facter.sh scripts that has this: . /etc/sysconfig/puppet . /etc/sysconfig/soe FACTER_PUPPETMASTER=$PUPPET_SERVER FACTER_SOE_VERSION=$SOE_VERSION FACTER_SOE_BUILD_DATE=$SOE_BUILD_DATE If I login, obviously the profile is loaded, the envvars are created and running puppetd manually means that Facter can see those envvars and my motd template works (it inserts those values). However, when Puppet runs as a se...

I''m using puppet to manage configs on machines where I don''t have root access. Whenever I use a File resource where the source is a puppet:// resource, I get tons of warnings when I run puppet that look like: Cannot manage ownership unless running as root True enough, I''m not running as root, but I also didn''t specifically mention a "owner"

Hi, I am running puppet-server 0.25.5 on CentOS 5.4. I defined a moudle in /etc/puppet/fileserver.conf as below: [files] path /tmp/puppet allow * I also defined a resource in /etc/puppet/manifests/site.pp: file { "/etc/passwd": owner => "root", group => "bin", mode => 644, } file { "/tmp/0909.txt": source =>

On a file resource, if the content parameter is set and checksum is set to none, I am getting "Parameter content failed: Munging failed..." This appears to be a bug, but maybe I missed something in the documentation and it isn''t supposed to work. cat test.pp file { "/tmp/foo": checksum => none, content => "this is foo\n", } puppet

Hi, I''m running client with --logdest=/var/log/puppet.log just to get a clean puppet log and don''t mix it with messages. # grep . /etc/sysconfig/puppet |grep -v "^#" PUPPET_SERVER=gridinstall01.pic.es PUPPET_LOG=/var/log/puppet.log But I only get this message in new log: # cat /var/log/puppet.log Mon Nov 24 14:59:53 CET 2008 Puppet (notice): Reopening log files And I know it runs cause I see puppet process calling yum, etc... Do I have to do anything else? **If I comm...

...After a few hickups (basically had to turn off RackBaseURI and turn on RailsAutoDetect) i got it running under https. I noticed today that reports hadn''t shown up since I switched to passenger and https so I switched it back to http and reports are working again. i had reporturl = https://$puppet_server/reports/upload/ set in the master section of my puppet masters conf file. i also had reposts = store, http I noticed in the docs for dashboard i need puppetmaster running under passenger to get reports working via https but it doesn''t mention much else. Has anyone else had a similar issu...

Does anyone have any suggestions about how to deal with multiple environments/tiers? For instance, we have several environments ( production, dev, qa, etc.. ) and within each environment, different tiers ( web, data, app, etc ). Each tier is a different IP network segment, so all the hosts in each tier have different configurations for certain things like resolv.conf, ntp.conf and so on. We do

...external_node_scripts_for_version_023_and_later > #!/bin/sh > # Super-simple external_node script for versions 0.23 and later > cat <<"END" > --- > classes: > - common > - puppet > - dns > - ntp > environment: production > parameters: > puppet_server: puppet.example.com > dns_server: ns.example.com > mail_server: mail.example.com > END > exit 0 And here''s the default output from the external node tool. > - name: server.example.com > parameters: {} > > classes: [] > ...without the environment defi...

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