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
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
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 verif
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.
> >
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 clien
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 t
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:
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 prob
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
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,
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
--~--~-~--~~-
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 gr
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
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 forPassenger
* 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:
> >>> [..]
> >>>
> 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 <
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". A
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
> 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 h
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
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
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 peop
22 matches
Mail list logo
