Re: [Puppet Users] exec resource long runtime

2015-01-22 Thread Trevor Vaughan
Hi Royee, Try adding --evaltrace to your puppet run to see how long each resource is taking to apply. Thanks, Trevor On Sun, Jan 18, 2015 at 9:54 AM, Royee Tager royee...@gmail.com wrote: Hi Martin, Attached is the output of the commands: [root@labit-lg02 ~]# time

Re: [Puppet Users] exec resource long runtime

2015-01-18 Thread Royee Tager
Hi Martin, Attached is the output of the commands: [root@labit-lg02 ~]# time /usr/sbin/spacewalk-channel -l Unable to locate SystemId file. Is this system registered? real 0m1.125s user 0m0.120s sys 0m0.055s [root@labit-lg02 ~]# [root@labit-lg02 ~]# time /usr/sbin/rhnreg_ks

Re: [Puppet Users] exec resource long runtime

2015-01-18 Thread Martin Alfke
Please also keep in mind that puppet is doing more: require = Class['spacewalk::install'], There is another class which also gets executed. The 48 second is not only the command execution time. Its the whole catalog apply time. Puppet always checks whether it has do do something prior doing

Re: [Puppet Users] exec resource long runtime

2015-01-18 Thread Martin Alfke
The 48 seconds is the complete time the agent needs for the catalog. Within the catalog you are running two commands: spacewalk-channel -l and rhnreg. Please add both execution times when comparing. On 18 Jan 2015, at 08:29, Royee Tager royee...@gmail.com wrote: Hi, If I run the following

[Puppet Users] exec resource long runtime

2015-01-17 Thread Royee Tager
Hi, If I run the following command manually (time /usr/sbin/rhnreg_ks -v --serverUrl=http://spacewalk.example.com/XMLRPC --activationkey=1-aab07306b6f673c367ebecae2aa55f22 --force --nohardware --nopackages --novirtinfo --norhnsd -v), the runtime is 15 seconds. However, if the command is