kevbuk-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org
2008-Jul-30 13:20 UTC
Rails Error: Unable to access log file...
I cannot get rails/passenger to write to my production log :( 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Seemingly Similar Threads
- Premature end of script headers error using Rails 2.3.1 and Passenger 2.1.1
- ror 3 + apache2 + passenger = apache test page
- How do I confirm importing repo key without user intervention?
- Puppetmaster setup with separate CA server configuration help
- pasenger does not start puppet master under nginx