similar to: Steps for recipe

Displaying 20 results from an estimated 40000 matches similar to: "Steps for recipe"

2007 Jun 05
3
custom type, recipe, how to solve this ?
Hi, I have a little trickky thing i wanted to do with puppet, mainly this is configuring web host on servers. I have a tree like this : NODE - WEB -APACHE - 1.x - 2.x - FTP - VSFTP - PROFTPD - STATS -AWSTATS - if FTP then configure awstats for awstats - URCHIN5 So my issue is that i want to be able to have
2007 Feb 20
5
Recipe for Apache2 on Debian (Etch)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Tim, *! Thank you for posting your nice apache2 recipe to the wiki! It''s really good to see how others make things happen and a good example for others. One little thing though caught my notice because I''m currently making the same naughty thing on Simple Text Recipes. There is no ensure attribute. Since you already have done
2010 Mar 04
3
Dependency cycles, please help.
Hi, I''m having trouble writing a recipe to handle apache/passenger. First, here is my apache2 class, found here : http://www.reductivelabs.com/trac/puppet/wiki/Recipes/DebianApache2Recipe --------------------------------------------- $apache2_sites = "/etc/apache2/sites" $apache2_mods = "/etc/apache2/mods" class apache2 { [...] define module ( $ensure =
2009 Jun 02
0
OSSEC Recipe?
Hi, I''m a fairly new to Puppet but so far have been very pleased with the recipes and my own simple scripts. However, I''ve hit a wall in the form of OSSEC, (http://www.ossec.net/main/) Most of my servers are running ubuntu or debain and neither support OSSEC via apt-get. I''ve thought about setting up my own local repository to handle this and to also package my own
2010 Aug 07
0
Recipe for Debians MySQL
Hiya Would anyone have a recipe for Debian''s MySQL. Thats to install and configure (i.e. root password). Kind Regards Brent Clark -- 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
2007 Dec 20
5
Apache2 module -- feedback appreciated
Hey folks, I''ve just uploaded an apache2 module[1] to our Google Code repository[2]. It''s based largely on the recipe available on the Puppet trac[3], but with a fair amount of modification and generalization... Basically, it provides abstractions for config file snippets, site definitions, and apxs modules -- and then "basic" and "debian"
2007 Oct 09
2
Failure to find definition
Hi, I''m trying to set up apache2 under puppet, as in this recipe: http://reductivelabs.com/trac/puppet/wiki/Recipes/DebianApache2Recipe I have a file "apache2.pp" as shown there, and then a webserver.pp file (see below). On running puppetd on the client, I get this message: err: Could not retrieve configuration: Could not find definition site in file
2007 Oct 31
2
Managing apache authentication
Hi there. I''m trying to wrap my head around puppet and its parlance and need some guidance... 2 Questions: 1) I have done some puppet stuff on a new server and would like to hear whether I have done things "the right way" 2) I want to build on top of that and am not sure how... Question 1 ========== We don''t normally host static websites for people, but have been
2012 Jan 15
1
puppet client server connection refused when I use puppet kick
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
2012 Oct 30
3
Could not parse for environment production: Syntax error at '{'; expected '}' at
Hi, ppl, I m following the puppet cookbook tutorial. On page 167 to 169 Managing Apache Servers. When I add the: apache::snippet { "site-specific.conf": } I got the error of the title: Could not parse for environment production: Syntax error at ''{''; expected ''}'' at /etc/puppet/manifests/nodes.pp:3. Here is my manifests node.pp
2012 Sep 18
1
How can i get directory recursively?
In manifest i have this instruction: file { "/etc/apache2": owner => root, group => root, mode => 740, recurse => true, source => "puppet:///dist/apache2" } By syntax its right, but on client i see error: err: /Stage[main]/Testing170/File[/etc/apache2]: Failed to generate additional resources using
2013 Jan 31
1
The way Puppet installs things fail
Basically, the way puppet installs things things with /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install <package_name> fails due to authentication WARNING: The following packages cannot be authenticated But if I do it from an ssh console normally, using apt-get install <package_name> it works fine without issues. Is there a way to change how puppet uses the
2013 Jul 22
0
wyrie/puppet-nagiosql -- anyone have experience with this module?
I made two decisions this afternoon that are now related to each other. 1. Use more of the modules that exist in the Forge 2. Rebuild my monitoring server As I perused the various modules that help with managing monitoring packages my eyes fell upon a module that reported to be able to manage nagiosql, a setup that I had been planning on migrating my nagios monitoring to. So I installed
2008 Jun 27
0
408 Request Timeout
Dear puppet masters, I''m having frequent timeout errors reported from my puppet clients in syslog: Jun 27 01:23:41 nc82 puppetd[9089]: Could not call fileserver.describe: #<RuntimeError: HTTP-Error: 408 Request Timeout > Jun 27 01:23:41 nc82 puppetd[9089]:
2012 Mar 13
2
vhost creation with and without ssl
Hello, I have this defined resource type which is working perfectly until I want an ssl an http vhost pointing to the same directory in which case the unique $servername variable became a singleton Do you have any idea how to get around this? I am pretty tired at the moment and cant think of any good solution. define vhost ($servername = "${hostname}.${domain}", $serveralias = [
2010 Aug 20
5
puppet dashboard gui looks odd from apache2
I downloaded the puppet-dashboard.git from http://github.com/puppetlabs/puppet-dashboard and did the installation in my ubuntu lucid puppet server following the steps in "Installation". Now I can run it fine using the WEBrick like this root@sys-ubuntu { ~/git/puppet-dashboard }$ ./script/server -e production => Booting WEBrick => Rails 2.3.5 application starting on
2009 Sep 03
2
Even the "Simplest Puppet Install Recipe" apparently isn't simple enough
I''ve tried this over and over, and I just cannot get it to work. I''m trying to do a proof of concept on puppet, so I''m using two CentOS 5.3 systems running in VMs on separate hardware (i.e. the two VMs are not on the same physical box). I''ve built the systems from scratch numerous times, and then pulled down puppet from the rpmforge repo. In the course of
2010 Jul 29
1
Could not find resource type ...
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
2009 Sep 10
2
passenger with ruby enterprise edition
Hi I am failing to start apache2 with ruby enterprise edition and passenger 2.2.5 [Wed Sep 09 17:38:20 2009] [notice] Apache/2.2.11 (Ubuntu) mod_ssl/2.2.11 OpenSSL/0.9.8g Phusion_Passenger/2.2.5 configured -- resuming normal operations *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (no such file to load -- puppet) (process 16544): from
2007 Nov 29
5
Solaris Zone site.xml recipe
I was finally able to get ldapnodes [1] working on our puppetmaster so i''m able to start working on the fun stuff. In the last few days it has become critical that we come up with a better way to manage the configuration of our Solaris zones. I am planning to write a recipe that provisions the zone [using the zone resource type], but would like to avoid having to keep a stockpile