> Thanks for your help. Unfortunately, I can't tell you much about the
> setup. I've only ever done this with passenger as well, and the person
> who did set it up has
> left the company.
I'm not really sure if you should raise a new ticket on this one - or
add an addendum to this:
http://project
On Tue, Sep 13, 2011 at 5:16 PM, Douglas Garstang
wrote:
>
> I wonder if the performance of the puppet master in 2.7.3 has
> increased to the point where passenger/mongrel aren't really required
> anymore? I'm running puppet in standalone debug right now, and forced
> 40 or so clients to reconnect
On Tue, Sep 13, 2011 at 5:12 PM, Ken Barber wrote:
>> I think this may be totally related. We're using mongrel... AND,
>> running the puppet master in standalone mode as you suggested yields
>> this now on the client:
>>
>> Sep 13 16:49:06 hproxy11 puppet-agent[27311]:
>> (/Stage[main]/Puppet::Set
> I think this may be totally related. We're using mongrel... AND,
> running the puppet master in standalone mode as you suggested yields
> this now on the client:
>
> Sep 13 16:49:06 hproxy11 puppet-agent[27311]:
> (/Stage[main]/Puppet::Setup/Notify[xxx = 2.7.3 ...]/message) defined
> 'message' as
On Tue, Sep 13, 2011 at 4:43 PM, Ken Barber wrote:
> How are you running your puppet master?
>
> Can you try it with just:
>
> puppet master --debug --no-daemonize
>
> Just there was a thread I recall about Mongrel - it may not be related:
>
> http://groups.google.com/group/puppet-users/browse_thr
How are you running your puppet master?
Can you try it with just:
puppet master --debug --no-daemonize
Just there was a thread I recall about Mongrel - it may not be related:
http://groups.google.com/group/puppet-users/browse_thread/thread/3f4072d375851ee7
It would be nice to see a packet capt
On Tue, Sep 13, 2011 at 4:27 PM, Ken Barber wrote:
> You could always do one of your crazy greps :-).
:(
>
> Out of curiosity - what do your /var/lib/puppet/yaml/facts/*.yaml
> files show you on your server?
clientversion: &id001 0.25.5
:(
Doug
--
You received this message because you are s
You could always do one of your crazy greps :-).
Out of curiosity - what do your /var/lib/puppet/yaml/facts/*.yaml
files show you on your server?
ken.
On Wed, Sep 14, 2011 at 12:16 AM, Douglas Garstang
wrote:
> On Tue, Sep 13, 2011 at 4:01 PM, Douglas Garstang
> wrote:
>> On Tue, Sep 13, 2011
On Tue, Sep 13, 2011 at 4:01 PM, Douglas Garstang
wrote:
> On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang
> wrote:
>> On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber wrote:
>>> Hmm ... well can you try using ${::puppetversion} ...?
>>
>> Adding this:
>>
>> notify{"xxx = ${::puppetversion} ...":}
On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang
wrote:
> On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber wrote:
>> Hmm ... well can you try using ${::puppetversion} ...?
>
> Adding this:
>
> notify{"xxx = ${::puppetversion} ...":}
>
> to the manifest gives this on the server:
>
> Sep 13 15:14:43 sv
On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber wrote:
> Hmm ... well can you try using ${::puppetversion} ...?
Adding this:
notify{"xxx = ${::puppetversion} ...":}
to the manifest gives this on the server:
Sep 13 15:14:43 sv2admin1 puppet-master[22452]:
(//hproxy11.h.foo.com//Stage[main]/Puppet::
Hmm ... well can you try using ${::puppetversion} ...?
Also - I notice you are using an ENC ... can you disable that and just
use node entries? Yet another place where we might be getting vars we
don't expect. In fact - setup a site.pp that is really blank - and
only contains that notify statement
On Tue, Sep 13, 2011 at 12:46 PM, Ken Barber wrote:
> The reason why I say this - is because I can replicate this problem myself
> with:
>
> node default {
> $puppetversion = "0.25.5"
> notice($puppetversion)
> }
>
> In fact its the only way I can think of to replicate the issue -
> besides all
Even using:
notify{"${::puppetversion} on ${::fqdn}":}
Instead would be of interest ...
ken.
On Tue, Sep 13, 2011 at 8:46 PM, Ken Barber wrote:
> The reason why I say this - is because I can replicate this problem myself
> with:
>
> node default {
> $puppetversion = "0.25.5"
> notice($puppe
The reason why I say this - is because I can replicate this problem myself with:
node default {
$puppetversion = "0.25.5"
notice($puppetversion)
}
In fact its the only way I can think of to replicate the issue -
besides all the other ways we have already ruled out. *shrug*.
ken.
On Tue, Sep
On Sep 13, 2011, at 12:28 PM, Douglas Garstang wrote:
> On Tue, Sep 13, 2011 at 12:25 PM, Craig White wrote:
>>
>> I'm thinking that he has puppet 0.25.5 gem installed and all of the rpm -e /
>> yum remove isn't going to solve that.
>>
>> try 'gem list --local'
>
> Craig, I posted this yeste
So that is the only case where you are using the variable throughout
your entire code? I mean - ALL your code ... not just the one line you
are printing to the screen ...
ken.
On Tue, Sep 13, 2011 at 8:30 PM, Douglas Garstang
wrote:
> On Tue, Sep 13, 2011 at 11:01 AM, Ken Barber wrote:
>> Yeah
On Tue, Sep 13, 2011 at 11:01 AM, Ken Barber wrote:
> Yeah this doesn't seem to be old versions of Puppet.
>
> So from my other email ... can you show us the code where you are
> doing your comparison for $puppetversion? I have a feeling I might
> know what it is ... although I'm probably wrong ..
On Tue, Sep 13, 2011 at 12:25 PM, Craig White wrote:
>
> On Sep 13, 2011, at 10:48 AM, Douglas Garstang wrote:
>
>> On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar wrote:
>>>
>>>
>>> - Original Message -
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum
wrote:
> Err, what is that 0
On Sep 13, 2011, at 10:48 AM, Douglas Garstang wrote:
> On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar wrote:
>>
>>
>> - Original Message -
>>> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum
>>> wrote:
Err, what is that 0.25-5 doc folder and what RPM owns it?
rpm -qf /usr/
If that were true the job of QA would be much easier
On Sep 13, 2011 10:48 AM, "Douglas Garstang"
wrote:
> On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar wrote:
>>
>>
>> - Original Message -
>>> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum
>>> wrote:
>>> > Err, what is that 0.25-5 doc fol
Yeah this doesn't seem to be old versions of Puppet.
So from my other email ... can you show us the code where you are
doing your comparison for $puppetversion? I have a feeling I might
know what it is ... although I'm probably wrong ...
In fact - grep for 'puppetversion' in all of your puppet co
On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar wrote:
>
>
> - Original Message -
>> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum
>> wrote:
>> > Err, what is that 0.25-5 doc folder and what RPM owns it?
>> >
>> > rpm -qf /usr/share/doc/puppet-0.25.5
>> >
>> > If nothing owns it, you've prett
- Original Message -
> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum
> wrote:
> > Err, what is that 0.25-5 doc folder and what RPM owns it?
> >
> > rpm -qf /usr/share/doc/puppet-0.25.5
> >
> > If nothing owns it, you've pretty much proved your system has old
> > Puppet artefacts lying arou
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum wrote:
> Err, what is that 0.25-5 doc folder and what RPM owns it?
>
> rpm -qf /usr/share/doc/puppet-0.25.5
>
> If nothing owns it, you've pretty much proved your system has old
> Puppet artefacts lying around. Personally I wouldn't trust any of the
> co
25 matches
Mail list logo
