similar to: could not find user 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

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:

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

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

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

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

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

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

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

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

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

(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

Hello, i wanted to know if we can use exported ressrouces to do things like this: - for all nodes tagged as xxx create on the node yyy a file which content is a template where we can have each hostname , or create one file per nodes matching exemple /etc/hosts.allow sshd: host1 sshd: host2 ... or /etc/backuppc/host1 /etc/backuppc/host2 ... from the docs it seems i can collect only ALL

Hi all, I''m using the version 0.24.1 with strange problem: When I enable storeconfigs in puppetmaster (puppet.conf) I have the following error on clients debug: Finishing transaction -604715208 with 0 changes info: Loading fact hardware_platform info: Loading fact dmi debug: Retrieved facts in 2.12 seconds debug: Calling puppetmaster.freshness *err: Could not retrieve configuration:

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

Hello everyone... I have configured the puppetmaster to use Apache/Passenger. However, executing a configprint (puppet --configprint all) from either the puppetmaster or an agent shows servertype = Webbrick Has anyone else seen this? What do I need to do to correct this? Thanks! JA -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

Hi, I''ve got some problems with setting up environments. On the master: [main] [...] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [...] environments = production,staging [production] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [staging] manifestdir = /opt/puppet-staging/manifests modulepath = /opt/puppet-staging/modules [puppetmasterd]

Hi - I a ran puppetd -vt against a brand newly build host (which is what I normally do for a new host) and got the usual message: err: No certificate; running with reduced functionality. info: Creating a new certificate request for sega-dev-1. info: Requesting certificate On the puppetmaster, I then list the waiting host with: puppetca --list then sign the key. In this case, I decided that the