similar to: Fatal messages being lost from daemon

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.

I''ve tried this on two different setups all running 0.22.1. One group is Ubuntu/OpenBSD the other is RHEL4/RHEL4. Master has signed client certs. puppetd works fine from client. If I run from the server side: root@server:~# puppetrun --host client_host.example.com Failed to load ruby LDAP library. LDAP functionality will not be available Triggering client_host.example.com Host

I''m trying to get puppetrun to work, without luck so far. I have my puppetmaster and clients working fine with the clients polling the master. Now I want to be able to force an update. Using version 0.23.2 On the client I set listen=true and created the namespaceauth.conf file. Restarted puppetd and it appears fine. On the master I run puppetrun as root and get root@plane:/etc/puppet#

Guys, I seriously could not find this topic in the documentation. What do you do when you need to force puppetd hosts get the new settings from puppetmasterd? What I found was only sending USR1 signal to the client process in order to make it refresh its configuration from the master. But I find it a bit inconvenient for a large amount of hosts. There is also puppetrun which, if I understand

Hello all, I''ve tried to run ''puppetrun'', but there seems something unconfigured regarding the certificates. The reverse way (puppetd pulls the config from puppetmasterd) works fine. The namespaceauth.conf on the client (where puppetd runs) is configured as follows: [puppetrunner] allow *.abc.net (also tried the calling host: puppet1.abc.net) But when I call

Hi When using puppetrun to trigger machines to get and apply their configuration, it will only trigger the machine when executing puppetrun for the second time: puppetmaster # puppetrun --host puppetclient puppetclient log: -- snip Apr 13 08:19:49 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08 puppetd[20208]: puppetmaster(172.16.34.12) triggered run Apr 13 08:20:08

Hi All, I was surprised to notice that a call to noop from puppetrun did not work as expected. on the agent side (for this case the server side..), I ran: puppetd --verbose --no-daemonize (where listen is set in the puppet.conf) on the puppet server side(in this case the client side), I ran: puppetrun --noop --host SERVER notice: SERVER(IP) triggered run info: Caching catalog at

I''m using puppet 0.24.7-4. I have a situation where I have some very long running puppet runs in order to do upgrades (removing applications from load balancers gracefully, et cetera). My puppet runs triggered via puppetrun are finishing successfully: Jun 8 20:31:29 puppetd[10178]: Finished catalog run in 345.18 seconds Puppetrun itself is timing out: err: Connection timeout calling

Hi everyone, Please help, I have built a new server and installed puppet (2.6.17) running on RHEL 6.3. It seems that it is not listening on port 8139. iptables -L: Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt

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:

What''s this mean? root@gravity:/etc/puppet/manifests# puppetd -v --listen info: Starting handler for Runner info: Starting server for Puppet version 0.22.1 info: Listening on port 8139 notice: Starting Puppet client version 0.22.1 err: Could not run Puppet::Client::MasterClient: Host gravity.example.org not authorized to call puppetmaster.freshness Thanks, Kent -- "It may be true

hi all , i want to disable runinterval option on puppetd . as i know , after every 1800 sec.( 30 mins) , puppet client pull configuration from puppet master . I want configuration to be pushed to puppet client when i wwould fire puppetrun on puppet master rather than after every 30 min , configuration pulled puppet client. runinterval :How often puppetd applies the client

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point

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

What is required to allow running puppetrun as a normal user? The documentation implies that puppetrun has to be run as root to get access to the SSL certificates. What permissions need to be set to allow normal users (or a group of users) to perform puppetrun? Is it possible to create a more-public certificate that can only be used for puppetrun? We could use the ability to have developers

Hello... I need some help with tags. as an example: # pseudo code class ssh { file { "/etc/ssh/ssh_config": # normal stuff tag("dangerous") } file { "/etc/ssh/sshd_config": # normal stuff tag("dangerous") } file { "/etc/ssh/ssh_known_hosts": # normal stuff tag("safe") } } on client: puppetd --tags

Hi, I''m having trouble getting puppetrun to work, it returns: # puppetrun --debug --host serverb debug: Puppet::Network::Client::Runner: defining puppetrunner.run Triggering serverb debug: Calling puppetrunner.run warning: peer certificate won''t be verified in this SSL session err: Could not call puppetrunner.run: #<RuntimeError: HTTP-Error: 500 Internal Server Error >

I''m trying to wrap my head around these files... do both of them need to reside on the client and master? are there any docs that describe these files and what all the option/ sections are and what they do? Thanks all.... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

hi,all I want the puppetd run in daemon only run by the puppetrun trigger, not schedule run . so how can do this ? what''s the maximum of the runinterval ? I want change this option to do this. Please help me . -- Huang Mingyou

I''m getting the following error when trying to run puppetd on the server. I''m using version 0.23.2 from the dlutter repo. The OS is RHEL 5. Any idea what this is? I see reference to namespaceauth.conf regarding this problem but I can''t find anything definitive. [puppet]# puppetd -v -o err: Could not call puppetmaster.freshness: #<RuntimeError: HTTP-Error: 500