On Tue, May 1, 2012 at 03:14, Kent <dri...@gmail.com> wrote: > I don't think it's issue #5752, I opened that issue and provided a > patch to resolve it. > When I build new versions of Puppet for my Solaris hosts I apply that > patch each time via my build script and I'm still having some hosts > where the crontab gets "eaten" and it always seems to correspond with > 'prtdiag' issues or timeouts. > > Facter has a timeout built in for prtdiag and then does a kill routine > if it needs to clean up. > I wonder if it's being overly agressive and accidentally killing some > or all of the Puppet run in turn causing this issue?
I agree, that I think this is probably what is happening. I've since stopped using puppet to manage our solaris crontab files since we can't currently fully puppetize our crontabs. Unfortunately, solaris doesn't have a cron.d directory where we can drop crontab files either. Romeo > On Mar 13, 5:31 pm, Greg <greg.b...@gmail.com> wrote: >> Have seen similar. Quite often when prtdiag fails to complete, I've >> found that restarting svc:/system/picl:default returns everything back >> to normal... >> >> Hopefully all your root cron jobs are in Puppet and will be rebuilt on >> the next run... >> >> Greg >> >> On Mar 14, 9:26 am, John Warburton <jwarbur...@gmail.com> wrote: >> >> >> >> >> >> >> >> > On 14 March 2012 09:16, Romeo Theriault <romeo.theria...@maine.edu> wrote: >> >> > > Here are the logs the solaris 10 box returns after it's crontab gets >> > > destroyed: >> >> > > ERR Puppet Could not prefetch cron provider 'crontab': Could not >> > > read >> > > crontab for root: No child processes >> > > NOTICE /Stage[main]/Puppet/Cron[puppet]/ensure created >> > > NOTICE Puppet Finished catalog run in 2.52 seconds >> >> > > After this the only thing that exists in the crontab is the entry we >> > > have puppet adding. >> >> > > I found this bug: >> >> > >http://projects.puppetlabs.com/issues/1672 >> >> > > which says there was a fix and it was merged but we're still seeing >> > > this issue... >> >> > > puppet agent v. 2.7.9 >> > > facter v. 1.6.5 >> >> > It could be this bug -https://projects.puppetlabs.com/issues/5752 >> >> > That andhttps://projects.puppetlabs.com/issues/9854arekeeping me from >> > pushing migrating to 2.7 up my priority list >> >> > Indeed, there are 5 issues marked Urgent in the 2.7.x bucket >> >> > John > > -- > 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. > -- Romeo -- 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.
