sorry for the late reply :)
but yes, I have switched to passenger.
Gus
On Tue, Sep 29, 2009 at 5:22 PM, Chris Westin wrote:
>
> I'm getting similar messages about cacrl, even though I haven't set
> it. Did switching to passenger fix the problem? Or did you find
> another way to fix it?
>
> I
I'm getting similar messages about cacrl, even though I haven't set
it. Did switching to passenger fix the problem? Or did you find
another way to fix it?
I'm using webrick and don't want to complicate things further for now
if I don't have to.
Chris
--~--~-~--~~~-
thanks Pete.. I will use passenger for sure... I were beginning to think
that the problem that I face when migrating from 0.24.8 to 0.25.0rc1 (which
I had already rolled back) was somehow connected to Webrick.. but I guess
not...
Cheers
On Thu, Aug 20, 2009 at 4:27 PM, Peter Meier wrote:
>
> Hi
Hi
> for now I haven't setup apache + passenger yet. I was running some tests in
> a lab environment first with the builtin webserver (I believe that it is
> Webrick, right?) and then I would setup passenger to increase sacalability.
> I must use passenger in 0.25.x?
no, you can still use webric
Larry,
for now I haven't setup apache + passenger yet. I was running some tests in
a lab environment first with the builtin webserver (I believe that it is
Webrick, right?) and then I would setup passenger to increase sacalability.
I must use passenger in 0.25.x?
Gus
On Thu, Aug 20, 2009 at 10:0
On Aug 19, 2009, at 3:42 PM, Gustavo Soares wrote:
> Hi all!
>
> I have migrated some machines from puppet 0.24.8 to 0.25.0rc1,
> mainly because of bug in 0.24.8 when using ssh_authorized_keys and I
> am getting the following messages when starting the client:
>
> Setting the :cacrl to 'fals