similar to: puppetversion and downgrade/upgrade of puppet

Hello, I try to install puppet on freebsd 6.X. All is well but i cannot get the certificte to install and be recognized. I run .19.3. I run the puppetd --test --waitforcert 60 then sign and then i got: err: No certificate; running with reduced functionality. info: Creating a new SSL key at /usr/local/.aqadmin/puppet/conf/ssl/private_keys/xxxxxxxxxxxxxx.pem info: Creating a new certificate

I have a little issue with purging. I use: file { [''/etc/shorewall/puppet'',''/etc/shorewall/puppet/rules'']: ensure => directory, mode => 0700, recurse => true, purge => true, } but purging does not work, i can do a touch

Hello, from the doc it seems that the User type has a provider of ''pw'' for FreeBSD. It seems the provider does not allow dupelicate, does not allow to manage the homedir and to manage password. in the code the duplicate uid is set so it seems the doc is out of date on this :) - manage home directory, i don''t really understand what is that parameter. The

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; \

Hello, I have a strange problem this nigth that i cannot solve, perhaps you can help me understand what is wrong. I have a file type that upload a directory into my servers. Inside this uploaded directory i create subdirectory and files on my own (directly on the target host). The problem is that when puppet comes back to the directory it spills out this error: err:

Hello, i use a file type to manage sysctl.conf. For some work i override this file by doign File[''/etc/sysctl.conf''] and i have an exec refresh only to run sysctl -p so it reread the sysctl.conf file if changed. My issue is that at each run i got, i start in state when i see the overriden one on the server: 1st run, i have the basic sysctl.conf not the ovveriden one

I just upgraded to .22.3 from .22.1 and now i got several error messages. I havent found why i got them. Nothing has changed but still there is error and i cannot correct them: err: Package[lsb-release](provider=aptitude): Could not find latest version i run debug: debug: package provider aptitude: Executing ''/usr/bin/dpkg-query -W --showformat ${Status} ${Package} ${Version}\n

(I''m emailing the list, rather than direct.) Adnet Ghislain wrote: > Hello, > > More on my deployment, i have an issue where the fact sometime does > not load and it seems that they do not work and as i rely on facts in it > ll fails: > > Oct 6 02:54:18 oiseadmin puppetd[42243]: Could not call > fileserver.list: #<Errno::ECONNRESET: Connection reset

Hi, I have a define that use a configuration file. Most of the time this is the same configuration file. Here this is a rsync configuration file. The issue is that i want the define to take care of the management of the file as only this define use it: define filevault( $source, $destination, $recursif = ''true'', $deletesource = ''delete'', $exclude =

It seems to me that when you setup an environement for a cron it just recreate the crontab at each run even if the cron has not changed. Seems it does not recognize actual environement settings. I put 2 environement and i got: info: Writing cron tab for aqadmin /linux/cron=puppetdcron/environment: environment changed '''' to

Cant seem to get Passenger to work on my test server. Keep getting the following error in access_log *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (no such file to load -- rack/builder) (process 1998): from config.ru:1 Rack was installed from gem and is in the gempath. puppetversion 0.24.8 (both server and client) passenger (2.2.5) rack (1.0.1) rake (0.8.3) RHEL

I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any ideas? Sanitized facter output: architecture => i386 domain => missyou.edu facterversion => 1.5.7 fqdn => broken.missyou.edu hardwareisa => i686 hardwaremodel => i686 hostname => broken id => root interfaces => eth0,sit0 ipaddress => 1.2.1.5 ipaddress_eth0 => 1.2.1.5 is_virtual => true

sorry to come with such a silly request but i have a code: shorewall-zone { "$name": SHTYPE => ''ipv4'', PARENT => "$PARENT" } and it bring a syntax error : debug: importing

Hi, I am getting the following error on my CentOS clients; err: Could not run Puppet configuration client: Invalid parameter stage at /etc/puppet/manifests/nodes.pp:32 The server is CentOS 5.4 with packages from the epel-puppet repos; # rpm -qa | grep puppet puppet-dashboard-1.0.3-3 puppet-2.6.1-0.3.rc3.el5 puppet-server-2.6.1-0.3.rc3.el5 The clients are; # rpm -qa | grep puppet

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction

fact loads: I use facter to search the rsync path and then i write this sudoers line: Cmnd_Alias BACKUPCOMMANDS = /usr/bin/rsync I call puppet like this: puppetd --factsync --server=xxx.yyy.61.131 --waitforcert 60 --test the recipe is: sudoensure_line { sudobackupcommands: ligne => "Cmnd_Alias BACKUPCOMMANDS = $rsyncpath",

First of all, I apologize for the triple post, but I did not see that the word wrap on the r-help list site would render my code unusable. So here it is again. Hoping that this time it will work if you cut and paste it in your Rgui. I have a program that works well in Rgui but that does not work in a batch file (Execution halted). Here's the code (it will work on your R, but you need

Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761

I have some facter file to distribute before running puppet on the platform. The problem is : how can i send the facter local.rb file so the rest of the .pp file take into account the new facts created ? ex: i have sudopath as a facter fact and one sudoers class that need that sudopath to work. How do you model that ? it seems puppet would have to rerun after the new local.rb is downloaded

Hello there, Since the update with ruby all my puppet function is dead (well known issue with the cert) . There has been some discutions on the dev list on how to patch this for future versions. I have read the list and wondered how we can solve the issue while waiting for the .24. I am in beta test of the .23.x version but on my production system i wanted to find a way to solve this now