Rails Error: Unable to access log file

I cannot get rails/passenger to write to my production log :frowning:

On my production server in the apache error_log I get:


Rails Error: Unable to access log file. Please ensure that /my/app/
log/
production.log exists and is chmod 0666.

Doing the following using copy/paste to avoid path/typo confusion:

ls -la

drw-rw-rw- 2 apache apache 4096 Jul 30 11:41 .
drwxrwxr-x 14 apache apache 4096 Jul 30 11:41 …
-rw-rw-rw- 1 apache apache 0 Jul 30 11:32 /my/app/log/production.log

cat /my/app/log/production.log

Passenger is set to run as user ‘apache’, as is apache/httpd itself.
Relevant httpd.conf lines:


PassengerDefaultUser apache
PassengerUserSwitching off

I also set the log level to 3 which didn’t seem to add anything
relevant to this problem to the error_log.

I’m running on CentOS 5 and SELinux is disabled:

sestatus

SELinux status: disabled

Looking at the processes, Passenger and Rails seem to be running as
the correct user ‘apache’ as does httpd.

Can somoeone tell me where to look next please, I’m a bit lost now.

Cheers,

Kev

Hey Kev!

You ever find the solution to this issue?

Im running three rails apps on my server, all on the same version of
rails.

One of them runs fine, the other two kick up this error when I try to
start them.

Any clues would be helpful?

Thanks

Gav

[email protected] wrote:

I cannot get rails/passenger to write to my production log :frowning:

On my production server in the apache error_log I get:


Rails Error: Unable to access log file. Please ensure that /my/app/
log/
production.log exists and is chmod 0666.

Doing the following using copy/paste to avoid path/typo confusion:

ls -la

drw-rw-rw- 2 apache apache 4096 Jul 30 11:41 .
drwxrwxr-x 14 apache apache 4096 Jul 30 11:41 …
-rw-rw-rw- 1 apache apache 0 Jul 30 11:32 /my/app/log/production.log

cat /my/app/log/production.log

Passenger is set to run as user ‘apache’, as is apache/httpd itself.
Relevant httpd.conf lines:


PassengerDefaultUser apache
PassengerUserSwitching off

I also set the log level to 3 which didn’t seem to add anything
relevant to this problem to the error_log.

I’m running on CentOS 5 and SELinux is disabled:

sestatus

SELinux status: disabled

Looking at the processes, Passenger and Rails seem to be running as
the correct user ‘apache’ as does httpd.

Can somoeone tell me where to look next please, I’m a bit lost now.

Cheers,

Kev

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs