Yeah, I have played with both max workers to 30 and PassengerMaxPoolSize to 30.
No change from my problem clients. So odd. Thank you for the suggestion. Rob On Tuesday, February 26, 2013 11:32:33 AM UTC-7, r.yeo wrote: > > Running the agent in debug mode on a some clients and I am seeing long run > times such as this, but only after the "using pson" lines : > > Tue Feb 26 10:57:38 2013: Debug: file_metadata supports formats: > b64_zlib_yaml pson raw yaml; using pson > Tue Feb 26 10:58:53 2013: Info: > /Stage[main]/Vpn::Config/File[/opt/cisco/vpn/.anyconnect_global]: Evaluated > in 75.03 seconds > > Tue Feb 26 10:58:53 2013: Debug: file_metadata supports formats: > b64_zlib_yaml pson raw yaml; using pson > Tue Feb 26 11:00:08 2013: Info: > /Stage[main]/Amadeuspro/File[/etc/puppet/tmp/com.HairerSoft.AmadeusPro.plist]: > > Evaluated in 74.78 seconds > Tue Feb 26 11:00:08 2013: Info: > /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Starting > to evaluate the resource > Tue Feb 26 11:00:08 2013: Debug: file_metadata supports formats: > b64_zlib_yaml pson raw yaml; using pson > Tue Feb 26 11:01:23 2013: Info: > /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Evaluated > in 75.00 seconds > > Tue Feb 26 11:01:23 2013: Debug: file_metadata supports formats: > b64_zlib_yaml pson raw yaml; using pson > Tue Feb 26 11:02:38 2013: Info: /Stage[main]/Puppet::Snow/File[/etc/hooks/ > cleanpup.pl]: Evaluated in 75.01 seconds > > This catalog took 921.02 to complete : > > Tue Feb 26 11:02:38 2013: Notice: Finished catalog run in 916.78 seconds > Tue Feb 26 11:02:38 2013: Changes: > Tue Feb 26 11:02:38 2013: Events: > Tue Feb 26 11:02:38 2013: Resources: > Tue Feb 26 11:02:38 2013: Total: 55 > Tue Feb 26 11:02:38 2013: Skipped: 6 > Tue Feb 26 11:02:38 2013: Time: > Tue Feb 26 11:02:38 2013: Filebucket: 0.00 > Tue Feb 26 11:02:38 2013: Package: 0.00 > Tue Feb 26 11:02:38 2013: Ssh authorized key: 0.00 > Tue Feb 26 11:02:38 2013: User: 0.06 > Tue Feb 26 11:02:38 2013: Group: 0.11 > Tue Feb 26 11:02:38 2013: Exec: 0.59 > Tue Feb 26 11:02:38 2013: Config retrieval: 13.28 > Tue Feb 26 11:02:38 2013: Last run: 1361901758 > Tue Feb 26 11:02:38 2013: File: 906.98 > Tue Feb 26 11:02:38 2013: Total: 921.02 > Tue Feb 26 11:02:38 2013: Version: > Tue Feb 26 11:02:38 2013: Config: 1361893868 > Tue Feb 26 11:02:38 2013: Puppet: 3.1.0 > > Also, this isn't global as I have nodes getting identical complete configs > in 7 seconds and run times are just fine after the using pson lines. > > Example of a fast node : > > Tue Feb 26 11:22:57 2013: Debug: file_metadata supports formats: > b64_zlib_yaml pson raw yaml; using pson > Tue Feb 26 11:22:58 2013: Info: > /Stage[main]/Amadeuspro/File[/etc/puppet/tmp/com.HairerSoft.AmadeusPro.plist]: > > Evaluated in 0.15 seconds > Tue Feb 26 11:22:58 2013: Info: > /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Starting > to evaluate the resource > Tue Feb 26 11:22:58 2013: Debug: file_metadata supports formats: > b64_zlib_yaml pson raw yaml; using pson > Tue Feb 26 11:22:58 2013: Info: > /Stage[main]/Adobe/File[/etc/puppet/tmp/com.adobe.Reader.plist]: Evaluated > in 0.07 seconds > > Puppet master and clients are 3.1 with Dashboard 1.2.22 and also using > PuppetDB. > > Any thoughts why I'd have trouble and long run times on select nodes when > pson is called? > > Thanks! > > -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
