Re: [Puppet Users] Re: Puppet + Nginx + Passenger: Certificate Request Problem

My working setup: puppet.conf [master] section has the following: > # Passenger SSL envvars > ssl_client_header = SSL_CLIENT_S_DN > ssl_client_verify_header = SSL_CLIENT_VERIFY applicable parts of nginx.conf: > env PATH > [...] > http { > [...] > > passenger_root /usr/lib/ruby/

Re: [Puppet Users] trouble with my virtual user setup

Hi, Can't test this, but isn't this declaration around the wrong way? # virtual.pp # class virtual_users::virtual I would expect: # virtual.pp # class virtual::virtual_users As I say, can't test before I reply. Cheers On 31/03/2011, at 7:33, MariaS wrote: > # virtual.pp > # > class virtua

[Puppet Users] Re: Puppet + Nginx + Passenger: Certificate Request Problem

On Tue, Mar 29, 2011 at 5:11 PM, Hugo Cisneiros (Eitch) < hugo.cisnei...@gmail.com> wrote: > Hi, > > I did a Puppetmaster installation using Nginx + Puppet and almost > everything is working. Almost :( > > When a new client is going to connect to the puppet server, it generates > its certificate a

[Puppet Users] Re: syntax error with case statment; in file type.

ok, dont bother answering the question about the other module... I got it straightened out... the logic was fubar I cut it down to a single file type, and service type with a few separators and it all works now. On Mar 30, 12:22 pm, trey85stang wrote: > Correction: > >   #  subscribe  => $higha

[Puppet Users] trouble with my virtual user setup

Hello, I'm a puppet newbie and I'm having trouble getting my virtual user setup to work. Can someone please tell me what's wrong with this setup? # virtual.pp # class virtual_users::virtual { @group { "users": gid=> "100", ensure => present } @user { "lmoore":

Re: [Puppet Users] Re: WEBrick, Passenger or Mongrel

On Mar 30, 2011, at 8:25 AM, hyzhang wrote: > Can someone please help me out here. I am stuck here. So I installed > everything. Then followed the instruction to set up rest from this > link: > http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger > > On "Configure Apache section" for R

[Puppet Users] Re: puppet client could not request certificate: Error 500 on SERVER

Thank. I am pasting the entire message here: Mar 30 14:01:04 puppetclient1 puppet-agent[28571]: Could not request certificate: Error 500 on SERVER: http://www.w3.org/TR/html4/strict.dtd";> Ruby (Rack) application could not be started

Re: [Puppet Users] puppet client could not request certificate: Error 500 on SERVER

On Wed, Mar 30, 2011 at 3:00 PM, hyzhang wrote: > Hi, I am new to puppet. > > I have puppet server set up with passenger. But when I start puppetd > from client, I see following error in the syslog file: > Mar 30 13:52:03 puppetclient1 puppet-agent[29732]: Could not request > certificate: Error 5

[Puppet Users] puppet client could not request certificate: Error 500 on SERVER

Hi, I am new to puppet. I have puppet server set up with passenger. But when I start puppetd from client, I see following error in the syslog file: Mar 30 13:52:03 puppetclient1 puppet-agent[29732]: Could not request certificate: Error 500 on SERVER: http://www.w3.org/TR/html4/strict.dtd";>

[Puppet Users] Re: syntax error with case statment; in file type.

sweet, got it fixed by using selectors instead of case Im going to add one more question to this thread since it appears to be syntax related as well... perhaps my logic is just a little fubar but, I have this module that the services complains that it cannot find the file dependencies: c

[Puppet Users] Re: syntax error with case statment; in file type.

Correction: # subscribe => $highavailability ? { #true => File["myapp"], #false => $hostname ? { # /$m[0-9]*/ => File["myapp1"], # /$s[0-9]*/ => File["myapp2"], #}, # }, On Mar 30, 12:20 pm, trey85stang wrote: > sweet,  got it fixed by using selectors inst

Re: [Puppet Users] Possible bug in configure script (torque 2.5.5)

> Wrong mailing list? Sure... I'm always thinking on puppet. sorry dudes! -- 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 puppet

Re: [Puppet Users] Possible bug in configure script (torque 2.5.5)

On Wed, 30 Mar 2011 18:24:50 +0200, Arnau Bria wrote: > > Hi all, > > it comes from another issue where David Beer is helping me, but > I faced a configure related issue when applying his solution: > > I should build torque 2.5.5 with : > > --with-tcp-retry-limit=2 > > After doing so, I shoul

[Puppet Users] Possible bug in configure script (torque 2.5.5)

Hi all, it comes from another issue where David Beer is helping me, but I faced a configure related issue when applying his solution: I should build torque 2.5.5 with : --with-tcp-retry-limit=2 After doing so, I should have a define in pbs_config.h, but it isn't: # grep -r TCP_RETRY_LIMIT src

Re: [Puppet Users] Re: RFC: Splitting up the file{} type functionality.

Am 29.03.2011 18:02, schrieb Nigel Kersten: On Tue, Mar 29, 2011 at 8:16 AM, Joe McDonagh wrote: I'd really prefer if the name of this resource didn't change. I understand there are problems but can't you just split the code and have different behavior based on something like filetype =>?

Re: [Puppet Users] wordpress.com and puppet, would they use it to update mysql db schema's also?

On 03/29/2011 06:52 PM, Richard Clark wrote: > On 29 March 2011 15:36, S Ahmed > wrote: > > Say for example wordpress.com uses puppet to > rollout the wordpress software for its customers. > > During updates to the software, say the

[Puppet Users] Re: WEBrick, Passenger or Mongrel

Can someone please help me out here. I am stuck here. So I installed everything. Then followed the instruction to set up rest from this link: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger On "Configure Apache section" for RHEL5, there is cp puppetmaster.conf /etc/httpd/conf.d/ (s

[Puppet Users] Disable masterhttp.log

I've got sufficient logging for my needs being written to /var/log/puppet/puppet.log On top of this, there's also /var/log/puppet/masterhttp.log which contains loads of stuff, and is getting large. Is there an easy way to disable this log file? I've had a quick search around but I can't see a

Re: [Puppet Users] Re: Simple class help

On 03/30/2011 05:05 PM, tigreton wrote: > So if i use content, and the file doesn't exist, the puppetmaster > *will* create it? Yes. -- 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@googlegroup

[Puppet Users] Re: Simple class help

So if i use content, and the file doesn't exist, the puppetmaster *will* create it? On 29 mar, 15:31, Felix Frank wrote: > Hi, > > On 03/29/2011 03:27 PM, tigreton wrote: > > > Thanks for your time Felix. I'm not clear hehe. > > So if i want to create a file and i musn't use content nor source, >

Re: [Puppet Users] syntax error with case statment; in file type.

On Mar 30, 2011, at 4:03 PM, trey85stang wrote: > I am getting a syntax error in a module and I'm not sure why... > > Anyone care to take a look? > > class audit { > file { "/etc/audit.rules": >owner => "root", >group => "root", >mode => 640, >case $operatingsystemrelease { >

[Puppet Users] syntax error with case statment; in file type.

I am getting a syntax error in a module and I'm not sure why... Anyone care to take a look? class audit { file { "/etc/audit.rules": owner => "root", group => "root", mode => 640, case $operatingsystemrelease { "10.2": { path => "/etc/audit.rules", source => "pu

[Puppet Users] Re: Changing NFS mount options to read only (ro) does not affect puppet change

On Mar 29, 8:00 pm, Forrie wrote: > Thanks for this information; this a somewhat a frustrating issue. > > IMHO, as per configuration management, if the mount options change, > then Puppet should "do the right thing" and umount and remount with > the proper options.  One problem there is what if s

[Puppet Users] Re: how puppet client update the files only when the flles from puppet server are new?

On Mar 29, 9:38 pm, metalove wrote: > Let's assume that > the file in the server was rollbacked to old data because of some > reason. > > then, puppet client will update also.. > > What I want is, > puppet client should reject the update in this case... > > so is there any option at puppet cline

Re: [Puppet Users] Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

I am unsure that necessity is the point. The discussion as I understand it is whether or not splitting up the file type would be helpful especially for those who are just coming to puppet. Would it help reduce confusion and lower the learning curve. While my background sees "everything as a file",

Re: [Puppet Users] Re: how puppet client update the files only when the flles from puppet server are new?

I think the fundamental problem here is that you see a particular piece of metadata in your mind (this version of the file is the previous version) which does not, in fact, exist. Since good practices dictate that your Puppet manifests, files, and templates are all in some form of version control,

Re: [Puppet Users] Re: [Puppet-dev] RFC: Splitting up the file{} type functionality.

I tend to use different defaults for the different types, so I would love to be able to do: File { mode => 0444 } Directory { mode => 0555 } This is not necessary at all. If you assign "mode => 444" to a directory, Puppet will automatically set the "execution" permission so