similar to: Strange messages on 0.25.4.

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":

Greetings. I am trying to set up a test puppet server in my environment to evaluate windows clients. On the server side, I am using puppet 2.7.14 (from the repos). I''m using the 2.7.14 windows 64 bit on the client (windows 2008 R2). I have another puppetmaster already using "puppet" hostname in DNS (running a very old version of puppet - can''t upgrade yet for various

Hi everyone, I have a puppet master/client infrastructure setup with apache. When on the same datacenter I don''t have any problem. I am trying to use another datacenter, so I setup the fileserver.conf as followed: # Files in the /path/to/files directory will be served # at puppet:///mount_point/. [modules] allow *.datacenter1 allow *.datacenter2 [plugins]

OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not

I''m rather new to puppet and I''ve been trying to get a module to work on the client servers. Right now I''m trying to get http://forge.puppetlabs.com/ghoneycutt/pam to run. When I try to run it I get these two errors: err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of resource: Could not retrieve information from source(s)

I am new to using puppet and having trouble when updating an agent from a master which has a lot of files. Usually the updates work, but when there are a lot of files I get this error when running: sudo puppetd --test --server puppet.example.local --trace --debug >>> debug: Failed to load library ''rubygems'' for feature ''rubygems'' debug: Failed to load

Hi all, I''m having a stupid moment getting a remote file bucket working. My client only file buckets locally, not remotely. I have this site.pp: ********* filebucket { "main": server => "puppet" } File { backup => "main" } node ''default'' { include test } ********* and this test module: ********* class test { file {

For some reason I am unable to run "dry runs" of the puppet client on my puppetmaster server. Running puppetd with the --test, --noop and verbose / debug flags results in nothing for about a minute or two then this output... $ time puppetd --test --noop -v err: Could not retrieve catalog from remote server: execution expired warning: Not using cache on failed catalog err: Could not

Hi guys, I am fairly new to puppet and I am having a problem with one of the clients. I recently installed a new server that should get config from puppet master. All similar servers I recently installed didn''t have any problem. I installed puppet agent on the server and sent a sign request. SSL cert is signed but when I run puppetd manually I get the following: info: Retrieving

Hi All, In my set-up, I''ve got a cron job that triggers a Puppet run every 20 minutes. I''ve found that on approximately 13 nodes (out of 166), puppetd just hangs. I have to go in, kill the process, remove /var/lib/puppet/state/puppetdlock, and run puppet again and then it''s fine. After a while, it just hangs again so I have to go in, kill the process, etc. Any ideas?

Hi, i''m a newbie about Puppet( 1 month ~) i got error on generate temp file, i''ll explain my situation: -i have a puppetmaster(version: 3.3.0),executed on root and a puppet agent(version 2.7) provisioning by vagrant,executed on root -my site.pp, where webserv is a parametrized class, and typews is a parameter to choice nginx or lamp module, -i have my Enc node with path

Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet

Hello, we have one puppet server managing approx servers, all FreeBSD. The problem is that the puppet clients all hangs, one by one, eventually. They will run for anything between an hour up to a week. But eventually the all hang. We really like puppet and want to keep using it. But the way it is now is completely unusable. We''ve tried many versions, from 24.x, and now 2.6.1rc1. But

on my puppet master server (v 2.7.17 , both server and client version) , the puppet agent can''t connect to itself. other clients connected to this puppet server are working fine. the hostname is puppet.domain.com [root@puppet /]# cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet

Hoping you guys might be able to help me out, I''m not sure what''s wrong but puppet agent hangs for over a minute, no resource spikes (CPU, memory, etc all stay basically the same as without starting puppet, barely a blip, and I''ve got more than enough headroom). It''s not a serious issue for continuous usage, but really, really annoying when testing the manifests

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Hi guys, I have a box that needs to identify itself to the puppetmaster as something different from the FQDN. I added certname to the agent configuration before the first run, but it doesn''t seem to be sufficient. The certificate was generated for the FQDN, and the host appears in the dashboard as the FQDN, and the node name used to evaluate the manifest is also the FQDN. I would

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

Hi guys, I''m trying to setup my first puppet installation and I''m running into problems. I''ve got the puppetmaster running on a fresh install of Centos 5.4. The puppet client is also on another Centos 5.4 server. Once I''ve signed the client certificate on the puppetmaster, the client seems to break. See below for the debug output from the client. Any clue as

Hey folks, I am using puppet for some OpenStack deployments and on a new node things look pretty good right until after the successful reception of a cert from the puppet master. I get this error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: $concat_basedir not defined. Try running again with pluginsync enabled at