Hi Steven,
I ran into the same problem this morning when rolling some new facter/
puppet packages for RHEL4. Going back to facter 1.5.2 seems to be a
usable workaround at the moment.
-ryan
On Feb 5, 10:48 am, "Steven Nemetz" wrote:
> > On Feb 4, 2009, at 6:49 PM, Steven Nemetz wrote:
>
> > >
> -Original Message-
>
> What about if you run Facter with --puppet, making sure it loads your
> custom facts?
>
> --
> Due to circumstances beyond your control, you are master of your fate
> and captain of your soul.
> --
On Feb 5, 2009, at 11:48 AM, Steven Nemetz wrote:
>>>
>>> Anyone have any ideas what could have happened to these 4 systems?
>>
>> Might you have a fact that's broken, or something similar? That's
>> been the cause of 99% of the startup hangs I've seen.
>>
>> --
>> It isn't necessary to have rela
> On Feb 4, 2009, at 6:49 PM, Steven Nemetz wrote:
>
> > All my puppet clients were running ok.
> > Then 2 things happened yesterday:
> > 1) I had puppet upgrade facter to 1.5.3 everywhere. Most were
> > running 1.3.8 prior.
> > 2) We had network problem, causing one of our datacente
On Feb 4, 2009, at 6:49 PM, Steven Nemetz wrote:
> All my puppet clients were running ok.
> Then 2 things happened yesterday:
> 1) I had puppet upgrade facter to 1.5.3 everywhere. Most were
> running 1.3.8 prior.
> 2) We had network problem, causing one of our datacenters to
> go
