Did anyone find a resolution to this problem? I am getting the same
thing with Solaris and have tried both 2.2.2 and 2.2.5 and get "Error
400 on SERVER: Bad Request" with both versions.
passenger-status seems to work properly:
passenger-status
--- General information ---
max
On Tue, Oct 20, 2009 at 9:36 PM, Matt wrote:
>
> I'd really bite the bullet Stephen and give passenger 2.2.2 a try.
OK - tried passenger 2.2.2 - same behaviour.
I'm going to blow everything away and start again from scratch and see
if I get the same results.
S.
--
Stephen Nelson-Smith
Technic
I'd really bite the bullet Stephen and give passenger 2.2.2 a try.
2009/10/20 Stephen Nelson-Smith :
>
> Hi,
>
> On Tue, Oct 20, 2009 at 9:25 AM, Matt wrote:
>>
>> Stephen FWIW, I has issues getting it to work with passenger 2.2.5 and
>> settled on version 2.2.2 installed using the gem install p
Hi,
On Tue, Oct 20, 2009 at 9:25 AM, Matt wrote:
>
> Stephen FWIW, I has issues getting it to work with passenger 2.2.5 and
> settled on version 2.2.2 installed using the gem install passenger
> -version 2.2.2
I'm still on 2.2.5. I've been able to exchange SSL certs, but now if
I run puppet on
Stephen FWIW, I has issues getting it to work with passenger 2.2.5 and
settled on version 2.2.2 installed using the gem install passenger
-version 2.2.2
Thanks,
Matt
2009/10/19 Stephen Nelson-Smith :
>
> Hello,
>
> I really didn't expect this to be difficult, but I've been struggling
> with thi
Hi Julian,
On Mon, Oct 19, 2009 at 7:32 PM, Julian Simpson wrote:
>
> Is there a file called rewindable_input.rb on the system? Looks like a
> missing gem or ruby path issue.
Thanks Julian - I think the problem is that rubygem-rack from EPEL is
an old version that doesn't contain rewindable_inp
Is there a file called rewindable_input.rb on the system? Looks like a
missing gem or ruby path issue.
J.
Sent from my iPhone
On 19 Oct 2009, at 18:52, Stephen Nelson-Smith
wrote:
>
> Hello,
>
> I really didn't expect this to be difficult, but I've been struggling
> with this all day :(
>
