similar to: upgrade to .22.3 and got errors on packages (debian sarge)

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

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

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:

Dear all, I''m seeing this strange thing: When I run "*puppet agent -td*" on the node (Nagios, in this example case), puppet fails to install Nagios3 (on Debian) with this: Debug: Executing ''/usr/bin/dpkg-query -W --showformat ${Status} ${Package} > ${Version}\n nagios3'' > Debug: Executing ''/usr/bin/apt-get -q -y -o >

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

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

Hi all, I''m getting very close to the next release of Puppet, and I need help making sure it''s as bug-free as possible. The major changes in this version relate to Rails (and thus resource collect/export) and transaction internals. If you are currently using Puppet''s rails support, you''re going to have to migrate manually, unfortunately (or just

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",

Hello, Since i use facter 1.5.5 i got error running it by hand. It still work in puppet but i loosed the hability to run it from the command line: (aqadmin)> /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50:in `require'': no such file to load -- facter (LoadError) from /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50

i wonder why this case fail: case puppetversion { ''0.22.4'':{ #ok notice(''ok bonne version'') } default:{ fail("mauvaise version de puppet $puppetversion, downgrade vers 0.22.4") } } gives me: protos:/usr/local/.aqadmin/home%(aqadmin)> facter puppetversion 0.22.4

(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 try install python-psycopg2 with other packages, when run apt-get -y update returns the errors: err: /Stage[main]/Etc/Package[build-essential]/ensure: change from purged to present failed: Could not set ''present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 err:

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

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

Hi, I''ve inherited a puppet setup for automating php installation and extension management. We''re on Debian and we''ve encountered a strange issue that I''ve traced down back to puppet I think. I''ve stripped back the configuration and made the problem reproducible, logs and config pasted below. 1. php5-common, php5-memcache, and php5-mysql are all

Basically, the way puppet installs things things with /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install <package_name> fails due to authentication WARNING: The following packages cannot be authenticated But if I do it from an ssh console normally, using apt-get install <package_name> it works fine without issues. Is there a way to change how puppet uses the

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 =

Hi, Just a quick query about some things that crop up when I run ''puppetd --test''. Every time I run this command I always see the following output, which I think is strange as the ''man'' package has been installed previously and the firewall service is definitely running. Has anybody got any suggestions as to why puppet thinks it needs to install the man

is there any way to prevent this timeou ? i tried --configtimeout=600 --filetimeout=600 but this does not changes anything -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users