On Fri, Oct 29, 2010 at 9:17 PM, DMaster <compu...@gmail.com> wrote:
> [Fri Oct 29 14:11:36 2010] [error] *** Passenger could not be
> initialized because of this error: Unable to start the Phusion
> Passenger watchdog (/usr/local/lib/ruby/gems/1.8/gems/passenger-3.0.0/
> agents/PassengerWatchdog): Permission denied (13)
> [Fri Oct 29 14:11:36 2010] [notice] Apache/2.2.9 (Unix) DAV/2
> Phusion_Passenger/3.0.0 PHP/5.2.6 configured -- resuming normal
> operations
>
>
> Running Rails 2.3.8 on Fedora Core. 2.2.5 does not seem to have this
> issue. Not sure what file or directory it is complaining about?

As the error message indicates, it's complaining that it cannot access
/usr/local/lib/ruby/gems/1.8/gems/passenger-3.0.0/agents/PassengerWatchdog
because of a permission problem. You need to fix that.

--
Phusion | The Computer Science Company

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

On Fri, Oct 29, 2010 at 10:15 PM, Phil Dindak <compu...@gmail.com> wrote:
> Thanks but.......
>
> the dirs and files are all like this:
>
> -rwxr-xr-x 1 root root 2811952 2010-10-29 14:08 PassengerWatchdog
> drwxr-xr-x  3 root root  4096 2010-10-29 14:08 agents
>
> or is root not a good thing :)

You need to check *all* parent directories as well. Each one of them
must be executable by the web server process.

--
Phusion | The Computer Science Company

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

On Fri, Oct 29, 2010 at 10:48 PM, Phil Dindak <compu...@gmail.com> wrote:
> I did that previously- did not think I wanted to clutter up the message :)
> drwxr-xr-x  13 root root  4096 2010-10-27 16:24 usr
> drwxr-xr-x  11 root root  4096 2010-10-27 16:23 local
> drwxr-xr-x 4 root root 4096 2010-10-28 16:49 lib
> drwxr-xr-x 6 root root    4096 2010-10-28 16:42 ruby
> drwxr-xr-x 6 root root 4096 2010-10-28 16:42 1.8
> drwxr-xr-x 40 root root 4096 2010-10-29 14:05 gems
> drwxr-xr-x 13 root root 4096 2010-10-29 14:08 passenger-3.0.0
>
> Seems a little misleading here - the perms seem fine.

The only thing left that I can think of is SELinux interfering. Try
turning it off or setting it to permissive mode.
I know little about writing SELinux policies, so if anybody can
contribute and maintain a policy file that would be great.

--
Phusion | The Computer Science Company

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)