search for: remotefile

Hi, I''m exploring Puppet and have hit a rather weird problem. The puppetmaster server is running CentOS4, fully updated, with puppet installed from the dlutter RPM repo, version 0.20.0-1.el4. I tried adding the remotefile function definition from http://reductivelabs.com/projects/puppet/documentation/installation.html in /etc/puppet/manifests/utils/remotefile.pp but when I start puppetmasterd I get: riffraff:brown /etc/puppet/manifests/utils $ sudo /usr/sbin/puppetmasterd --verbose info: Starting server for Puppet...

What is the right way to write definition so that defaults can be overriden? $puppetdir = "puppet://$server/files" define remotefile($source, $owner = "root", $group = "root", $mode = 0644, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup, recurse => $recurse, source => &q...

I tried using $name in this manner: remotefile { "/etc/auto_direct.local": mode => 644, source => "solall/$name" } (The remotefile function is handy, BTW) When I use $name here, instead of specifying the actual path to the file (solall/etc/auto_direct.local), puppetd ends up making /etc/auto_direct.lo...

"Service and class definitions are scoped just as variable assignments are." But what about types? Here''s an example: class solserver inherits server { remotefile { "/etc/shadow": mode => 400, group => staff, source => "solall/etc/shadow.server" } Is it possible to just override the "/etc/shadow" definition for some nodes? It certainly doesn''t work to just redefine the remotefile["/etc...

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? - Ian

I recently update my remotefile definitions (others might have already done so or have been using a better one than mine). I added an ensure parameter so I could do overrides using remotefile rather than the underlying file: define remotefile($owner = root, $ignore = ".svn", $group = root, $mode = 644, $source, $ba...

Hi, I had a working puppet setup using version 0.22 until the ruby security patch bit me. I tried upgrading server and clients to 0.24.1 however my old manifests don''t seem to work anymore. When I run puppetd on the client I see lots of messages like: err: //Node[waterbuck]/yumupdater/Remotefile[/etc/cron.hourly/yumupdater]/File[/etc/cron.hourly/yumupdater]/ensure: change from absent to file failed: Could not set file on ensure: undefined method `[]'' for nil:NilClass at /raid/puppet/manifests/definitions/remotefile.pp:15 The remotefile.pp looks ok to me: ----------- remotefile ....

Hello The following chunk is within a class definition. ${name} is being exchanged with an empty string: remotefile { "/${server_xml}": owner => tomcat, group => tomcat, mode => 600, source => "${ftoe_src_prefix_dev}${name}.jvm1" } However in the following chunk, lower down in the same class definition, ${name} is being exchanged with "/usr/local/tom...

...ckage { bash: source => "/usr/ports/packages/i386/All/bash-3.1.17.tbz", ensure => installed, subscribe => [''/etc/profile'',''/etc/profile.d/'',''/etc/bash/''] } remotefile{ "/etc/profile": mode => 664, source => "apps/bash/etc/profile" } remotefile { "/etc/profile.d/": mode => 664, source => "apps/bash/etc/profile.d/" }...

Hi, I''m trying to use several sources to pick from in a remotefile statement: remotefile { "/etc/sudoers": mode => 0440, source => [ "config/apps/sudo/sudoers.${host}", "config/apps/sudo/sudoers" ], sourceselect => first } But it doesn''t seem to work. I get an error like this: "File source /srv/...

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup, recurse => $re...

Hi everyone, I got a basic puppetmaster setup, which works well for Linux. I''ve setup a basic function: define remotefile($owner = root, $group = root, $mode, $source, $backup = false, $recurse = false) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup, source => [ &q...

So I have $base = "/opt/local/etc" remotefile { "$base/saslauthd.conf": source => "apps/saslauthd/saslauthd.conf", mode => 400, # This file contains special info owner => root; "$base/saslauthd.init": source => "apps/saslauthd/s...

I am trying to write a definition that downloads and extracts a tar file if the destination directory does not exist. The tar file won''t change and does not need to be download and extracted if it changes. The definition I am using now is: define remote_tar($source, $directory) { remotefile { "/tmp/$name.tgz": source => $source, } exec { "tar-$name": command => "tar -xzf /tmp/$name.tgz", directory => $directory, creates => "$directory/$name", require => File["/tmp/$name.tgz&quot...

Hi, I just upgraded to puppet 0.20.0 today after a short time playing with 0.19.3. The docs say to use the uppercase form for types but that seems to break for me. When I updated the remotefile function to use the new way, the puppet clients complain about objects not being found. For example: ----- OLD WAY (works, just with deprecations) ----- define remotefile (...) { file { $name : owner => $owner, source => "puppet://$server/$source" } } ----...

...restart => true } on any changes in nrpe.cfg the files get synced on the puppet client and puppetd writes out the following messages when running in debug mode: info: Filebucket[/var/lib/puppet/clientbucket]: Adding /etc/nagios/nrpe.cfg(d74c3c576cbc9c400407f679af44ed0e) info: //base/nagios/remotefile[/etc/nagios/nrpe.cfg]/File[/etc/nagios/nrpe.cfg]: Filebucketed to puppet with sum d74c3c576cbc9c400407f679af44ed0e debug: //base/nagios/remotefile[/etc/nagios/nrpe.cfg]/File[/etc/nagios/nrpe.cfg]/checksum: Replacing /etc/nagios/nrpe.cfg checksum {md5}d74c3c576cbc9c400407f679af44ed0e with {md5...

...group => $name, mode => 755, require => User[$name] } file { "$home/.ssh": ensure => directory, owner => $name, group => $name, mode => 700, require => File[$home] } remotefile { "$home/.ssh/authorized_keys": source => "sshkeys/$name", mode => 600, owner => $name, group => $name, require => File[$home] } } I can call it with: systemuser { newusername: home => "/home/...

I just upgraded to 0.22.0 from 0.18.4 and I''m running into what I think are problems due to changes in scope rules. In my site.pp manifest, I have the following: import "classes/*" node nfsserver { include nfsserver } node webserver { include webserver } class cluster1_sites { website { "example.com": ...; "example2.com": ...; } } node

...ere not trusted: hostname was not match with the server certificate Any subsequent runnings of puppetd --test give the same error. puppet.myclient.com is a CNAME. When I pass the A record on the command line, I get a little further, but still see similar errors: err: //workstation/puppet-config/remotefile[/etc/sysconfig/puppet]/File[/etc/sysconfig/puppet]/source: Could not describe /files/puppet-config/puppet.sysconfig: Certificates were not trusted: hostname was not match with the server certificate info: //workstation/puppet-config/remotefile[/etc/sysconfig/puppet]/File[/etc/sysconfig/puppet]/sour...

...mplains it doesn''t know how to install freenx. However I don''t want it to install freenx even if it would figure out how to do that. If freenx is not installed I just don''t want this class to have any net effect. -------------------------- class nx_clientkey { remotefile { "/var/lib/nxserver/home/.ssh/authorized_keys2": source => "os/$operatingsystem/nx/authorized_keys2", ensure => file, mode => 600 } remotefile { "/var/lib/nxserver/home/.ssh/default.id_dsa.pub":...