similar to: Problem starting puppetd for the first time (Could not create resources ...)

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its

Hello, Configuration : - Debian 8 - Wordpress 5.3.2 (Apache) - Icecast 2 - Radio web player : Streamcast I just installed my Web radio that was working correctly in full HTTP. I add a Lets Encrypt certificat on my Wordpress that is now in HTTPS. Since my Wordpress is in HTTPS, my stream on the website is not working. The direct Link in HTTP is working correctly. I checked on the internet and

Hi, From looking at the puppetd --help, there is not currently (at 0.22.4) a method of specifying tags in the puppetd.conf. I was hoping to use this for the following reason: Currently, I use ''noop = true'' in my puppetd.conf, and run ''puppetd --no-noop {tags}'' to install the configurations that I am happy with. This is because I''m currently

Hello all, I am new to puppet and I currently just use it during development - just two hosts. I only manage distribution of files/permissions with it. I am wondering why puppetd is running slowly on one of these machines. Google told me that File with "recurse => true" will make things run slowly. I use "recurse => true" :( Now I want to find out now if the slowdown I

Hi, I have a lot of systems where the puppetd doesn''t do anything .. When I test with puppetd -tv, it s running well, but when it is started as deamon th process do nothing :( How can I debug this ? Vincent May 29 10:07:56 puppetd[6160]: Reopening log files May 29 10:07:56 puppetd[6160]: Starting Puppet client version 0.24.8 May 29 10:07:56 puppet: puppetd startup succeeded May 29

Hi experts! I am running Puppet 0.25.5 on CentOS, and I have two machines, one running as master one as client. My master machine seems alright but my client machine keeps on getting this message: "Could not run: Could not create PID file: /var/lib/puppet/run/puppetd.pid" I''m new to this and I''m really confused, the steps I took for the client is almost identical to

I''ve got the following class that runs if I activate the repo in /etc/yum.conf. If I run "puppetd -t" from the command line it will restart puppetd fine. If I let the class run on it''s own as a deamon puppetd does not restart. The puppetmaster on the other hand does restart using either method. I ran the client in "--debug" but that doesn''t seem to

Hello Luke, After our services do now successfully restart, we hit now the already opened bug where the restarted service takes over puppetd port if it''s configured to listen. One solution is to remove the listen option but it''s very nice to invoke a puppetrun on the clients from the central server without waiting for its next run. Where you already able to take a look? It

I configured my rsync daemon to be restarted when the rsyncd configuration file changes. When the rsync daemon gets restarted by puppet, it listens on the same port puppetd does, so running puppetd again results in an error. The init script for rsync is small and can not be changed from puppet (all variables are declared within the init script and it only searches for the path where the rsync

On the Configuration refrence page the listen setting is descriped thusly: listen Whether puppetd should listen for connections. If this is true, then by default only the runner server is started, which allows remote authorized and authenticated nodes to connect and trigger puppetd runs. The question is when listen is set to true, does puppetd only listen for remote calls or will it listen for

This feels like a FAQ and sorry if it is, I failed to find an answer. I''d like some advice on handling backward compatibility between puppetd and puppetmaster. My puppetmaster is at v0.24.5 using Debian Lenny packages. I tried to bring up a puppetd client v0.25.4 (Ubuntu 10.04 packages) but failed to have it download the puppetmaster''s certificate. The puppetd client seemed

If you install puppet from the ubuntu 9.04 repositories (apt-get install puppet) it sets up puppet differently than the gem. The differences are obvious from the /etc/puppet/puppet.conf which looks like this [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=true [puppetmasterd]

Hi, I have a Gentoo server running puppetmasterd from Puppet 0.24.1 and a Ubuntu server running puppetd from Puppet 0.23.2. I have added listen=true to the [puppetd] section on the client and run puppetd --debug. I then run puppetrun --debug --host hostname on the puppetmaster server. This is the output I get: Puppetmaster: # puppetrun --debug --host hostname Failed to load ruby LDAP library.

While running puppetd on a linux client I get the following, the actual spot that the segfault happens varies, but it always happens. This is on ubuntu with the stock apt ruby1.8.4 package. Puppet also installed from apt. Puppet version 0.18.4 It seems very likely that this isnt a bug in puppet per se, but it is tickling a yaml bug (regardless of where it fails, it is always yaml). But I

Hi folks I know that has, to some degree, been run over the past year in different ways, but, I may have yet another instance of an issue on this. The puppetmaster system and the puppet system are both running 0.24.7-r1, on a gentoo system. Other puppet systems are running 0.24.4. The puppet system (not the puppetmaster system) that is running 0.24.7-r1 is showing multiple close_wait

I am having troubles with getting puppetd running on some of my Solaris10 update 7 (05/2009) boxes. I use Jumpstart to build my servers, so the installation is repeatable, consistent, and automated, so it is especially confusing that some boxes work, and others don''t. I can ssh into both of these machines, so the host certs should be OK. As part of my installation, I download the

Hi, I was managing a bunch of Centos 4.5 with Puppet until the ruby security patch bit me creating ssl problems. As I''m not able/willing to patch the installed version I tried upgrading to dlutter''s 0.24.0-2.el5 version. Unfortunately this didn''t help much. So I removed the server and client installation completely (making sure to manually remove the config, ssl, ...

i''m having trouble with a file resource with 0.24.1. the manifest is very simple: file { "/": ensure => directory, owner => "root", group => "root", mode => 755 } when i run puppetd, i get the attached stack trace. removing this resource enables puppetd to complete its run successfully. any ideas? didn''t have this

Hello all, I have a little problem with the --listen option. Id like my client servers to update only when I run puppetrun on the puppetmaster server. So far, I tried: puppetd --listen --server mymasterserver -v (on the client server) Then: puppetrun --host myclientserver The updates runs ok... but the client check for updates again every 30 mins or so and I dont want him to do so. I tried:

When I use the latest puppet 0.25.1 I got the same problem. This is what I do: 0. Install the Ubuntu 8.04 server with ssh, ruby, rdoc, libopenssl- ruby and git-core (which gets removed after clone). 1. Install the latest puppet from git repositories on both machines using git clone «git clone git://github.com/reductivelabs/puppet» and «git clone git://github.com/reductivelabs/facter» 2. Install it