Hi,
I have a few hundreds RHE4 running (not to mention a few hundreds of RHE3)
without having this issue.
any chance you are restarting your mongrels (e.g. because of memory leaks)?
at the same time?
do you see the request on the apache log correctly etc?
Cheers,
Ohad
On Thu, Dec 17, 2009 at 1:
Yeah, most of them are.
>>> On 17/12/2009 at 4:55 pm, Dan Bode wrote:
> Hi,
>
>>
>> debug: Format pson not supported for Puppet::FileServing::Metadata; has not
>> implemented method 'from_pson'
>> debug: Format s not supported for Puppet::FileServing::Metadata; has not
>> implemented method 'fro
Hi,
>
> debug: Format pson not supported for Puppet::FileServing::Metadata; has not
> implemented method 'from_pson'
> debug: Format s not supported for Puppet::FileServing::Metadata; has not
> implemented method 'from_s'
>
> Can you open a ticket for this?
>
> Is that most likely due to using an
In addition to my previous email the output following may be helpful.
debug: Format pson not supported for Puppet::FileServing::Metadata; has not
implemented method 'from_pson'
debug: Format s not supported for Puppet::FileServing::Metadata; has not
implemented method 'from_s'
Is that most lik
Hi Dan,
> How often are the clients checking in with the server?
They check in every half hour (I believe that is the default period).
> also, can you capture the --debug and --trace output for this error.
In the realm of all possibly annoying things to have happen, running it with
--debug and -
Hi Matt,
>
> Hi Dan,
> The error I'm getting is:
>
> Failed to retrieve current state of resource: Could not retrieve file
> metadata for puppet:///modules/rhnsd/rhnsd: at
> /etc/puppet/modules/rhnsd/manifests/init.pp:22
>
> can you show the file resource that this refers to (aka: the code)
How o
>>> On 17/12/2009 at 4:21 pm, Dan Bode wrote:
> Hi,
>
> I'm running into a problem whereby some nodes are struggling to retrieve the
>> metadata for files. I've moved all the nodes across to 0.25.1 to try and
>> eliminate version inconsistencies though they still appear. I've also
>> started us
I'm using mongrel for those 100 hosts.
>>> On 17/12/2009 at 4:17 pm, Ohad Levy wrote:
> You didnt mention, but are you using webrick with 100 hosts?
>
> Ohad
>
> On Thu, Dec 17, 2009 at 1:12 PM, Matthew Delves
> wrote:
>
>> Hey All,
>> I'm running into a problem whereby some nodes are struggl
Hi,
I'm running into a problem whereby some nodes are struggling to retrieve the
> metadata for files. I've moved all the nodes across to 0.25.1 to try and
> eliminate version inconsistencies though they still appear. I've also
> started using asynchronous stored configs as well.
>
can you be spe
You didnt mention, but are you using webrick with 100 hosts?
Ohad
On Thu, Dec 17, 2009 at 1:12 PM, Matthew Delves wrote:
> Hey All,
> I'm running into a problem whereby some nodes are struggling to retrieve
> the metadata for files. I've moved all the nodes across to 0.25.1 to try and
> eliminat
Hey All,
I'm running into a problem whereby some nodes are struggling to retrieve the
metadata for files. I've moved all the nodes across to 0.25.1 to try and
eliminate version inconsistencies though they still appear. I've also started
using asynchronous stored configs as well.
I'm wondering i
I use foreman dashboard* :)
it provides me an overview of all hosts in their latest status - e.g. all
OK, Active(puppet did something), Error (puppet reported an error, or out of
sync (puppet is not running).
and of course you can get the host list when you click on each of the
statuses.
additio
Hi,
I was wondering what people out there are doing to monitor puppetd in
large environments. I'd love to hear what the best practices are around
this.
We have a few hundred hosts and are currently looking at the timestamps
on the yaml files in /var/lib/puppet/yaml/facts/ on puppetmasters t
Yes all of this is very convoluted, but not because of my mind,
just because Puppet PARSER is too strict and prevents states that can
exists in the real.
No, i do not try to use exec to change the change the state of the
service which is -executed- elsewhere (i aggree it would be stupid and
There a few custom reports already in foreman (including email summary
notification*1), I'll be happy to add more use cases if you add feature
requests :)
cheers,
Ohad
[1] http://theforeman.org/wiki/foreman/Summarized_E-Mail_Reports
On Thu, Dec 17, 2009 at 1:39 AM, JL wrote:
> Is it possible
Rein Henrichs wrote:
>
>
> You do not have to configure individual puppet clients.
>
That's awesome... I thought I would have to have the report processor on
each node.
--
Joe McDonagh
Operations Engineer
Silent Penguin Services
AIM: YoosingYoonickz
IRC: joe-mac on freenode
www.colonfail.com
Hi,
Is it possible to disable tagmail reports for one environment but not
> another? For example, when I run 'puppetd --test --
> environment=testing', I do not want to receive an email. I tried
> adding "!testing" to to tagmail.conf, but that didn't work.
>
you can access a hosts environment (
Hrrm. I haven't previously messed with 'reports' or even external node
generation. What do I need to do to tie into my existing vanilla
nodes.pp-style setup?
David
On Wed, Dec 16, 2009 at 09:29:33AM -0800, Rein Henrichs wrote:
>Hi folks,
>Dashboard doesn't (currently) use stored config
On 12/16/2009 01:06 PM, jokeeffe wrote:
> OK, here is my problem. I have 2 different versions of openssl from 2
> different repos. Our organization is using the standard openssl
> package for just about everything and want to make sure it current.
> Then we have a special package that has its singl
No, I definitely agree and its a bad practice. Unfortunately, its out
of my control.
On Dec 16, 12:14 pm, Ian Ward Comfort
wrote:
> On 16 Dec 2009, at 10:06 AM, jokeeffe wrote:
>
> > OK, here is my problem. I have 2 different versions of openssl from
> > 2 different repos. Our organization is u
On 16 Dec 2009, at 10:06 AM, jokeeffe wrote:
> OK, here is my problem. I have 2 different versions of openssl from
> 2 different repos. Our organization is using the standard openssl
> package for just about everything and want to make sure it current.
> Then we have a special package that ha
OK, here is my problem. I have 2 different versions of openssl from 2
different repos. Our organization is using the standard openssl
package for just about everything and want to make sure it current.
Then we have a special package that has its single dependency on our
own custom version of openss
Is it possible to disable tagmail reports for one environment but not
another? For example, when I run 'puppetd --test --
environment=testing', I do not want to receive an email. I tried
adding "!testing" to to tagmail.conf, but that didn't work.
Alternatively, I would like to add a statement to
Hi folks,
Dashboard doesn't (currently) use stored configs or existing reports. The
README.markdown file in your Dashboard directory has instructions on using
the included puppet_dashboard report processor with your puppetmasterd to
send reports to the Dashboard. Please let me know if you run into
tomholl wrote:
> I was able to get puppet-dashboard up and running on my existing
> puppet server and the interface looks great. However none of my
> existing puppet environment activity is showing up in the puppet-
> dashboard.
>
> I have successfully setup puppetshow and storeconfigs in a prior
>
This looks really great. I will definately look into this approach. Thanks
for the tip!
Regards,
Kenneth
On Thu, Dec 10, 2009 at 12:47 PM, Ohad Levy wrote:
> You might consider using extlookup (http://nephilim.ml.org/~rip/puppet/*
> extlookup*.rb)
> or if you use foreman, you could define vari
I was able to get puppet-dashboard up and running on my existing
puppet server and the interface looks great. However none of my
existing puppet environment activity is showing up in the puppet-
dashboard.
I have successfully setup puppetshow and storeconfigs in a prior
installation of puppet and
On Tuesday 15 December 2009 23:39:31 Douglas Garstang wrote:
> And... even then I'd be requiring a definition, not a class. Is that
> even valid? How would the syntax look?
Definition is like a custom type so
define foo() {}
foo {'bar':}
file {'/tmp/bar': require => Foo['bar'] }
--
Michae
28 matches
Mail list logo
