On Mon, Sep 27, 2010 at 5:17 PM, Nigel Kersten <nig...@google.com> wrote:
> On Mon, Sep 27, 2010 at 5:09 PM, Douglas Garstang > <doug.garst...@gmail.com> wrote: > > On Mon, Sep 27, 2010 at 4:58 PM, Nigel Kersten <nig...@google.com> > wrote: > >> > >> On Mon, Sep 27, 2010 at 4:50 PM, Douglas Garstang > >> <doug.garst...@gmail.com> wrote: > >> > I'm trying to find a programmatic way to determine if the result of a > >> > puppetrun was ok. Rather than scraping /var/log/messages, is there > >> > another > >> > way to determine that a puppet run completed with errors and how long > it > >> > took to run? Is that state maintained on the client's disk somewhere? > >> > >> What version of Puppet? > > > > Nigel, > > 2.6.1. > > > >> > >> How are you running the agent? out of cron? or as a daemon? > >> > > > > Agent is running as a daemon. I'm running puppetrun --host=<host> on the > > puppetmaster. > > > >> > >> If you're running it out of cron, there's a —detailed-exitcodes > >> argument you can use to determine the client state. > >> > >> Have you looked at dumping a report at the end of your run and whether > >> that reports the info you want? > >> > >> > > Not yet... can I do that if I use puppetrun on the puppetmaster? > > I'm not much of an expert in puppetrun as we don't use it here. > > What's the end goal? Do you want centralized reports that you can > analyze? or you just want to know whether the run had errors with > ad-hoc puppetruns ? > > Nigel, the end goal is to not have to not have to log into the client every time I run puppet to see if puppet applied the updates correctly. I must be doing it a few hundred times a day and it's getting a bit old. Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
