similar to: puppetrun error:ConfigurationError: Invalid pattern HOST

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.

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

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#

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 >

Hi, I''m rolling out a new Puppet install and am having some problems with certs. I''ve googled and read the docs but can''t find anything. Almost all boxes on the network are dual-homed, with a primary network (VLAN, /27 subnet) for public data and an admin/management network for backups and other backend stuff. All hosts have a primary interface on the main network (and

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

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

Can''t seem to make it work puppet 2.6.8 (client/server) # puppet kick -f ubuntu4.ttinet Triggering ubuntu4.ttinet Host ubuntu4.ttinet failed: Error 400 on SERVER: ''save '' is not an allowed value for method directive ubuntu4.ttinet finished with exit code 2 Failed: ubuntu4.ttinet root@ubuntu4:~# cat /etc/puppet/auth.conf path /run method save allow *

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

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

I want to use puppetrun so I added --listen to the puppetd command-line. Puppetd would run and then immediately exit. I couldn''t figure out the cause because there was nothing in the logs. I finally figured it out when I ran it with --verbose. # puppetd --listen --verbose Will not start without authorization file /etc/puppet/namespaceauth.conf My guess is that the fatal message is

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

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, Now that I can run my client with the --silent and --no-client option, Id like to centralize the logs on my puppet server and not on my puppet clients. The problem is that so far I havent found an option to tell puppetrun to get the logs back on my server. Is that possible to do such a thing with puppetrun? (running on v.0.18.4) Thanks in advance. -- Jean-Christophe Lacaze Ministry

Hi. I have a trouble that disabling automountd on Solaris10. So could you tell me what I should do to fix this trouble. [Environment] Puppetmasterd -version : 0.25.3 -OS : Solaris10 10/09 Puppetd -version : same as Puppetmasterd -OS : same as Puppetmasterd [What I did & trouble detail] 1.Edit manifest file. service { ''autofs'': ensure =>

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

YASP... Yet Another SSL Problem, this time on puppetrun. $ sudo puppetrun -p 10 --host anotherhost -t aze Failed to load ruby LDAP library. LDAP functionality will not be available Triggering anotherhost Host anotherhost failed: Certificates were not trusted: tlsv1 alert unknown ca anotherhost finished with exit code 2 Failed: anotherhost Running with "strace -f" shows that

I just started playing with puppet. Unfortunately, it keeps crashing in a variety of places. I don''t have much experience with Ruby yet, so any tips in tracking down these problems would be appreciated. I''m using the Debian package 0.18.4-1. Here''s the output of a couple runs: www01:/home/cwarden# puppetd --verbose --onetime info: Caching configuration at

Hi While running puppetrun on my master server, i receive the following error on the client host for which puppetrun has been run: err: Could not retrieve catalog: Could not find terminus plain for indirection node Please help what needs to be done for the same. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

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