On Wed, Sep 1, 2010 at 4:55 PM, Patrick wrote:
>
> On Sep 1, 2010, at 5:28 AM, Héctor Rivas Gándara wrote:
>> I still have random "Segmentation Faults" with ruby on AIX. I will
>> ignore them for the moment until I will compile last ruby source (may
>> be 1.9.x) and test it.
> I remember reading s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> On Sep 1, 2010, at 5:28 AM, Héctor Rivas Gándara wrote:
>> I still have random "Segmentation Faults" with ruby on AIX. I will
>> ignore them for the moment until I will compile last ruby source
>> (may be 1.9.x) and test it.
>
>
> I remember readi
On Sep 1, 2010, at 5:28 AM, Héctor Rivas Gándara wrote:
> I still have random "Segmentation Faults" with ruby on AIX. I will
> ignore them for the moment until I will compile last ruby source (may
> be 1.9.x) and test it.
I remember reading somewhere that puppet isn't compatible with 1.9.x versi
2010/8/30 Héctor Rivas Gándara :
>>> The errors appear once or two times, randomly, and if I execute the
>>> client again it works properly. They are usually these kind of errors:
>> You will probably find life improved by deploying
>> another mode of operation for the puppetmaster daemon, and us
> We monitor the logs the same way we monitor for any other failures in our
> system. I would generally suggest you take the same approach, since it means
> you don't have two distinct processes for detecting problems.
> (In my case, that involves both 'logcheck' as per the Debian package, and
>
Héctor Rivas Gándara writes:
> I am using puppet 2.6.1rc3 in a test environment with AIX, Suse,
> Debians. Right now there are 5 clients... I am running puppet from cron
> each 30m (using random minute per host). I have prepared a configuration
> ready to deploy puppet in all our infrastructure
Hello,
I am using puppet 2.6.1rc3 in a test environment with AIX, Suse,
Debians. Right now there are 5 clients... I am running puppet from
cron each 30m (using random minute per host). I have prepared a
configuration ready to deploy puppet in all our infrastructure.
If I deploy and use it every
