Hi luke,
thanks for quick reply. as i m able to see that puppet master taking around 7-8 seconds to compiler catalog and puppet client taking around 1106 second to apply catalog . seems strange , because some manifest and configuration (on both master and client) working fine with dozens of servers concurrently. Since Sunday getting strange behavior........ feel free to ask, if some more input required to resolve d issue. thanks, Sanjiv Singh On Jul 4, 8:32 pm, Luke Bigum <luke.bi...@lmax.com> wrote: > Sanjiv, > > How long does your master think that catalog compilation is taking? > Look for these lines: > > Jul 4 15:13:53 puppetmaster puppet-master[26138]: Compiled catalog > for puppetclient in environment live in 0.12 seconds > > And then the time for the agents applying that catalog: > > Jul 4 15:13:55 puppetclient puppet-agent[24198]: Finished catalog run > in 1.22 seconds > > -Luke > > On Jul 4, 4:13 pm, "sanjiv.singh" <sanjiv.si...@impetus.co.in> wrote: > > > > > > > > > On Jul 4, 7:36 pm, Ken Barber <k...@puppetlabs.com> wrote: > > > > > my manifest contains number of file (flat and templete ) and for > > > > pulling some jars on client. > > > > I guess I was looking to find out the specifics of how big these > > > manifests and templates are in total on the nodes you are having > > > specific performance issues with. You say 'big manifests' but this is > > > a relative statement :-). > > > > If 'nothing has changed' (please confirm this with your svn/git > > > history) then it must be something else other then content or puppet > > > itself .... > > > > Without seeing your content its a hard one to trace via a mailing > > > list, there could be a network issue and some function you are trying > > > to execute could be lagging or having trouble resolving dns etc. Try > > > running your puppetmasterd in the foreground using something like: > > > > puppetmasterd --no-daemonize --debug --trace --logdest console > > > > And as you do a single run, see if it gives you any clues as to what > > > its blocking on during those 20 minutes. > > > > ken. > > > Hi Ken, > > thanks for quick reply. > > > as per yr suggestion , > > > sudo /usr/sbin/puppetmasterd --no-daemonize --debug --trace --logdest > > console > > > fired in puppet master........ > > there is noting seems wrong in debug trace...., only taking time to > > do stuff. > > > these is some clue for you that may help you to find out root cause. > > i have configured puppet master to log in file /var/log/puppet/ > > masterhttp.log > > > . > > . > > . > > . > > . > > [2011-07-04 10:57:18] DEBUG close: 10.122.130.1:45575 > > [2011-07-04 10:57:24] DEBUG Puppet::Network::HTTP::WEBrickREST is > > invoked. > > [2011-07-04 10:57:24] 209.251.184.24 - - [04/Jul/2011:10:57:24 EDT] > > "GET/production/file_metadata/production/tomcat-web.xml HTTP/1.1" 200 > > 391 > > [2011-07-04 10:57:24] - -> /production/file_metadata/production/tomcat- > > web.xml > > [2011-07-04 10:57:24] DEBUG close: 209.251.184.24:20132 > > [2011-07-04 10:57:24] DEBUG accept: 10.122.130.1:8767 > > [2011-07-04 10:56:33] ERROR OpenSSL::SSL::SSLError: > > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: > > 44:in `accept' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: > > 44:in `listen' > > /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' > > /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' > > /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' > > /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' > > /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' > > /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' > > /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' > > /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' > > /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: > > 42:in `listen' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: > > 41:in `initialize' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: > > 41:in `new' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: > > 41:in `listen' > > /usr/lib/ruby/1.8/thread.rb:135:in `synchronize' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb: > > 38:in `listen' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:131:in > > `listen' > > /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:146:in > > `start' > > /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:128:in `start' > > /usr/lib/ruby/site_ruby/1.8/puppet/application/ > > puppetmasterd.rb:122:in `main' > > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in > > `send' > > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in > > `run_command' > > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in > > `exit_on_fail' > > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > > /usr/sbin/puppetmasterd:66 > > > there are in log repetted error trace for each file puppet master > > serving to client. > > > thanks, > > Sanjiv singh -- 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.
