similar to: prerun_command don't stop puppet on error

Hello Everybody, We need to open some ports on the target machine, let''s say 694:udp and 3306:tcp I couldn''t find any documentation how can I do this with Puppet. What the best way of doing this? Thank you Dmytro -- 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''m looking for background information about how bug #7127[1] should be fixed: prerun_command don''t stop puppet on error I think there''s general agreement that if the prerun command fails, then the catalog should not be applied, but the report should be sent, and the report''s status should be "failed". However, what about the post-run

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

Hello , There is a way to source /etc/profile inside puppet on demand? My problem is that I install Java, afterwards I set JAVA_HOME variable in /etc/profile. After Java is installed, a gem which depends on Java starts to install ... but as it needs JAVA_HOME environment to be set, it fails. I am not sure what can I do ... Thank you, Adrian -- You received this message because you are

Hi I have just put puppet onto a new Ubuntu install and it ran a couple of times but now I get Execution of ''/etc/puppet/etckeeper-commit-pre'' returned 1: whenever puppetd runs. Grepping on etckeeper-commit turns up lots of posts to ubuntu and debian forums about changes made in February. Does anyone know what the story is? I''ve ended up with a screwed pam

Hello ! I''m trying to implement a Nagios solution based on David Schmitt''s Complete Config. But I the following error when running puppetd -t - v : notice: Starting catalog run err: //Node[monitoring]/nagios::target/Nagios::Host[]/File[/conf.d/ _host.cfg]/ensure: change from absent to present failed: Could not set present on ensure: No such file or directory - /conf.d/

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 all, I have installed and configure puppet client in new virtual machine, but I have this error when running *puppetd --test (even if I run /etc/init.d/puppet restart) /usr/lib/ruby/1.8/puppet/defaults.rb:136:in `handle'': Invalid environment test (ArgumentError) from /usr/lib/ruby/1.8/puppet/util/settings.rb:299:in `parse'' from

Hi, ppl I dont know what to do. I configure a new client do sync with my server. the server accept de client_cert without errors and then when i run the "puppet agent -t" agaion i got this error output info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server

I have very strange problem. I set up puppet client on serveral servers but have problem with one of them. When I invoke: root@www ~ # puppet agent --server puppetmaster.domain.ltd --test notice: Ignoring --listen on onetime run info: Caching catalog for puppetclient.domain.ltd info: Applying configuration version ''1326444431'' notice: Finished catalog run in

Just installed the puppet master server in and the client just installed the puppet I managed to sign the certificates root@Puppetmaster:/etc/puppet# puppet cert --list --all + "puppetclient" (96:9A:C3:8D:B6:72:A4:5F:01:AA:40:A9:95:3E:FB:D2) + "puppetmaster" (12:92:DF:EB:72:E5:DF:99:D8:22:CA:5F:22:3A:1D:61) at the time I create the file site.pp in / etc / puppet / manifests

I am using stored configs to manage my nagios host and services checks and I have run into a problem that I have been unable to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until

Couple of questions. Firstly, what''s the plugin error about? puppet agent --onetime --test --verbose info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from source(s) puppet://puppet/plugins info: Caching catalog for mon01.ap1.xxx.com info: Applying configuration version ''1346878830'' err:

Hi folks, For the first time since I started playing with puppet I started down the road of using exported resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>>

I did a fresh install on Ubuntu 12.04 with apt packages from puppet labs. I have agents talking to my puppetmaster. Puppetmaster is running apache/passenger connected to puppetdb and puppet-dashboard is setup to use puppetdb but it is not able to see any reports submitted to puppetdb. When an agent connects to master I see : Info: ''replace facts'' command for hostname

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

Package: logcheck-database Severity: normal Tags: patch The rules in /etc/ignore.d/server/nagios contain the explicit version number "2". Now that lenny includes nagios3, those rules don't work anymore. Please change the rules to work for both nagios2 and 3. That can easily be done by replacing the 2 by (2|3) for example. -- System Information: Debian Release: lenny/sid APT

Hello all, I'm trying to conect two asterisk servers using two B410p Digium cards. One card on each server. I just setting up the first BRI port on server A as nt_ptp and the first BRI port on server B as te_ptp. I use an ethernet wire to connect the first port of server A (nt_ptp) with the first port on server B (te_ptp) but the port light cotinues blinking on red on both sides once the

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

Here is my class class puppetconf { file { "/etc/puppet/puppetd.conf": mode => 644, owner => root, group => root, source => "puppet://puppet/cci/etc/puppet/puppetd.conf", notify => exec[puppet_restart] } file { "/etc/init.d/puppet": mode => 755, owner => root, group => root,