On Thu, 9 Sep 2010 11:43:44 +0200, Sandor Szuecs
wrote:
> On Sep 8, 2010, at 9:45 PM, James Cammarata wrote:
>
>> Definitely ruby's fault on this one, apparently. The original system I
>> was
>> testing on is RHEL4, with ruby 1.8.1-7. I just tested the exact same
>> configs on a RHEL5 box with
On Sep 8, 2010, at 9:45 PM, James Cammarata wrote:
> Definitely ruby's fault on this one, apparently. The original system I was
> testing on is RHEL4, with ruby 1.8.1-7. I just tested the exact same
> configs on a RHEL5 box with ruby 1.8.5-5 and it worked flawlessly:
I guess ruby 1.8.1 is the
On Wed, 8 Sep 2010 12:13:04 -0700, Nigel Kersten wrote:
> On Wed, Sep 8, 2010 at 12:05 PM, James Cammarata wrote:
>>
>> On Wed, 8 Sep 2010 12:02:09 -0700, Nigel Kersten
>> wrote:
>>> On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata wrote:
> Just for the record, I have many tens of tho
On Wed, Sep 8, 2010 at 12:05 PM, James Cammarata wrote:
>
> On Wed, 8 Sep 2010 12:02:09 -0700, Nigel Kersten wrote:
>> On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata wrote:
>>>
Just for the record, I have many tens of thousands of 0.25.4-1
clients, and I've never ever seen this probl
On Wed, 8 Sep 2010 12:02:09 -0700, Nigel Kersten wrote:
> On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata wrote:
>>
>>> Just for the record, I have many tens of thousands of 0.25.4-1
>>> clients, and I've never ever seen this problem with pluginsync.
>>
>> Yep, just upgraded to 0.25.5-1 from EP
On Wed, Sep 8, 2010 at 11:39 AM, James Cammarata wrote:
>
>> Just for the record, I have many tens of thousands of 0.25.4-1
>> clients, and I've never ever seen this problem with pluginsync.
>
> Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same:
>
> [2010-09-08 14:34:51] myser
On Wed, 08 Sep 2010 13:39:34 -0500, James Cammarata wrote:
>> Just for the record, I have many tens of thousands of 0.25.4-1
>> clients, and I've never ever seen this problem with pluginsync.
>
> Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same:
>
> [2010-09-08 14:34:51] m
> Just for the record, I have many tens of thousands of 0.25.4-1
> clients, and I've never ever seen this problem with pluginsync.
Yep, just upgraded to 0.25.5-1 from EPEL and the issue/URL is the same:
[2010-09-08 14:34:51] myserver - - [08/Sep/2010:14:34:51 EDT] "GET
/production/file_metadatas
On Wed, Sep 8, 2010 at 9:53 AM, James Cammarata wrote:
>
> On Wed, 8 Sep 2010 09:46:15 -0700, Nigel Kersten
> wrote:
>> On Wed, Sep 8, 2010 at 9:25 AM, James Cammarata wrote:
>>>
> The only way to get rid of this error is to set the libdir variable,
> which
> I don't think is right.
On Wed, 8 Sep 2010 09:46:15 -0700, Nigel Kersten
wrote:
> On Wed, Sep 8, 2010 at 9:25 AM, James Cammarata wrote:
>>
The only way to get rid of this error is to set the libdir variable,
which
I don't think is right. Can anyone point out what I'm doing wrong
>> here?
The docum
On Wed, Sep 8, 2010 at 9:25 AM, James Cammarata wrote:
>
>>> The only way to get rid of this error is to set the libdir variable,
>>> which
>>> I don't think is right. Can anyone point out what I'm doing wrong
> here?
>>> The documentation on custom facts is pretty horrible, and is too much a
>>>
On Wed, 08 Sep 2010 11:25:39 -0500, James Cammarata wrote:
>>> The only way to get rid of this error is to set the libdir variable,
>>> which
>>> I don't think is right. Can anyone point out what I'm doing wrong
> here?
>>> The documentation on custom facts is pretty horrible, and is too much a
>> The only way to get rid of this error is to set the libdir variable,
>> which
>> I don't think is right. Can anyone point out what I'm doing wrong
here?
>> The documentation on custom facts is pretty horrible, and is too much a
>> mish-mash of old vs new methods.
>>
>
> So setting the factpat
On Tue, Sep 7, 2010 at 1:59 PM, James Cammarata wrote:
>
> I'm trying to setup a module to deploy custom facts, and I'm running into
> some issues.
>
> I've created a directory called "custom" in my modules directory, and
> created sub-directories there so I have custom/lib/facter (as is described
I'm trying to setup a module to deploy custom facts, and I'm running into
some issues.
I've created a directory called "custom" in my modules directory, and
created sub-directories there so I have custom/lib/facter (as is described
in the documentation).
On my puppetmaster, I've added this to fi
15 matches
Mail list logo
