[Puppet Users] Re: Issues with clients connecting
On Jun 25, 10:54 am, Curt Micol wrote: > I am working on moving to a new puppetmaster. Along with this move I > am updating to Puppet 0.24.8. > > As it stands, my test client can't connect: > notice: Starting Puppet client version 0.24.8 > debug: Loaded state in 0.00 seconds > debug: Retrieved facts in 1.12 seconds > debug: Retrieving catalog > debug: Calling puppetmaster.getconfig > err: Could not retrieve catalog: Could not find node > 'vz200b.liquidweb.com'; cannot compile It says it can't compile the catalog - this is _not_ a connection problem. Can you test without external nodes first? Christian --~--~-~--~~~---~--~~ 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: Performance of Passenger vs. Mongrel
On Jun 26, 3:05 pm, Mark Plaksin wrote: > Scott Smith writes: > > Mark Plaksin wrote: > > Are you running the same # of mongrels as Passenger workers? > > Sort of :) We run 12 masters in mongrel. Passenger doesn't seem have a > "run at least this many puppetmasters" setting. We set the max to 12 to > match mongrel but we never saw more than 6 masters running. We bumped > max to 24 late yesterday and I now see 11 masters running. We'll see > how it performs during today's big schedule run. If you only feed it high traffic once a day or so, you might want to set PassengerPoolIdleTime much larger, say 172800. You probably would only see an effect on the next day, though. Christian --~--~-~--~~~---~--~~ 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: Performance of Passenger vs. Mongrel
On Jun 26, 9:56 pm, Mark Plaksin wrote: > Scott Smith writes: > > Mark Plaksin wrote: > > >> Load average is peaking around 10. That's not so good compared to > >> running under mongrel where the load peaked at less than 5 (both with > >> 0.25b1 and 0.25b2). > > > Were the puppetmasters verifiably slower? If so, how did you measure it? > > I didn't measure but load average has been a good indicator for us. Oh, > and our stats system has stats based on Puppet reports. The "how long > did the file part of all manifests on all machines take to run" graph > says that our file server is slower with Passenger than it is with > Mongrel. The difference is about a factor of 2--just like the > difference in the peak load averages. What worries me is, that you are saying it takes twice as long and your load is twice as high. So you're actually seeing a 4-time worse performance, which is /very/ bad. Which processes do you see running? puppetmasterds and Apaches or only one kind of them? How long does file serving take for you? Are there very large files? If so, you might want to test with PassengerUseGlobalQueue on. Which versions are your clients? 0.25beta too? Christian --~--~-~--~~~---~--~~ 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: Performance of Passenger vs. Mongrel
On Jun 26, 11:19 pm, Scott Smith wrote: > Christian Hofstaedtler wrote: > > > What worries me is, that you are saying it takes twice as long and > > your load is twice as high. So you're actually seeing a 4-time worse > > performance, which is /very/ bad. > > Which processes do you see running? puppetmasterds and Apaches or only > > one kind of them? > > Even then, I don't think a load average of 10 on his system is something > to worry about. A load average of 5 on his 8 core system simply means > that he is not CPU bound. The CPU(s) are underutilized. Even at 10 I > would wager that he still is not. It's still a lot of worry if it's 4-times worse. It will mean less clients per server when scaling up. It'd be interesting to compare this setup with 0.24.8, as the passenger-related integration code got completely rewritten for 0.25. Christian --~--~-~--~~~---~--~~ 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: node cache and Passenger
On Jun 25, 7:11 pm, Rob McBroom wrote: > I've started using Passenger and it seems to be working just fine, but > I see this in the logs on the puppetmaster for what looks like every > run on every node. > > Jun 25 13:02:53 puppet puppetmasterd[7825]: Expiring the node > cache of client.foo.com > Jun 25 13:02:53 puppet puppetmasterd[7825]: Not using expired > node for client.foo.com from cache; expired at Thu Jun 25 13:01:53 > -0400 2009 > Jun 25 13:02:53 puppet puppetmasterd[7825]: Caching node for > client.foo.com > > Any ideas? Thanks. I have no idea what this even means and why you would be seeing this only with Passenger. Christian --~--~-~--~~~---~--~~ 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: puppet logging with passenger
On Aug 8, 6:14 am, Ohad Levy wrote:
> I've tried to change logging to warn, it ended up breaking the puppetmaster
> not being able to sign new certificates.
IIRC, you can do something like this for 0.24.8:
Puppet::Util::Log.newdestination("/path/to/log")
Maybe look at Puppet::Util::Log for the details.
Christian
--~--~-~--~~~---~--~~
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: Virtual recipe signals hardware nodes as 'openvz'
On Sep 8, 12:34 pm, Julien Cornuwel wrote: > Not sure this is the right place to report this. > On an OpenVZ HardwareNode, the 'virtual' parameter given by facter > says 'openvz'. > This is because the /proc/user_beancounters file also exists on the > hardware node. This has been fixed already: http://projects.reductivelabs.com/projects/facter/repository/revisions/6393e82e86def14891b204803aba156059736749 Facter 1.5.6 correctly reports "openvzhn" for Hardware Nodes (and "openvzve" for containers). > This has some bad side-effects as a hardware node should, for example, > have a NTP configuration, where a container should not. True. Christian --~--~-~--~~~---~--~~ 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: Puppet 0.25 migration
AFAIK this is the result of a known bug in Passenger 2.2.3 and newer. ext/rack/README states: > *** Important note about Passenger versions: >2.2.2 is known to work. >2.2.3-2.2.4 are known to *NOT* work. >2.2.5 (when it is released) is expected to work properly again. You should probably downgrade to 2.2.2, and if that works you might try upgrading to 2.2.5 and see if that works. If it does (or not), please report back :) Christian --~--~-~--~~~---~--~~ 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: Puppet 0.25 migration
On Sep 9, 8:30 pm, jrojas wrote: > I am seeing this problem as well. > Reverting from 2.2.5 to 2.2.2 did not help. I've now done some tests with 2.2.5 and did not find any obvious problems - so, if you are seeing a problem with 2.2.5, please try to reproduce it with webrick. If it persists, it's not a Passenger related bug. In any case please file bugs, but see #2516, #2517 and #2620 first. Thanks, Christian --~--~-~--~~~---~--~~ 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: Puppet 0.25 migration
On Sep 12, 11:51 pm, Christian Hofstaedtler wrote: > On Sep 9, 8:30 pm, jrojas wrote: > > > I am seeing this problem as well. > > Reverting from 2.2.5 to 2.2.2 did not help. > > I've now done some tests with 2.2.5 and did not find any obvious > problems - so, if you are seeing a problem with 2.2.5, please try to > reproduce it with webrick. If it persists, it's not a Passenger > related bug. In any case please file bugs, but see #2516, #2517 and > #2620 first. Those bug numbers were wrong. Please check those: "Bug #2617: Problem with certs upgrading puppetmaster to 0.25.0" "Bug #2619: Fresh 0.25.0 client cannot 'authenticate' to 0.25.0 puppetmaster." "Bug #2620: Regex problem in puppetmaster auth.conf" > > Thanks, > Christian --~--~-~--~~~---~--~~ 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: authentication issue with passenger
Also: please check that you have the required settings in the masters puppet.conf as mentioned in http://github.com/reductivelabs/puppet/blob/master/ext/rack/README If it still doesn't work, please post a full log from master + server for a single client run. Christian --~--~-~--~~~---~--~~ 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: authentication issue with passenger
What does the client in question say when this happen? Does this happen all the time? Did you try with no auth.conf? Christian --~--~-~--~~~---~--~~ 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: Passenger versions with Puppet 0.25.1 puppetmasterd
On Nov 6, 11:32 pm, Nigel Kersten wrote: > [..] > I'm in the middle of testing 2.2.5 now, and hit this problem. > > http://groups.google.com/group/phusion-passenger/browse_thread/thread... > > Once that fix was applied, 0.24.8 and 0.25.1 clients are working > happily for me with an install of the current git 0.25.x branch. So, you're saying, 2.2.5 works fine with current 0.25.x git, with a passenger fix applied but not my puppet patch? If so, then this "passenger is not working" problem puzzles me completely. Could qualify for a heisenbug. May I ask what versions of Ruby and Apache you're using? Thanks, Christian --~--~-~--~~~---~--~~ 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: Serious issue with 0.25.1, at wits end
On Nov 6, 9:36 pm, Paul Lathrop wrote: > On Thu, Nov 5, 2009 at 2:30 AM, Christian Hofstaedtler wrote: > > I've now been able to reproduce this withPassenger2.2.5 and > > current Puppet HEAD. The surprising solution is to remove the work > > around code forPassenger2.2.4, which falls back to using ENV for > > stuff which ain't in request.env. > > > I've posted a patch to puppet-dev [1] which actually does this. > > If you could test it, it'd be great. > > Tested and confirmed, this works great. Thanks, Christian! Thanks for testing this. Christian --~--~-~--~~~---~--~~ 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: Passenger versions with Puppet 0.25.1 puppetmasterd
* Nigel Kersten [091109 22:22]: > > On Sat, Nov 7, 2009 at 8:12 AM, Nigel Kersten wrote: > > On Sat, Nov 7, 2009 at 3:14 AM, Christian Hofstaedtler > > wrote: > >> > >> On Nov 6, 11:32 pm, Nigel Kersten wrote: > >>> [..] > >>> I'm in the middle of testing 2.2.5 now, and hit this problem. > >>> > >>> http://groups.google.com/group/phusion-passenger/browse_thread/thread... > >>> > >>> Once that fix was applied, 0.24.8 and 0.25.1 clients are working > >>> happily for me with an install of the current git 0.25.x branch. > >> > >> So, you're saying, 2.2.5 works fine with current 0.25.x git, with a > >> passenger fix applied but not my puppet patch? > > > > Yes. > > > >> > >> If so, then this "passenger is not working" problem puzzles me > >> completely. Could qualify for a heisenbug. > > I just realized I have this in place... > > ssl_client_header=HTTP_X_SSL_SUBJECT > > could that possibly be changing behavior? > > I also have separate virtual hosts for CA and non-CA servers on > different ports. I haven't fully tested running a 0.25.1 CA under the > above configuration. It's interesting that it even works. It's supposed to only work with ssl_client_header = SSL_CLIENT_S_DN. Having this configured /wrong/ would lead to clients not getting authorized at all; if your clients work, then it can't be actually "wrong". Are you using an SSL proxy or something else which might change SSL behaviour? Thanks, Christian -- christian hofstaedtler --~--~-~--~~~---~--~~ 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: passenger not accepting alternate config file
> config.ru:
> $:.unshift('/apps/puppet/puppet/lib')
> $:.unshift('/apps/puppet/facter/lib')
> $0 = "puppetmasterd"
> require 'puppet'
> ARGV << "--debug"
> ARGV << "--verbose"
> ARGV << "--rack"
> ARGV << "--config /tmp/puppetmasterd.genconfig"
Did you try with this? ->
ARGV << "--config"
ARGS << "/tmp/puppetmasterd.genconfig"
Christian
--
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
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=.
[Puppet Users] Re: properly removing dead hosts.
On Nov 21, 2:43 pm, Udo Waechter
wrote:
> Hello all.
>
> I know there were many discussions about how to remove hosts from puppet. I
> know the script that removes all entries from the database.
>
> What I am looking for is a solution that sets all exported resources to
> "ensure => absent". Assumed that they have a "ansure" parameter.
>
[...]
>
> And the last question:
> How do you all handle the case when hosts die. Do you simply remove all
> storedconfigs and do not care about exported resources that might have been
> imported by other hosts (ssh-keys, mounts, nagios-checks, ...)? Or do you go
> to all those hosts and remove the resources by hand?
We have these stanzas in the manifest for the nagios server:
48 resources { "nagios_service":
49 purge => true
50 }
51 resources { "nagios_host":
52 purge => true
53 }
54 resources { "nagios_hostgroup":
55 purge => true
56 }
For other resources we're using similar stanzas, and for file-snippet
exported resources we just automatically purge the containing
directory.
This combined with cleaning the host from the storedconfigs DB gets
rid of all the traces left.
Christian
--
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
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=.
[Puppet Users] Re: authentication issue with passenger (resolved)
You know, this usually means that you don't have these settings in
your puppet.conf, as doc'ed:
Required puppet.conf settings:
[puppetmasterd]
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
-ch
On Jan 8, 7:30 pm, jb wrote:
> Thank you Silviu - I just went through a 0.25.2 installation using
> passenger 2.2.8 just yesterday and had the same issues which started
> this thread:
>
> puppetmasterd[29797]: Puppet Server (Rack): Internal Server Error:
> Unhandled Exception: "Host app3.chassis1 10.x.x.x) not authorized to
> call fileserver.list"
> puppetmasterd[29797]: Denying unauthenticated client app3.chassis1
> (10.x.x.x) access to fileserver.list
>
> Your suggestions commends below fixed the issue..
>
> On Dec 17 2009, 8:37 am, Silviu Paragina wrote:
>
>
>
> > What's your apache vhost config? Passenger 2.2.2 with 0.25.1 didn't work
> > for me with the config from the example in 0.25.1 tree
> > I think there is an error in the 0.25.1 example one.
>
> > I had to add:
> > 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
>
> > Silviu
>
> > On 17.12.2009 15:22, lluis wrote:
--
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
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Fwd: Re: [Puppet Users] Re: authentication issue with passenger (resolved)]
> From: Silviu Paragina > Subject: Re: [Puppet Users] Re: authentication issue with passenger (resolved) > Date: Sat, 09 Jan 2010 15:30:39 +0200 > To: puppet-users@googlegroups.com > > Christian Hofstaedtler wrote: >> You know, this usually means that you don't have these settings in >> your puppet.conf, as doc'ed: >> >> Required puppet.conf settings: >> [puppetmasterd] >> ssl_client_header = SSL_CLIENT_S_DN >> ssl_client_verify_header = SSL_CLIENT_VERIFY >> >> -ch >> >> > Noted. > Does this work with both passenger 2.2.2, 2.2.5 and above? Yes. -ch -- christian hofstaedtler -- 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 puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: problem with my filebucket and passenger
I've just checked on my installation, and filebucket seems to work
fine (under passenger).
For testing, I put these into the manifest:
filebucket { main: server => $servername }
File { backup => main }
And these into namespaceauth.conf on the puppetmaster:
[puppetbucket]
allow *.domain.com
On Dec 29, 9:43 pm, "Jeff Frost" wrote:
> I'm getting the following error from puppetd whenever it tries to backup a
> file to the filebucket on the server.
>
> err:
> //Node[devdata]/dataserver/data_packages/apacheconf/File[/etc/apache2/modules.d/00_mpm.conf]/source:
> change from {md5}0ffbbd3efd8934e7d9113cc13a375326 to
> puppet:///files/data/etc/apache2/modules.d/00_mpm.conf failed: Could not
> connect to puppet on port 8140
Is your puppetmaster really called "puppet"? Can you connect (for
example by using telnet) from the client to "puppet" on port 8140?
Christian
--~--~-~--~~~---~--~~
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] puppet 0.24.4 & missing compiles
Hello, I've got a Puppet installation on 0.24.4 and see missing catalog compiles for some clients. Most other puppet clients compile fine and work fine. The logs give me this: while working fine: (on the master:) Jan 19 05:09:29 puppetmasterd[30489]: Caching node lb01.int.inqnet.at Jan 19 05:09:36 puppetmasterd[30489]: Stored catalog for lb01.int.inqnet.at in 5.48 seconds Jan 19 05:09:36 puppetmasterd[30489]: Compiled configuration for lb01.int.inqnet.at in 6.21 seconds Jan 19 05:09:46 puppetmasterd[20070]: Processing reports store, log, tagmail for lb01.int.inqnet.at (on the client:) Jan 19 05:09:39 puppetd[28508]: Starting catalog run Jan 19 05:09:46 puppetd[28508]: Finished catalog run in 7.34 seconds missing the compile: (on the master:) Jan 19 06:10:11 puppetmasterd[24308]: Processing reports store, log, tagmail for lb01.int.inqnet.at (on the client:) Jan 19 06:10:03 puppetd[28508]: Starting catalog run Jan 19 06:10:11 puppetd[28508]: Finished catalog run in 8.21 seconds Except the obviously "missing" lines from the puppetmaster log, I did not find anything interesting. Is this a known problem? Christian -- Christian Hofstädtler InQnet GmbH, Vienna, Austria --~--~-~--~~~---~--~~ 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: Props to the Passenger instructions.
On Mar 26, 3:09 am, Nigel Kersten wrote: > So I just got around to trying outPassengertoday, and I have to say, > this is a really really simple setup. > > The instructions are great, and everything just worked seamlessly out > of the box once I fulfilled the dependencies. Good to know that people are actually using this. On Mar 26, 3:36 am, Jason Rojas wrote: > Did you have any issues where you had to add *s to namespace.conf > like I did? > > [puppetreports.report] > allow * > > [puppetbucket] > allow * > > [...] I've not seen any issues regarding namespaceauth, but I'm unsure if I ever tested without a properly configured namespaceauth.conf. If you can reproduce this, maybe file a ticket and assign it to me. Chris --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
