Try the 'Starting and managing delayed job workers' section in here: http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
If the workers aren't running (and they don't run by default unless you follow the steps in that section) then you can see a backlog of tasks. On Thu, Feb 23, 2012 at 4:32 PM, Robert Stinnett <rob...@robertstinnett.com> wrote: > And what do we do about that? I've restarted the services, even > restarted the server and nothing comes back to life. > > Robert > > > On Feb 23, 9:10 am, Kenneth Lo <k...@paydiant.com> wrote: >> If that's the case I believe your pe-puppet-dashboard-workers service died >> somehow in your master. >> >> --KL >> >> On 2/23/12 9:51 AM, "Robert Stinnett" <rob...@robertstinnett.com> wrote: >> >> >> >> >> >> >> >> >> >> >We are using RHEL - 2.6.18-238.1.1.0.1.el5xen >> >> >I do not know of any recent kernel patches (let me put it this way -- >> >I didn't make any!). >> >> >If I go to the "Live Management" part of the dashboard I can control >> >the agents, etc -- but they won't do anything in the dashboard view >> >and it shows up as over 800 tasks are backlogged on them. >> >> >I've searched the log files I could find for any error messages, but >> >haven't found anything yet. It seems strange that the agents work in >> >command-line mode, and through the live management, but aren't via the >> >dashboard/cron process, >> >> >Thanks, >> >Robert Stinnett >> >> >On Feb 22, 3:53 pm, Aaron Grewell <aaron.grew...@gmail.com> wrote: >> >> Are you running RHEL 5? Did you recently patch your kernel? If so, >> >> you've probably been bitten by a kernel bug. I've successfully used >> >> kernel-2.6.18-274.17.1.el5 and backrev versions from the >> >> kernel-2.6.18-238.x.x series. >> >> >> On 02/22/2012 12:26 PM, Robert Stinnett wrote: >> >> >> > Hi there, >> >> >> > I am relatively new to Puppet (totally new) and had been cruising >> >> > right along for a few days until about a week ago when our puppet >> >> > agents went unresponsive. I've restarted both them and the servers >> >> > several times to no avail. Can anyone point me down the path of how >> >> > to diagnose this issue? We are currently evaluating Puppet to bring >> >> > into our Enterprise for managing server provisions/configs/etc. >> >> >> > Thanks, >> >> > Robert Stinnett >> >> >-- >> >You received this message because you are subscribed to the Google Groups >> >"Puppet Users" group. >> >To post to this group, send email to puppet-users@googlegroups.com. >> >To unsubscribe from this group, send email to >> >puppet-users+unsubscr...@googlegroups.com. >> >For more options, visit this group at >> >http://groups.google.com/group/puppet-users?hl=en. >> >> This message is for the designated recipient only and may contain >> privileged, proprietary, or otherwise private information. If you have >> received it in error, please notify the sender immediately and delete the >> original. Any other use of the email by you is prohibited. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
