similar to: Design, syntax question for passing values from node.pp

I need a pointer in the right direction... Is there a document for migrating puppet/passenger to 3.0? -- Peter L. Berghold Salty.Cowdawg@gmail.com http://blog.berghold.net “"Don''t wait until everything is just right. It will never be perfect. There will always be challenges, obstacles and less than perfect conditions. So what. Get started now. With each

Got the following: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload package: Could not autoload /usr/local/lib/site_ruby/1.8/puppet/provider/package/windows.rb: no such file to load -- windows/error at /etc/puppet/modules/php/manifests/init.pp:28 on node This after I reverted back to puppet v2.7.11 on my master. Not running windows anywhere... why am I

Do I remember correctly that puppet-forge is no longer accepting uploads? -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to

Observe the following code sniget: user { nagios : comment => "Nagios Host Monitoring Service", shell => "/bin/bash", home => "/home/nagios", ensure => present } file { nagios-homedir : path => "/home/nagios", owner => "nagios",

Hi folks, I''m about to propose to my current company that we use puppet to manage releases of home grown software. The environment is a mix of Solaris 8/9/10 and RHEL 5&6. I''ve got a handle on how to create recipes to release software into the RHEL environment. The unknown for me is how to manipulate the pkgadd provider to load the locally grown package stream. Can

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 <<! !>>

Let me start by saying, I am a puppet rookie. I am trying to get a passenger module working and receive the following messages. I am trying to figure understand where the ''resource type '' should be? Or, defined? Is it another module that I should included under puppet/modules ? the message: _________________ ... debug: importing

I have this configuration: class monit { # Installing packages. package { "monit": ensure => latest; } file { "/etc/default/monit": owner => "root", group => "root", mode => "0644", source => "puppet:///monit/etc/default/monit", } file { "/etc/monit/monitrc": owner => "root", group =>

"The nice thing about standards is that there are so many to choose from." -- Andrew S Tannenbaum Debian does wonky things when you install a gem from "gem install." Usually this isn''t a problem unless there are executables to consider. I am running into that very thing with the "puppet-module" script on my laptop which runs a flavor of Debian. I thought I

Hi! Anyone knoe if it''s possible to realize resources with the spaceship operator checking for regex equality? Something like: User<| group =~ /(qa|prod)/ |> If not, anyone know of another way to do this sort of thing? Thanks a lot! Guy -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send

Might there be anything CentOS related on why I cannot access the Monit GUI system on http://box-running-monit.com:2812 ? I am using a very basic /etc/monit.conf config, but I cannot get it serve the web page on my box The service start and stops fine (e.g. "/etc/init.d/monit start"), and I have it set to listen to port 2812 in the "/etc/monit.conf file" (so far, kept the

Hi i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

I''m suddenly getting the below errors from Rack during puppetd -t (excerpted from the pink HTML output and cleaned for readability): Could not prepare for execution: Got 10 failure(s) while initializing: change from absent to directory failed: Could not set ''directory on ensure: Permission denied - /var/lib/puppet/yaml; change from absent to directory failed: Could not set

Hi all, I''d got the impression that puppet didn''t care about ordering - ie. the ordering of imports and includes related to calling them in the manifest. Lately I''ve had big trouble getting puppet to accept that I require some resource that I _have_ defined elsewhere in the manifest. To explain it, here is a simplified example: site.pp: -------- import

On one of my development servers mongrel dies when idle for any length of time. Since I''ve not been able to solve that problem I thought I''d route around it by using monit to kick things when necessary. My monitrc contains the following... -------------------------------------------------------------------------------- check process mongrel_8310 with pidfile

Anybody else experience the need to restart puppetmasterd before a node can register itself. I''ve been cleaning up my installation here on client nodes and every once and a while I find myself needing to restart the puppetmaster daemon. A client node attempts to connect and never does. A restart fixes things. There doesn''t seem to be anything useful in the error messages

Hello all, So, I''ve been using monit with mongrel for a while now, since the 0.3.x days (I think it was). It used to work fine, but now I seem to be having some trouble. I''m currently using mongrel 1.0.1 and I am using the same monit configuration I''ve always been using, yet everytime monit should restart mongrel, I get "Execution failed". For the start