search for: ip_to_cron

...evaluate: Not a directory - /var/lib/puppet/lib/puppet/parser/ functions/gsub.rb err: /File[/var/lib/puppet/lib/puppet/parser/functions/hostname.rb]: Could not evaluate: Not a directory - /var/lib/puppet/lib/puppet/ parser/functions/hostname.rb err: /File[/var/lib/puppet/lib/puppet/parser/functions/ip_to_cron.rb]: Could not evaluate: Not a directory - /var/lib/puppet/lib/puppet/ parser/functions/ip_to_cron.rb err: /File[/var/lib/puppet/lib/puppet/parser/functions/ network_lookup.rb]: Could not evaluate: Not a directory - /var/lib/ puppet/lib/puppet/parser/functions/network_lookup.rb err: /File[/var/lib/...

Hi everyone, I have a problem with my Puppet server, the server is overloaded and processes need to add half of my farm nodes yet! The server is hosted on a blade with the following characteristics: Processors: 8 cores Memory Ram: 12 Gb Operating System: Debian Squeeze Version of parcel: 2.7.1-1 ~ bpo60 puppet 1 puppet-common 2.7.1-1 ~ bpo60 1 2.7.1-1 ~ bpo60 1 puppetmaster puppetmaster 2.7.1-1 ~

Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as

...et/ namespaceauth_2.6.conf.erb"), }, require => Package["puppet"], } # puppet cron { "puppet": ensure => present, command => "/usr/local/bin/launch-puppet", user => "root", minute => ip_to_cron(2), require => [ File["/var/log/puppet"], File["/usr/local/bin/ launch-puppet"], File["/etc/profile.d/puppet.sh"], File["/etc/ profile.d/facterlibs.sh"] ], } # cron # setup paths file { "/etc/profile.d/puppet.sh": own...