Hi Felix,

Catalog compile time is around 10 seconds
One Node:
Nov 14 14:25:20 puppetmaster01 puppet-master[6884]: Compiled catalog for 
test-www01-xxx-com.xxxxx.net in environment test in 6.24 seconds

On my search i also find this curious behavior. Any ideas why?
Nov 15 22:08:00 puppetmaster01 puppet-master[27680]: Compiled catalog for 
rpm-repo.xxxxxx.com in environment production in 2.94 seconds
Nov 15 22:40:00 puppetmaster01 puppet-master[27680]: Compiled catalog for 
rpm-repo.xxxxxx.com in environment production in 122.44 seconds
Nov 15 23:07:59 puppetmaster01 puppet-master[27659]: Compiled catalog for 
rpm-repo.xxxxxx.com in environment production in 2.18 seconds

I also found this message in log file. Possible a PuppetDB performance 
problem?
Nov 16 00:41:58 puppetmaster01 puppet-master[27659]: Could not retrieve 
resources from the PuppetDB at puppetmaster01.xxxxxxx.com:8081: 
Net::ReadTimeout on node rpm-repo.xxxxxxxxx.com

CPU load average: 0,19, 0,18, 0,15 (values from top at the moment)

At the moment i have around 200 nodes (most nodes with empty catalog). 
Every node connect every 30 minutes to puppet master.

In last days i play a little bit with puppet-load.rb (found in 
/usr/share/puppet/ext). 35 nodes with 10 repeats give a good availability 
of the puppetmaster service.

greetings
Philipp

Am Montag, 10. November 2014 09:59:49 UTC+1 schrieb Felix.Frank:
>
> Hi, 
>
> how long does it take to compile one catalog? Examine the puppetmaster 
> logfile. 
>
> How many agents are there and how frequently do they check in? 
>
> Depending on the scale of your agent network, 4 CPUs may actually be too 
> few. The master is almost always CPU bound. 
>
> Cheers, 
> Felix 
>
> On 11/01/2014 09:58 PM, Philipp Dallig wrote: 
> > Hi, 
> > Nodes with a filled catalog runs from time to time in: Could not 
> > retrieve catalog from remote server: execution expired 
> > In my opinion i have a strong puppetmaster. 
> > Some Facts: 
> > max memory: 4 GB RAM (in average more then 2 GB free) 
> > load average: 0,14 
> > 4 vCPU 
> > visualization with lxc 
> > OS: CentOS7 
> > HostOS: CentOS 7 
> > Puppetmaster Version: 3.7 
> > Puppet Agents Version: 3.4+ 
> > Passenger-Version: 4.0.50 
> > PuppetDB in the same Container 
> > 
> > I have Foreman as an ENC, Foreman runs on the same Host in an other LXC 
> > Container. 
> > 
> > Postgres 9.1 for Foreman und PuppetDB is on an other Host. 
> > 
> > At the moment i have no more ideas, how i can solve this problem. 
> > 
> > Maybe a passenger-memory-stats report help for a solution 
> > 
> > 
> > 
> > ---------- Apache processes ---------- 
> > PID    PPID  VMSize     Private  Name 
> > -------------------------------------- 
> > 1571   1     126.6 MB   4.1 MB   /usr/sbin/httpd -f 
> > /www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start 
> > 15954  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
> > /www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start 
> > 15955  1571  2006.7 MB  6.9 MB   /usr/sbin/httpd -f 
> > /www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start 
> > 15957  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
> > /www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start 
> > 15959  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
> > /www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start 
> > 15966  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
> > /www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start 
> > ### Processes: 6 
> > ### Total private dirty RSS: 38.18 MB 
> > 
> > 
> > -------- Nginx processes -------- 
> > 
> > ### Processes: 0 
> > ### Total private dirty RSS: 0.00 MB 
> > 
> > 
> > ----- Passenger processes ----- 
> > PID    VMSize    Private  Name 
> > ------------------------------- 
> > 15936  212.2 MB  0.3 MB   PassengerWatchdog 
> > 15939  879.7 MB  1.0 MB   PassengerHelperAgent 
> > 15945  215.4 MB  0.9 MB   PassengerLoggingAgent 
> > 16119  465.8 MB  79.8 MB  Passenger RackApp: 
> > /www/sites/puppetmaster.mycompany.com/puppetmasterd 
> > 16126  465.9 MB  78.4 MB  Passenger RackApp: 
> > /www/sites/puppetmaster.mycompany.com/puppetmasterd 
> > 16135  466.0 MB  82.9 MB  Passenger RackApp: 
> > /www/sites/puppetmaster.mycompany.com/puppetmasterd 
> > 16144  530.9 MB  96.9 MB  Passenger RackApp: 
> > /www/sites/puppetmaster.mycompany.com/puppetmasterd 
> > ### Processes: 7 
> > ### Total private dirty RSS: 340.24 MB 
> > 
> > 
> > 
> > If someone need more informations, let me know. 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Puppet Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to [email protected] <javascript:> 
> > <mailto:[email protected] <javascript:>>. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/9748f970-59fd-4621-8944-84bae189072d%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/puppet-users/9748f970-59fd-4621-8944-84bae189072d%40googlegroups.com?utm_medium=email&utm_source=footer>.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/cb30c37e-fb59-4d41-9631-a7f9ea38d848%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to