[Puppet Users] Researching Puppet - Local host variations

[thinkwell]

Hello everyone,

First-time poster investigating Puppet for managing CentOS-based
firewall distros at various locations. I have approximately 130
machines to administrate so some type of config management is
certainly needed.

I've been working through Puppet tutorials and I'm wondering if Puppet
will do what I need; all machines are very similar. However each
machine will have small differences. For example,

1. SSH Ports: Machines have custom SSH ports so that's one variable
that would prevent me from just copying sshd_config.

2. Squid ACLs: All machines will have certain Squid ACLs, but many
machines will vary otherwise, say in cache size for example.

3. Iptables: All machines have standardized Iptables rules in /etc/
rc.d/rc.firewall.local. But again each machine has rules on a per-host
basis.

Originally, what I thought I could do is have certain sections of the
config files managed by Puppet, with other sections managed by local
edits on a per-host basis. But I'm gathering that's not how Puppet
works - you manage the whole config file and apply various config
versions based on Facter facts, node types, etc. If that's my only
option, I'll have to maintain custom conf files on Puppetmaster for
every host!

I'm open to advice generally, and comments specifically on how to
manage small per-host variations. Create custom Facter conditionals
for hosts?

Thanks!

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Struggle with erb syntax

[thinkwell]

Hello everyone,

I'm new to puppet & ruby - some experience with Python. I'm working at
getting some templates coded with hashes & conditionals, and using a
contrived example here to get myself started:

This works as I expect in ruby code:

pets = {"snakes"=>["python", "boa constrictor"], "kitties"=>["tomcat",
"pussycat"], "puppies"=>["akitas", "collies", "german shepherds"]}

for pet in pets.keys
puts pet
for pt in pets[pet]
if pet == 'snakes' then
puts "#{pt} is in the #{pet} family"
end
end
end



So, that's the output I want in my ERB template, which is created
thusly:
<% for pet in pets.keys %>
<%= pet %>
<% for pt in pets[pet] %>
<% if pet == 'snakes' then %>
<%=  "#{pt} is in the #{pet} family" %>
<% end %>
<% end %>
<% end %>

However, no matter how I fiddle the syntax, I always get:
err: Could not retrieve catalog from remote server: wrong header line
format


What am I doing wrong?

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Researching Puppet - Local host variations

[thinkwell]

I'm getting this worked through in my head, I think. I wanted to make
sure that Puppet would totally support me if the migration is made.
I've concluded that I can standardize a bit more than I have, and with
Daniel's suggestion, quoted below, I'm well impressed! :

file {
"/etc/rc.d/rc.firewall.local": source =>
"puppet:///modules/firewall/rc.firewall.${fqdn}"  }

That's just perfect - allows very granular "per machine" edits that'll
streamline workflow 100%. Thanks for the comments everyone! :-)

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Struggle with erb syntax

[thinkwell]

Well, harrumph. Scratchin' mah head - totally baffled, perplexed. I
went to eat and gave it a break. Came back and re-verified syntax
checks. Syntax OK - just as before. Ran puppet validate for the first
time with no errors.

Then, for kicks and giggles, I again to apply the config to the node.
Shazzam - it worked; yet I had made no changes. :-( Very nice it's
working, but why the earlier "err: Could not retrieve catalog from
remote server: wrong header line
format" that cost me so much time? Seems buggy, but I reckon it's me,
the learning puppet user.

Question: what are some debugging tips & tricks that you experts use
when developing new module classes & templates, especially when the
errors messages are so vague? What can I learn from this incident?

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: CentOS 5 packages in EPEL are outdated ?

[thinkwell]

Use the rpmforge repos. That version is 2.7.9

http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-5aabf02717d5b6b12d47edbc5811404998926a1b

On Tuesday, March 13, 2012 5:29:54 AM UTC-4, Julien C. wrote:
>
> Answering to myself: no 2.6.14 doesn't send reports.
> I'll have a look at yum.puppetlabs.com
>
> Le mardi 13 mars 2012 10:16:11 UTC+1, Julien C. a écrit :
>>
>> Hi,
>>
>> I tried using EPEL repositories as stated here: 
>> http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Red_Hat_Centos
>> The Puppet version there is 2.6.14 or did I miss something?
>>
>> My concern is: will I have reports with that version? I'm using dashboard 
>> to keep an eye on my deployment and I need to know if there is a problem 
>> without checking on each server...
>>
>> Regards,
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Y8rG9Sk_SPwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet master on Centos 5.4 box

[thinkwell]

Hello everyone,

I'm trying to setup a Puppetmaster on a Centos 5.4 box, following
James Turnbull's "Pro Puppet" book. Everything's working fine, until I
get to the part about running Passenger, which I'll need to do.

However, to install rake, I had to upgrade ruby from the default
1.8.5. I tried uninstalling 1.8.5 & puppet altogether, installed 1.8.7
successfully. So, now I'm using RVM running ruby 1.8.7. When I went to
re-install puppet, yum insisted ruby 1.8.1> was a dependency and
refused to installed without also installing the old system ruby.

I thought I had things configured correctly, but when I connect via a
client, I get the following error:


Ruby (Rack) application could not be started

A source file that the application requires, is missing.
It is possible that you didn't upload your application files
correctly. Please check whether all your application files are
uploaded.
A required library may not installed. Please install all libraries
that this application requires.
Further information about the error may have been written to the
application's log file. Please check it in order to analyse the
problem.
Error message:
no such file to load -- puppet/application/master
Exception class:
LoadError
Application root:
/etc/puppet/rack/puppetmaster
Backtrace:
#   FileLineLocation
0   /usr/local/rvm/rubies/ruby-1.8  36  in `gem_original_require'
1   /usr/local/rvm/rubies/ruby-1.8  36  in `require'
2   config.ru   13
3   /usr/local/rvm/gems/ruby-1.8.7  51  in `instance_eval'
4   /usr/local/rvm/gems/ruby-1.8.7  51  in `initialize'
5   config.ru   1   in `new'
6   config.ru   1



This is not terribly surprising, since yum installed puppet to
/usr/lib/ruby/site_ruby/1.8/puppet/

I tried moving that directory & /usr/lib/ruby/site_ruby/1.8/puppet.rb
to /opt/puppet/lib/ with the same error message resulting.

It's infuriating. Is it possible to run puppet with multiple versions
of ruby installed?

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet master on Centos 5.4 box

[thinkwell]

Ahah. That's my mistake - gem install puppet - it is, then.

 

> 
> at the point you install rvm and with it various ruby versions then all of 
> the ruby gems that you install cannot be from centOS packaging but rather 
> would have to be using the specific ruby version and gem version.
>
> Thus you should do things like...
>
> gem install puppet
> gem install passenger
> etc.
>
> Craig
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/doMKyhqJkNgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Cron job isn't running

[thinkwell]

I only need to run puppet weekly, so I made this little shell script and 
put in the the /etc/cron.weekly folder, but it's not running. If I run the 
script manually, it works just fine. Why not from cron?



#!/bin/bash

#
# Cron job managed by Puppet
#


# Randomize 15 minutes to avoid overloading server
sleep $((RANDOM % 900))
exec puppet agent --no-daemonize --onetime

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Ccx8LJ7QCRMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Cron job isn't running

[thinkwell]

Ahah, I made a custom FACTER variable in my .bashrc file and that bash 
environment variable isn't run by cron.  So that's my problem... I'll need 
to research how to pass a custom FACTER variable to a cron script and have 
it be accessible at script run time.




On Thursday, April 19, 2012 3:43:16 PM UTC-4, thinkwell wrote:
>
> I only need to run puppet weekly, so I made this little shell script and 
> put in the the /etc/cron.weekly folder, but it's not running. If I run the 
> script manually, it works just fine. Why not from cron?
>
>
>
> #!/bin/bash
>
> #
> # Cron job managed by Puppet
> #
>
>
> # Randomize 15 minutes to avoid overloading server
> sleep $((RANDOM % 900))
> exec puppet agent --no-daemonize --onetime
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/pN4AXumKJeYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Puppet broken in upgrade from 3.0.1 to 3.1.0

[thinkwell]

Hello everyone,

Recently puppet was upgraded from 3.0.1 to 3.1.0 when I did a sudo apt-get 
update on my Kubuntu server.

Now, I'm getting the following error 
when running puppet. My config.ru 
file is the same as the source3.1.0 
config.ru 
file
.

So I'm scratching my head. My apache error log only shows:

[code]
[Wed Feb 06 11:37:08 2013] [warn] RSA server certificate CommonName (CN) 
`' does NOT match server name!?
[/code]
But that apparently didn't prevent puppet from functioning for quite some 
time, since I found I was getting that error months ago.
[code]
[Sun Dec 09 07:57:49 2012] [warn] RSA server certificate CommonName (CN) 
`' does NOT match server name!?
[/code]

Anybody have some help for me?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet broken in upgrade from 3.0.1 to 3.1.0

[thinkwell]

My problem is now resolved... Thanks for your replies, Dominic and Johan. 

I'm not using puppet to manage the puppet server, but in the course of 
troubleshooting, I tried running puppet agent -t on the puppet server. This 
gave me a certificate mismatch error and when I deleted the old certificate 
and created & signed a new one, everything worked.

Sorta puzzles me. Why would this mismatched agent certificate on 
puppetmaster interfered with other puppet agent runs?


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet broken in upgrade from 3.0.1 to 3.1.0

[thinkwell]

Yes, I do have a hardcoded certificate name in my master section. That's 
why I my agent cert issue was so unexpected. Oh well, I guess all's well 
that ends well. 

I just think I'll disable the repo and not do upgrades for a long time, now 
that I'm at 3.1. These little glitches make little grey hairs after awhile 
and snip off a few minutes of life expectancy. Speaking in generalites, of 
course. Puppet is wonderful. : -)


On Friday, February 8, 2013 3:39:41 PM UTC-5, Jo wrote:
>
> On Feb 7, 2013, at 5:50 AM, Dominic Cleal wrote:
>
> Sorta puzzles me. Why would this mismatched agent certificate on
>
> puppetmaster interfered with other puppet agent runs?
>
>
> The same certificate that is used for the agent on the master server is
> also used for the master process itself (inbound connections).
>
>
> Only if you let your puppet server use the host it's running on FQDN, 
> which I devoutly disagree with in practice. Best to keep them separate by 
> putting a hardcoded certname in the [master] section to avoid these kinds 
> of problems.
>
> -- 
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet broken in upgrade from 3.0.1 to 3.1.0

[thinkwell]

Well, this problem continues to harass me. I have to recreate an agent 
certificate on the puppet master after every reboot before puppet agents 
will update successfully. 

What am I doing wrong?

On Wednesday, February 6, 2013 2:43:44 PM UTC-5, Johan De Wit wrote:
>
>  On 02/06/2013 05:46 PM, thinkwell wrote:
>  
> Hello everyone,
>
> Recently puppet was upgraded from 3.0.1 to 3.1.0 when I did a sudo apt-get 
> update on my Kubuntu server.
>
> Now, I'm getting the following error 
> <http://thinkwelldesigns.com/puppet.html>when running puppet. My 
> config.ru file <http://thinkwelldesigns.com/config.txt>is the same as the 
> source 3.1.0 config.ru 
> file<https://github.com/puppetlabs/puppet/blob/3.1.0/ext/rack/files/config.ru>
> .
>
> So I'm scratching my head. My apache error log only shows:
>
> [code]
> [Wed Feb 06 11:37:08 2013] [warn] RSA server certificate CommonName (CN) 
> `' does NOT match server name!?
> [/code]
> But that apparently didn't prevent puppet from functioning for quite some 
> time, since I found I was getting that error months ago.
> [code]
> [Sun Dec 09 07:57:49 2012] [warn] RSA server certificate CommonName (CN) 
> `' does NOT match server name!?
> [/code]
>
> Anybody have some help for me?
>
> Thanks!
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users...@googlegroups.com .
> To post to this group, send email to puppet...@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>
> have you checked your /etc/puppet/puppet.conf, could be overwritten by the 
> upgrade ?
>
>
> -- 
> Johan De Wit
>
> Open Source Consultant 
> Red Hat Certified Engineer(805008667232363)
> Puppet Certified Professional 2013 (PCP006)
> _
>
> Open-Future   Phone   +32 (0)2/255 70 70
> Zavelstraat 72Fax +32 (0)2/255 70 71
> 3071 KORTENBERG   Mobile  +32 (0)474/42 40 73
> BELGIUM   http://www.open-future.be
> _
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Ruby (Rack) application could not be started

[thinkwell]

Hello Ramin. Thanks for your reply. I didn't install rvm, I'm only using 
system ruby.  Regarding the use of gems vs puppet repositories, well, I 
installed Puppet from the official apt repos but I wasn't aware that 
passenger can be installed from there as well. If that's the case, why is 
the documentation <http://docs.puppetlabs.com/guides/passenger.html>so out 
of date? 

I removed all my gems, installed puppetmaster-passenger & ruby-rack from 
apt, and get this output (G):

Setting up ruby-rack (1.3.5-1) ...
Setting up librack-ruby (1.3.5-1) ...
Setting up libapache2-mod-passenger (2.2.11debian-2) ...
Setting up puppetmaster-passenger (3.1.1-1puppetlabs1) ...
Module ssl already enabled
Module headers already enabled
Enabling site puppetmaster.
To activate the new configuration, you need to run:
  service apache2 reload
Syntax error on line 3 of /etc/apache2/sites-enabled/puppetmaster:
Invalid command 'PassengerHighPerformance', perhaps misspelled or defined 
by a module not included in the server configuration
Action 'configtest' failed.
The Apache error log may have more information.
   ...fail!
invoke-rc.d: initscript apache2, action "restart" failed.
dpkg: error processing puppetmaster-passenger (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 puppetmaster-passenger

*
What is the recommended way to configure Puppet 3.1.1 with Apache!!?*

On Monday, March 25, 2013 11:05:14 PM UTC-4, Ramin K wrote:
>
> On 3/25/2013 7:04 PM, thinkwell wrote: 
> > My puppet master server got torched so I'm rebuilding - ubuntu 12.04.2 
> LTS. 
> > 
> > After fiddling / tweaking / reading docs 
> > <http://docs.puppetlabs.com/guides/passenger.html> for hours now and I 
> > am reduced to hair-pulling frustration. 
> > 
> > I'm endeavoring to install 3.1.1 (3.0.2 on the old server) and I'm 
> > getting "Ruby (Rack) application could not be started 
> > <http://thinkwelldesigns.com/errors2.html>" errors. I updated my 
> > config.ru <http://thinkwelldesigns.com/config.txt> file with the 3.1 
> > source 
> > <
> https://github.com/puppetlabs/puppet/blob/master/ext/rack/files/config.ru>. 
>
> > 
> > 1. I'm not getting errors in the /var/log/apache2/errors.log as the 
> > error message hints I should. 
> > 2. I tried my certs from my backup. 
> > 3. I tried recreating server certs, but no change. 
> > 
> > I don't manage my puppet master with puppet, so I came on this discovery 
> > very late. For whatever it's worth. 
> > 
> > 1. Installed puppet agent on the puppet master. 
> > 2. Ran puppet agent -t to generate an agent certificate 
> > 3. Get this error: 
> > 
> > Error: Could not request certificate: Error 500 on SERVER:  > HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 
> >  
> > 500 Internal Server Error 
> >  
> > Internal Server Error 
> > The server encountered an internal error or 
> > misconfiguration and was unable to complete 
> > your request. 
> > Please contact the server administrator, 
> >   [no address given] and inform them of the time the error occurred, 
> > and anything you might have done that may have 
> > caused the error. 
> > More information about this error may be available 
> > in the server error log. 
> >  
> > Apache/2.2.22 (Ubuntu) Server at puppet Port 8140 
> >  
> > 
> > 
> > here is my gem list which shows rack is installed. 
> > *** LOCAL GEMS *** 
> > 
> > activemodel (3.2.13) 
> > activerecord (3.2.13) 
> > activesupport (3.2.13) 
> > arel (3.0.2) 
> > builder (3.0.4) 
> > daemon_controller (1.1.2) 
> > fastthread (1.0.7) 
> > i18n (0.6.1) 
> > multi_json (1.7.2) 
> > passenger (3.0.19) 
> > rack (1.5.2) 
> > rake (10.0.4) 
> > tzinfo (0.3.37) 
> > 
> > Many thanks for your assistance. I'm about maxed out. :-( 
>
> Your gem listing makes me thing you've installed Ruby inside rvm, is 
> that the case? If so, you'll need to install Puppet within the same Ruby 
> as the one the passenger.so resides in and is configured in 
> /etc/apache2/mod-enabled/passenger.{conf,load} 
>
> fwiw, you may find it simpler to use the distro packages though I would 
> pull in the official Passenger 3.x repo from apt.brightbox.net as well 
> as apt.puppetlabs.com 
>
> Ramin 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Ruby (Rack) application could not be started

[thinkwell]

Still no luck. Installed from gems, installed from Puppet Apt, installed 
from brightbox. Some thing must be busted for each one. Puppet runs always 
generating scads of errors .

Is Passenger enabled? I had to create these files manually since the 
packages from brightbox didn't. I guess the settings are correct

Contents of /etc/apache2/mods-available/passenger.conf:
PassengerRoot /usr/lib/ruby/1.8/phusion_passenger
PassengerRuby /usr/bin/ruby1.8

Contents of /etc/apache2/mods-available/passenger.load:
LoadModule passenger_module /usr/lib/apache2/modules/mod_passenger.so

This. Is. Getting. To. Be. One. *S**crming.* Pain. 

Thanks for your help Ramin, but why oh why can't we have up-to-date 
documentation that gives correct step-by-step installation directions?  How 
esoteric does this have to be?

On Tuesday, March 26, 2013 1:35:19 PM UTC-4, Ramin K wrote:
>
>
> However in your current case I'd make sure that the Passenger module has 
> been enabled. When Apache thinks a command is invalid it's almost always 
> that the module the command is meant to config is not enabled or loaded. 
>
> Ramin 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] One client out of 150 doesn't apply config changes

[thinkwell]

Hello everyone,

I have one puppet client that suddenly stopped applying configuration 
changes during the. I'm running with -v to see errors - no errors are shown 
and the puppet run completes with:

info: Caching catalog for 
info: Applying configuration version '1349982313'
notice: Finished catalog run in 49.28 seconds

However, the changes required aren't made. This only happens on one client 
out of 150+ so it seems to be a client error. Is there some puppet cache 
that I need to clear?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/tIPYTLDRp68J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Upgrading puppet 2.7.19 to 3.0.1

[thinkwell]

Hello everyone. I'm asking this question with reluctance; but I've been 
working on this upgrade for most of the day. I had a working Kubuntu 12.04 
puppet master 2.7.19 with most clients at 2.7.19 as well. I'm trying to 
upgrade the puppetmaster to 3.0.1 for the speed improvements. Upgrading via 
apt generated unwelcome errors that I need not go into here. Let's just say 
that I uninstalled all ruby versions & ruby gems and started from scratch.

So now I have puppet 3.0.1 installed from the puppetlabs debian repo and I 
thought I'd fought my way through the thicket, but I've hit a wall with 
this error When running puppet agent on the clients. I get the following 
error:

Ruby (Rack) application could not be started


*Error message:*undefined method `settings' for Puppet:Module*Exception 
class:*NoMethodError*Application root:* /etc/puppet/rack/puppetmaster
*Backtrace:*  # File Line Location  0   
/usr/lib/ruby/vendor_ruby/puppet/application.rb273  in `run_mode'  1   
/usr/lib/ruby/vendor_ruby/puppet/application/master.rb5 
 2   /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb36 in 
`gem_original_require'  3   
/usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb36 in `require'  
4   config.ru13 
 5   /var/lib/gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb46 in 
`instance_eval'  6   /var/lib/gems/1.8/gems/rack-1.1.0/lib/rack/builder.rb
46 in `initialize'  7   config.ru1 in `new'  8   config.ru

My puppetmaster site and conf files are attached. I'd be under many 
obligations for some help.

TIA,

Dave

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/3BNJL8OuZVsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.


# you probably want to tune these settings
PassengerHighPerformance on
PassengerMaxPoolSize 12
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
RackAutoDetect Off
RailsAutoDetect Off

Listen 8140


SSLEngine on
SSLProtocol -ALL +SSLv3 +TLSv1
SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP

#SSLCertificateFile  
/var/lib/puppet/ssl/certs/bearkub.thinkwell.lan.pem
SSLCertificateFile  
/var/lib/puppet/ssl/certs/puppet.thesecurityappliance.com.pem
SSLCertificateKeyFile   
/var/lib/puppet/ssl/private_keys/bearkub.thinkwell.lan.pem
SSLCertificateChainFile /var/lib/puppet/ssl/certs/ca.pem
SSLCACertificateFile/var/lib/puppet/ssl/certs/ca.pem
# If Apache complains about invalid signatures on the CRL, you can try 
disabling
# CRL checking by commenting the next line, but this is not recommended.
SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem
SSLVerifyClient optional
SSLVerifyDepth  1
# The `ExportCertData` option is needed for agent certificate 
expiration warnings
SSLOptions +StdEnvVars +ExportCertData

# This header needs to be set if using a loadbalancer or proxy
RequestHeader unset X-Forwarded-For

RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e

DocumentRoot /usr/share/puppet/rack/puppetmasterd/public/
RackBaseURI /

Options None
AllowOverride None
Order allow,deny
allow from all




LoadModule passenger_module 
/var/lib/gems/1.8/gems/passenger-2.2.11/ext/apache2/mod_passenger.so
PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
PassengerRuby /usr/bin/ruby1.8

# Recommended Passenger Configuration
PassengerHighPerformance on
PassengerUseGlobalQueue on
# PassengerMaxPoolSize control number of application instances,
# typically 1.5x the number of processor cores.
PassengerMaxPoolSize 10
# Restart ruby process after handling specific number of request to resolve MRI 
memory leak.
PassengerMaxRequests 4000
# Shutdown idle Passenger instances after 30 min.
PassengerPoolIdleTime 1800
# End of /etc/httpd/conf.d/10_passenger.conf

# /etc/httpd/conf.d/20_puppetmaster.conf
# Apache handles the SSL encryption and decryption. It replaces webrick and 
listens by default on 8140
Listen 8140


SSLEngine on
SSLProtocol -ALL +SSLv3 +TLSv1
SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
# Puppet master should generate initial CA certificate.
# ensure certs are located in /var/lib/puppet/ssl
# Change puppet.example.com to the fully qualified domain name of the Puppet 
master, i.e. $(facter fqdn).
SSLCertificateFile /var/lib/puppet/ssl/certs/puppet.thesecurityappliance.com.pem
SSLCertificateKey

Re: [Puppet Users] Upgrading puppet 2.7.19 to 3.0.1

[thinkwell]

I am using the new config.ru file now; thanks for the tip. Where is the 
puppetmaster init script? As I mentioned, I'm starting over from scratch so 
I deleted the init scripts from the 2.7.19 install, but installing  3.0.1 
didn't include an init script. Very strange.

Are there any docs I can read regarding the configuration of 3.0.1 from 
soup-to-nuts?  For 2.7.19 I used Turnbull's Pro Puppet book but that not 
getting me going in 3.0. 

On Tuesday, October 30, 2012 10:15:46 PM UTC-4, Andreas Ntaflos wrote:
>
> On 2012-10-31 03:01, thinkwell wrote: 
>  > So now I have puppet 3.0.1 installed from the puppetlabs debian repo 
> and 
> > I thought I'd fought my way through the thicket, but I've hit a wall 
> > with this error When running puppet agent on the clients. I get the 
> > following error: 
> > 
> > 
> >   Ruby (Rack) application could not be started 
> > 
>
> Just an idea, are you using the config.ru file updated for 3.0, provided 
> by the puppet-common package? Should be in 
> /usr/share/puppet/ext/rack/files/config.ru or 
> /usr/share/puppet/rack/puppetmasterd/config.ru. 
>
> Andreas 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/mQl06YvHwboJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Upgrading puppet 2.7.19 to 3.0.1

[thinkwell]

Hey, hey, hey. Never mind. I had the application root wrong. Changed 2 
things at once as I noticed a few other settings were wrong when I updated 
the config.ru file. Got the application root wrong in the process. Now I'm 
going again!

On Wednesday, October 31, 2012 10:39:08 AM UTC-4, thinkwell wrote:
>
> I am using the new config.ru file now; thanks for the tip. Where is the 
> puppetmaster init script? As I mentioned, I'm starting over from scratch so 
> I deleted the init scripts from the 2.7.19 install, but installing  3.0.1 
> didn't include an init script. Very strange.
>
> Are there any docs I can read regarding the configuration of 3.0.1 from 
> soup-to-nuts?  For 2.7.19 I used Turnbull's Pro Puppet book but that not 
> getting me going in 3.0. 
>
> On Tuesday, October 30, 2012 10:15:46 PM UTC-4, Andreas Ntaflos wrote:
>>
>> On 2012-10-31 03:01, thinkwell wrote: 
>>  > So now I have puppet 3.0.1 installed from the puppetlabs debian repo 
>> and 
>> > I thought I'd fought my way through the thicket, but I've hit a wall 
>> > with this error When running puppet agent on the clients. I get the 
>> > following error: 
>> > 
>> > 
>> >   Ruby (Rack) application could not be started 
>> > 
>>
>> Just an idea, are you using the config.ru file updated for 3.0, provided 
>> by the puppet-common package? Should be in 
>> /usr/share/puppet/ext/rack/files/config.ru or 
>> /usr/share/puppet/rack/puppetmasterd/config.ru. 
>>
>> Andreas 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/4ht0Jvu-ijQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Console color in 3.0.1

[thinkwell]

A trivial post, perhaps, but I liked the console coloring of 2.7 much 
better than 3.0. Is there a way to get the 2.7 coloring back or to 
customize the console color scheme?

TIA,

Dave

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/4bXHMLuqsJ8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Console color in 3.0.1

[thinkwell]

Josh, thanks for that ticket link. I've signed up as a watcher.

Jeff, I've added the puppet27_console code to a client machine, then added 
the lines below to its puppet.conf, but no luck. Coloring remains the 3.0 
version. Is that possible? Or did I do something wrong?

[main]
logdest = telly_prototype_console


On Wednesday, October 31, 2012 1:55:19 PM UTC-4, Jeff McCune wrote:
>
> On Wed, Oct 31, 2012 at 10:37 AM, thinkwell 
> 
> > wrote:
>
>> A trivial post, perhaps, but I liked the console coloring of 2.7 much 
>> better than 3.0. Is there a way to get the 2.7 coloring back or to 
>> customize the console color scheme?
>>
>
> It's possible, but not exactly easy.  For a time, the new format was only 
> available using the log destination "telly_prototype_console" with 
> something like this in puppet.conf:
>
> [main]
> logdest = telly_prototype_console
>
> However, in commit 537343d we replaced the default destination named 
> "console" with the telly console.  Unfortunately, we didn't leave the old 
> destination in place as an option, but I'm not sure if we could have.
>
> If this really bothers you, you might be able to create a new destination 
> using:
>
> Puppet::Util::Log.newdesttype :puppet27_console do
>  ...
> end
>
>  You can see the Puppet 2.7.19 console formatter here:
>
> https://github.com/puppetlabs/puppet/blob/2.7.19/lib/puppet/util/log/destinations.rb#L88-104
>
> -Jeff
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/pDFpaqB_IYsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Console color in 3.0.1

[thinkwell]

Josh, thanks for that ticket link. I've signed up as a watcher.

Jeff, I've added the puppet27_console code to a client machine, then added 
the lines below to its puppet.conf, but no luck. Coloring remains the 3.0 
version. Is that possible? Or did I do something wrong?

[main]
logdest = puppet27_console


On Wednesday, October 31, 2012 1:55:19 PM UTC-4, Jeff McCune wrote:
>
> On Wed, Oct 31, 2012 at 10:37 AM, thinkwell 
> 
> > wrote:
>
>> A trivial post, perhaps, but I liked the console coloring of 2.7 much 
>> better than 3.0. Is there a way to get the 2.7 coloring back or to 
>> customize the console color scheme?
>>
>
> It's possible, but not exactly easy.  For a time, the new format was only 
> available using the log destination "telly_prototype_console" with 
> something like this in puppet.conf:
>
> [main]
> logdest = telly_prototype_console
>
> However, in commit 537343d we replaced the default destination named 
> "console" with the telly console.  Unfortunately, we didn't leave the old 
> destination in place as an option, but I'm not sure if we could have.
>
> If this really bothers you, you might be able to create a new destination 
> using:
>
> Puppet::Util::Log.newdesttype :puppet27_console do
>  ...
> end
>
>  You can see the Puppet 2.7.19 console formatter here:
>
> https://github.com/puppetlabs/puppet/blob/2.7.19/lib/puppet/util/log/destinations.rb#L88-104
>
> -Jeff
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/kMbNEefYMEEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Console color in 3.0.1

[thinkwell]

I'm not a ruby programmer and the puppet internals will remain a wilderness 
to me for the near future. So I'll have to content myself with watching the 
ticket and waiting for the final solution. Thanks alot for your ideas, 
though.

On Wednesday, October 31, 2012 7:45:54 PM UTC-4, Jeff McCune wrote:
>
> On Wed, Oct 31, 2012 at 12:24 PM, thinkwell 
> 
> > wrote:
>
>> Josh, thanks for that ticket link. I've signed up as a watcher.
>>
>> Jeff, I've added the puppet27_console code to a client machine, then 
>> added the lines below to its puppet.conf, but no luck. Coloring remains the 
>> 3.0 version. Is that possible? Or did I do something wrong?
>>
>
> I'm not sure this will work even if you did everything perfectly, so I 
> think this way lies madness.  Unless you're up for the challenging of 
> hacking at the internals of Puppet, I think this is a bad road to go down.
>
> If you'd like to keep trying though, please post the changes you made as a 
> patch or into a topic branch on Github and we can continue the discussion 
> on the puppet-dev mailing list or irc channel.
>
> -Jeff
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/nN1oQ-VlO7oJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Geppetto Project doesn't show folder structure

[thinkwell]

I'm feeling a bit besieged right now. I'm starting an extended project and 
I wanted to work in Kate. Kate's syntax highlighting is broken, so I check 
for an xml file and found one from reductive labs that gives a lovely 
404.

I'm no Eclipse guru, but I decided to give geppetto a try so I downloaded 
and ran it. Clicked File > New > Project > Puppet Module Project.

Then I went to my server and copied the beginnings of my project to my 
desktop and here geppetto nicely created a Puppet Module directory 
structure for me. And then in its infinite wisdom, elected not to show it 
in the Project Explorer. 

Pardon my snarkiness. I'd just like to start this project with beautiful 
syntax highlighting and ease of navigation. Kate has one but not the other. 
Apparently geppetto has the other but not the one.

How can I get the Project Explorer to Explore? 

TIA,

Dave

P.S. Does one have to be an Eclipse guru to use geppetto?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.


<>

[Puppet Users] Re: Geppetto Project doesn't show folder structure

[thinkwell]

Ok, the joke's on me. Select the project, right click and Refresh.

I said I was feeling besieged...  :-|

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Could not request certificate: Retrieved certificate does not match private key; please remove certificate from server and regenerate it with the current key

[thinkwell]

Sorry to resurrect an old thread, but this one did it for me. I always 
cleaned the master and deleted the /var/lib/puppet/ssl directory on the 
client when I had cert errors but that was not doing the trick. Came across 
this thread and blew away the /var/lib/puppet/ directory instead and VOILA!


On Wednesday, May 29, 2013 3:51:29 PM UTC-4, Jeff Silverman wrote:
>
> I see my mistake.  On the client, I should have deleted /var/lib/puppet/ 
> instead of /var/lib/puppet/ssl.  Deleting  /var/lib/puppet/ cleared the 
> issue.  
>
>
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] initdb error with puppet-postgresql module

[thinkwell]

Hello everyone,

I'm trying out the puppet-postgresql module (v. 3.3.3) on Rhel 5 & 6 
machines, installing Postgresql 9.3. When installing manually from the 
repos, everything works as expected:

1. yum -y install postgresql93-server
2. service postgresql-9.3 initdb
3. service postgresql-9.3 start

However, when installing from puppet-postgresql, 
/var/lib/pgsql/9.3/data/pg_log/ gets created prematurely, so the puppet run 
fails with output like so:

Error: Could not start Service[postgresqld]: Execution of 
'/etc/init.d/postgresql-9.3 start' returned 1: 
Error: /Service[postgresqld]/ensure: change from stopped to running failed: 
Could not start Service[postgresqld]: Execution of 
'/etc/init.d/postgresql-9.3 start' returned 1: 
Notice: 
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate
 
postgres connection for /postgres]: Dependency Service[postgresqld] has 
failures: true
Warning: 
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate
 
postgres connection for /postgres]: Skipping because of failed dependencies
Notice: 
/Stage[main]/Postgresql::Server::Service/Anchor[postgresql::server::service::end]:
 
Dependency Service[postgresqld] has failures: true

Manually running initdb gives this output:

[root@system ~]# /etc/init.d/postgresql-9.3 initdb
Initializing database: mkdir: cannot create directory 
`/var/lib/pgsql/9.3/data/pg_log': File exists


The only way around the problem is to manually delete the file and manually 
run initdb. After that, puppet runs succeed.
1. rm -rf /var/lib/pgsql/9.3/data/pg_log
2. service postgresql-9.3 start


If you just delete the file and re-run puppet, the pg_log director is again 
created prematurely.


Any help to fix this problem?

TIA,

thinkwell

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/dfd1bb55-c9ae-4e11-9733-d17ca3e75533%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: initdb error with puppet-postgresql module

[thinkwell]

Well, I found the problem. The initdb command was failing with this error:

runuser: cannot set groups: Operation not permitted

So, the folder was created but not the default database. When I commented 
out user & group, the command worked on both Rhel 5 & 6. Is this a bug?

  exec { 'postgresql_initdb':
command   => $initdb_command,
creates   => "${datadir}/PG_VERSION",
#user  => $user,
#group => $group,
logoutput => true,
#logoutput => on_failure,
require   => File[$datadir],
  }


Hope it helps someone else. 





On Monday, June 16, 2014 7:16:51 PM UTC-4, thinkwell wrote:
>
> Hello everyone,
>
> I'm trying out the puppet-postgresql module (v. 3.3.3) on Rhel 5 & 6 
> machines, installing Postgresql 9.3. When installing manually from the 
> repos, everything works as expected:
>
> 1. yum -y install postgresql93-server
> 2. service postgresql-9.3 initdb
> 3. service postgresql-9.3 start
>
> However, when installing from puppet-postgresql, 
> /var/lib/pgsql/9.3/data/pg_log/ gets created prematurely, so the puppet run 
> fails with output like so:
>
> Error: Could not start Service[postgresqld]: Execution of 
> '/etc/init.d/postgresql-9.3 start' returned 1: 
> Error: /Service[postgresqld]/ensure: change from stopped to running 
> failed: Could not start Service[postgresqld]: Execution of 
> '/etc/init.d/postgresql-9.3 start' returned 1: 
> Notice: 
> /Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate
>  
> postgres connection for /postgres]: Dependency Service[postgresqld] has 
> failures: true
> Warning: 
> /Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate
>  
> postgres connection for /postgres]: Skipping because of failed dependencies
> Notice: 
> /Stage[main]/Postgresql::Server::Service/Anchor[postgresql::server::service::end]:
>  
> Dependency Service[postgresqld] has failures: true
>
> Manually running initdb gives this output:
>
> [root@system ~]# /etc/init.d/postgresql-9.3 initdb
> Initializing database: mkdir: cannot create directory 
> `/var/lib/pgsql/9.3/data/pg_log': File exists
>
>
> The only way around the problem is to manually delete the file and 
> manually run initdb. After that, puppet runs succeed.
> 1. rm -rf /var/lib/pgsql/9.3/data/pg_log
> 2. service postgresql-9.3 start
>
>
> If you just delete the file and re-run puppet, the pg_log director is 
> again created prematurely.
>
>
> Any help to fix this problem?
>
> TIA,
>
> thinkwell
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d5c3eeef-2307-46e2-93c5-193415a954c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.