Thanks James,
I installed the patch and got the proper error message err: Could not
retrieve catalog from remote server: hostname was not match with the
server certificate. I'm using ruby 1.8.7.
It's still weird however that it complains about the hostname as it
was working before. Nevertheless,
I'm getting this frustrating error message and can't figure out why.
Puppet claims I'm missing a template file:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not find template 'nagios/nrpe.cfg/MASTER.erb' at /usr/
local/etc/puppet/modules/nrpe/manifests/init.pp:22
On Tue, Jun 8, 2010 at 8:31 PM, donavan dona...@desinc.net wrote:
On Jun 8, 2:39 am, Héctor Rivas key...@gmail.com wrote:
Is there anybody working extending puppet for AIX?
How is the best way to share our improvements and colaborate?
I believe Andrew Forgue did a lot (all?) of the
Robert robertsch...@gmail.com writes:
On May 6, 9:56 am, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
I suspect we will turn 'node default' into 'class default', then include
that rather than inheriting that, since that does fix the scope issue.
On 9 June 2010 06:09, Jason Koppe jason.robert.ko...@gmail.com wrote:
On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh
joseph.e.mcdon...@gmail.com wrote:
Daniel Kerwin wrote:
Hi list,
i just enabled storeconfigs and cannot use puppetrun on more than 5
hosts. When i try 6+ i get the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mi den 9. Jun 2010 um 3:35 schrieb Joe McDonagh:
But that is exact the point. If I collect the information with
ssh-keyscan there is a little change that the key is wrong and not the
one of the machine. Puppet give a nice way to
Nevermind, I found out that I had accidentially overwritten the
puppet.conf...
Luckily I had a backup and everything is up and running again :)
On 9 Jun, 09:32, kit efossv...@gmail.com wrote:
I'm getting this frustrating error message and can't figure out why.
Puppet claims I'm missing a
Love the speed increase. A couple of initial thoughts, I should probably
raise tickets:
1 - Sort by name as default in Hosts section
2 - bring back the yaml link in the Hosts section for a host
Matt
On 7 June 2010 09:22, Ohad Levy ohadl...@gmail.com wrote:
I’m happy to announce a new version
On Tue, Jun 8, 2010 at 10:50 AM, Nigel Kersten nig...@google.com wrote:
We had a chat about this on the list relatively recently.
The server actually writes out the client fact data *before* the external
node provider gets invoked, so you can poke into the fact store on the
server,
FYI - Found that thread:
http://groups.google.com/group/puppet-users/browse_thread/thread/28c7b30874bb792c/dca3587668d50f9e?hl=enlnk=gstq=external+nodes#dca3587668d50f9e
Sorry that this was a rehashing of it - but I agree that this process should
be listed in the docs. I'll look into what needs
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/
Correction: I copied the foreman.rb to /usr/lib/ruby/site_ruby/1.8/
puppet/reports/foreman.rb from extras/puppet/foreman/files/foreman-
report.rb. The instructions called for the file to be copied to /usr/
lib/ruby/1.8/puppet/reports, but that's not the directory structure
that I have. I also
On RHEL, using the rpm packages for foreman and puppet, I had to copy /
usr/share/foreman/extras/puppet/foreman/files/foreman-report.rb to /
usr/lib/ruby/site_ruby/1.8/puppet/foreman.rb and everything works
swimmingly.
Also, uncomment #reports=log, foreman in puppetmasterd... it may still
work in
For what it is worth, to solve a similar problem with dashboard
(distributing puppet_dashboard.rb for reporting), I just stuck it in
modules/dashboard/lib/puppet_dashboard.rb with puppet.conf:
pluginsync=true. Then puppet distributes it automatically into a lib
directory and things work nice
Hi guys,
I'm trying to setup my first puppet installation and I'm running into problems.
I've got the puppetmaster running on a fresh install of Centos 5.4.
The puppet client is also on another Centos 5.4 server.
Once I've signed the client certificate on the puppetmaster, the
client seems to
On Jun 8, 3:57 pm, Rudy Gevaert rudy.geva...@gmail.com wrote:
Dear all,
I'm fairly new to puppet, so please excuse this newbie question.
I was wondering how I can override a certain variable in a module I
downloaded from the forge.
By example. I downloaded and installed the
Hi guys,
I'm trying to setup my first puppet installation and I'm running into
problems.
I've got the puppetmaster running on a fresh install of Centos 5.4.
The puppet client is also on another Centos 5.4 server.
Once I've signed the client certificate on the puppetmaster, the
client seems to
Sorry for the double post. Thought the first didnt send.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
I have about a dozen sites with puppet masters in each. They are
geographically located with some slow network links between them. The setup
I was evaluating is to have a centralized stored config server running mysql
with all of my remote masters sending their locations data back to the
central
Update - After the client tries to connect, I found this in the
puppetmaster WEBrick log:
[2010-06-09 17:52:10] DEBUG accept: 10.1.1.70:49980
[2010-06-09 17:52:10] ERROR OpenSSL::SSL::SSLError: sslv3 alert bad certificate
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:44:in
I evaluated this scenario a couple of years ago (before puppetq), and it was
never a feasible solution due to a. latency (e.g. everything is much
slower), b. if wan goes down, your master wont work.
One of the reasons that I've developed Foreman, is to overcome this problem,
the way I do it is:
-
I don't want to use sqllite... puppetqd doesn't leave me much of a choice
since it will default to it even if you tell it to use mysql as your
storedconfig DB since thats needed for the centraldb. Ultimately I think
puppetqd needs support for keeping a cached copy of various database flavors
Solved - God I had SELinux sometimes.
On Wed, Jun 9, 2010 at 4:57 PM, Matt Keating keats...@gmail.com wrote:
Update - After the client tries to connect, I found this in the
puppetmaster WEBrick log:
[2010-06-09 17:52:10] DEBUG accept: 10.1.1.70:49980
[2010-06-09 17:52:10] ERROR
0.25.5 changed the default vardir from /var/puppet to /var/lib/puppet
and it's caused the odd issue we have to fix in the Mac pkg
preflights.
After re-reading 'man hier' I'm tempted to change the default on OS X to:
/var/db/puppet
instead.
/var/ multi-purpose log, temporary,
My issue is basically, that I'm running foreman under passenger, and
this config seems to break reporting. Yesterday,I was using webbrick
and it was working fine, with the URL of foreman.rb pointing to
http://host:3000. Today with passenger, I'm trying to point it to
either http://host or
hi guys, I'm a newbie so please be gentle. ;)
I'm running puppet on gentoo with the modules from example42. They
seem to work well but I'm running into a problem with the way gentoo
does certain packages. Redhat and other distros seem to bundle the
mysql or openssh packages in mysql-client and
Hello Nigel,
/var/db/puppet sounds good for the default location..
a little background: We have a central services team, and many field
teams that directly support our customers.
We've been looking into separating the $vardir based on team (central or
field). We're still in the thinking
With reports=log,foreman you'll see them under /var/lib/puppet/reports
even if they aren't actually getting to foreman itself. Executability of
foreman.rb won't factor in this working or not.
The code in foreman.rb is probably connecting directly to foreman on
http://(local?)host:3000. You
What does your apache conf look like for foreman and the reports?
On Wed, Jun 9, 2010 at 9:09 AM, CraftyTech hmmed...@gmail.com wrote:
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 /
Queuing support from ActiveMQ doesn't even make a difference for me -- I
thought the purpose of adding the queuing support was to queue the data in
puppetqd's memory and let that flush out to the database when it could. I'm
still seeing this error from the puppetmaster (not puppetqd).
err: could
/etc/httpd/conf.d/foreman.conf:
VirtualHost *:443
ServerName hostnameXYZ
ServerAlias foreman
RailsAutoDetect On
DocumentRoot /var/www/html
RailsBaseURI /foreman
# Use puppet certificates for SSL
SSLEngine on
SSLCertificateFile /var/lib/puppet/ssl/certs/
/etc/httpd/conf.d/foreman.conf:
VirtualHost *:443
ServerName hostnameXYZ
ServerAlias foreman
RailsAutoDetect On
DocumentRoot /var/www/html
RailsBaseURI /foreman
# Use puppet certificates for SSL
SSLEngine on
SSLCertificateFile /var/lib/puppet/ssl/certs/
/etc/httpd/conf.d/foreman.conf:
VirtualHost *:443
ServerName hostnameXYZ
ServerAlias foreman
RailsAutoDetect On
DocumentRoot /var/www/html
RailsBaseURI /foreman
# Use puppet certificates for SSL
SSLEngine on
SSLCertificateFile /var/lib/puppet/ssl/certs/
hostnameXYZ.pem
Looks like my config, except I added the following to see my reports
Alias /report /var/lib/puppet/rrd/
Directory /var/lib/puppet/rrd/
PassengerEnabled off
Options Indexes
Order deny,allow
Allow from all
/Directory
On Wed, Jun 9, 2010 at 2:15 PM, CraftyTech
What happens if you have foreman listen say on port 3000 with
passenger and have ssl disabled?
On Jun 9, 3:29 pm, CraftyTech hmmed...@gmail.com wrote:
/etc/httpd/conf.d/foreman.conf:
VirtualHost *:443
ServerName hostnameXYZ
ServerAlias foreman
RailsAutoDetect On
DocumentRoot
Nigel,
We're trained to check /var/db for pkgdmg trigger files anyways - I've got
no problem with it. I'll need to make sure my external nodes script can
find the $vardir/yaml/facts store, but other than that I don't have a
problem with its change. I suspect many may not notice - at least
On Wed, Jun 9, 2010 at 6:15 PM, Gary Larizza ccsh...@gmail.com wrote:
Nigel,
We're trained to check /var/db for pkgdmg trigger files anyways - I've got
no problem with it. I'll need to make sure my external nodes script can
find the $vardir/yaml/facts store, but other than that I don't have a
On Wed, Jun 9, 2010 at 9:17 PM, Nigel Kersten nig...@google.com wrote:
On Wed, Jun 9, 2010 at 6:15 PM, Gary Larizza ccsh...@gmail.com wrote:
Nigel,
We're trained to check /var/db for pkgdmg trigger files anyways - I've
got
no problem with it. I'll need to make sure my external nodes
On Wed, Jun 9, 2010 at 6:22 PM, Gary Larizza ccsh...@gmail.com wrote:
On Wed, Jun 9, 2010 at 9:17 PM, Nigel Kersten nig...@google.com wrote:
On Wed, Jun 9, 2010 at 6:15 PM, Gary Larizza ccsh...@gmail.com wrote:
Nigel,
We're trained to check /var/db for pkgdmg trigger files anyways - I've
wiki is right, I forgot this: ssl_client_header = HTTP_X_SSL_SUBJECT
On 6月9日, 上午10时21分, Jomo zhan...@gmail.com wrote:
It works for me too, thank you.
It should be added to the wiki.
btw, my nginx is 0.8.29.
On 6月9日, 上午12时01分, Dan Carley dan.car...@gmail.com wrote:
On 8 June 2010 10:06,
Hi all
We've just finished enabling ticket creation and updates via email.
You can now send an email to tick...@puppetlabs.com to create a ticket.
You must have a Redmine account to do this and your From address must
match the address on your Redmine account. Any attachments added to
the
41 matches
Mail list logo
