While I was looking through redmine for interesting features to vote for, I came across #17190.
This indicates that there is not currently a good way to get the information that you are looking for.
However, towards the end of that ticket it references another ticket that indicates the framework for this functionality may be in place, it'd just be a matter of someone patching it in.
Probably just adding "--debug" to the puppet master config in /etc/default/puppetmaster or /etc/sysconfig/puppetmaster might be enough to find the source of your problem. Just have a look to syslog or the puppetmaster logfile.
Alternatively you should look at the problem from the point of view of the operating system (i.e. resource usage).
Probably you can gain also some useful information using "strace" on the process id of your puppetmaster: (start strace, repdroduce your problem, stop tracing with CTRL+c)
strace -frvT -s128 -o /tmp/<filename for trace ouput> -p <puppetmaster pid>
You will get output ... (more)
Asked: 2013-02-04 16:58:58 -0500
Seen: 781 times
Last updated: May 06 '13