We are moving to have our nagios servers generate their nagios configs based
on what services are installed on specific hosts (as well as the hosts
registering themselves). What we have found is that our runtimes have gone
through the roof on this and I'm trying to figure out why (summary below
from a puppet run). The config pull takes a while, but the majority of the
time is spent on the client side. Running puppet with -d has a large chunk
of this time with nothing being updated on the screen and one processor core
being pegged. We're running 2.6.9 on SL6.0 x86_64.
I'm not sure if I have an unreasonable number of resources and I need to do
things differently or if I have a problem on my client I need to address.
Any insight or direction to go down to continue debugging?
(Ignore the errors, side effect of this being a test build on a test
machine)
# time puppets -td
…..
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml;
using pson
[stall for a long time]
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml;
using pson
….
notice: Finished catalog run in 1094.09 seconds
Changes:
Total: 2
Events:
Success: 2
Failure: 3
Total: 5
Resources:
Skipped: 1
Total: 1566
Changed: 2
Failed: 3
Out of sync: 5
Time:
User: 0.00
Filebucket: 0.00
Host: 0.00
Mount: 0.01
Ssh authorized key: 0.01
Schedule: 0.01
Class: 0.01
Yumrepo: 0.03
Package: 0.23
Total: 108.87
Last run: 1315860016
File: 19.57
Exec: 29.27
Config retrieval: 52.20
Service: 7.53
real 20m47.707s
user 18m12.793s
sys 0m39.436s
#
Thanks,
jl
--
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.
