Héctor Rivas Gándara <[email protected]> writes:
> I am using puppet 2.6.1rc3 in a test environment with AIX, Suse,
> Debians. Right now there are 5 clients... I am running puppet from cron
> each 30m (using random minute per host). I have prepared a configuration
> ready to deploy puppet in all our infrastructure.
>
> If I deploy and use it everywhere, need to known each error. That is my
> first question How is the best way to report failures in puppet
> configuration?
We monitor the logs the same way we monitor for any other failures in our
system. I would generally suggest you take the same approach, since it means
you don't have two distinct processes for detecting problems.
(In my case, that involves both 'logcheck' as per the Debian package, and
Splunk, together with a network-wide reliable log collection facility.)
> I was using the email aproach, but I am having lots of random errors
> in clients that make the puppet runs fail and send a report error. For
> 5 hosts I am receiving around 150 emails/day. I do not known if this
> is normal.
No. You should receive zero error messages per day.
> The errors appear once or two times, randomly, and if I execute the
> client again it works properly. They are usually these kind of errors:
I bet that you are still using the default webrick puppetmaster configuration,
and I see you are using sqlite with storedconfigs.
Neither of those is really very good at scale, and "scale" doesn't mean very
many nodes I am afraid. You will probably find life improved by deploying
another mode of operation for the puppetmaster daemon, and using a real
database (I use PostgreSQL) for storedconfigs.
[...]
> Mon Aug 30 12:57:18 +0200 2010 //puppetclient.myhost.com/Puppet (err):
> Could not save yaml puppetclient.myhost.com: class or module required
That looks troublingly like a local Ruby problem of some sort.
> I also get sometimes some errors from cron output like these:
>
> Could not run: method `directory?' called on terminated object (0x2005051c)
> /usr/local/lib/ruby/site_ruby/1.8/puppet/util/zaml.rb:243: [BUG]
> Segmentation fault ruby 1.8.7 (2009-06-12 patchlevel 174) [rs6000-aix]
> /srv/scripts/puppet/puppet.ctl.sh: line 117: 319712 IOT/Abort trap
> (core dumped) $PUPPETD ${PUPPET_OPTS} ${PUPPET_EXTRA_OPTS}
> --onetime --no-daemonize --verbose
>
> Is this normal?
Core dumps in Ruby are absolutely not normal, and are a sign you should look
to upstream Ruby support for fixing the problem with your interpreter.
It is hard to say how many of the other errors (other than sqlite locking)
might be caused by underlying Ruby problems, so that sounds like a really good
place to start on resolving this trouble.
Regards,
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
