Re: Installing mod_ruby on OS X and Apache 2

------=_Part_245_30228168.1156387031997
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

If your Apache installation is using the "worker" MPM, which is
thread-based, mod_ruby might not be compatible with that.  Perhaps you could
try switching to the "prefork" MPM, which is process-based (like Apache 1.3).
This might require compiling from source.  See
http://httpd.apache.org/docs/2.0/mod/ for details on the different MPM's
available.

Ted Behling
[email protected]

On 8/22/06, Alex Schearer <[email protected]> wrote:
>
> Hi, I'm using the latest OS X (I guess that's 10.4.7), Apache 2 and
> Ruby 1.8.4; so far all of these things are working great.  I am able
> to access my server, I can run other scripts -- php for example --
> and I can also run ruby through terminal.  I was even able to compile
> mod ruby successfully, yet everything is not OK.  The problem occurs
> when I try to load a ruby file or even enter a directory with ruby
> support.  I followed the instructions on the Wiki doc and eventually
> created the directory /Library/WebServer/Documents/ruby, when I
> access this directory I get a 500 internal server error.  So I
> checked my error logs and found the following:
> mod_ruby: error in ruby
> mod_ruby: from /usr/local/lib/ruby/1.8/apache/ruby-run.rb:53in `handler`
>
> mod_ruby: error in ruby
> mod_ruby: /Library/WebServer/Documents/ruby:0:in `value`: Thread
> (0x13e5740): deadlock (fatal)
>
> So there's the error, I guess now I should give you a little more
> information about my installation.  Apache is installed in /usr/local/
> apache2, Ruby is installed in /usr/local/bin, I compiled ruby with
> pthread enabled (a message came up without it enabled recommending
> that I enable it) and with apxs.
>
> I hope that is enough to work with, feel free to ask for any other
> information.  Thanks for any help, Alex.
>
>

------=_Part_245_30228168.1156387031997--