Hello Dimitris, I had a similar problem. Not really sure where it came from. The permission seems to be all fine. I manage to get over the problem by starting the mongrel cluster manually as the following:
sudo mongrel_rails cluster::configure -p 8000 -N 2 sudo mongrel_rails cluster::start It worked for me. The problem seems to be in setting up the group permission for the mongrel cluster. Did you find the cause of the error? ./Carl On Jun 14, 1:28 pm, dimitris <[EMAIL PROTECTED]> wrote: > All, > > This is possibly a deprec issue, but may relate to Capistrano as well. > In any case, this list is more active than deprec, so I'm hoping that > someone has experienced similar problems and can help. > > In short, my deprec/capistrano tasks are executed loosely following > the "use deprec/capistrano to simplify your life" post at slicehost, > seehttp://wiki.slicehost.com/doku.php?id=automated_rails_install_and_dep.... > > It seems that most tasks execute successfully, except for starting a > mongrel cluster. The tasks themselves do not report a problem, but > looking through the mongrel and apache logs, it's clear that something > is not done right. > > Setup: > Ubuntu server 7.0.4 > Capistrano 1.4.1 > Deprec 1.7.1 > > relevant snippets from the mongrel log on the server > > (mongrel.log) > ** Daemonized, any open files are closed. Look at log/mongrel. > 8000.pid and log/mongrel.log for info. > ** Starting Mongrel listening at 127.0.0.1:8000 > ** Changing group to app_domaine. > ** Changing user to mongrel_domaine. > ** Starting Rails with production environment... > ** Daemonized, any open files are closed. Look at log/mongrel. > 8001.pid and log/mongrel.log for info. > ** Starting Mongrel listening at 127.0.0.1:8001 > ** Changing group to app_domaine. > ** Changing user to mongrel_domaine. > ** Starting Rails with production environment... > Rails Error: Unable to access log file. Please ensure that /var/www/ > apps/domaine/current/config/../log/production.log exists and is chmod > 0666. The log level has been raised to WARN and the output directed to > STDERR until the problem is fixed. > /usr/lib/ruby/1.8/fileutils.rb:1246:in `initialize': Permission denied > - /var/www/apps/domaine/current/config/../public/blank.html > (Errno::EACCES) > from /usr/lib/ruby/1.8/fileutils.rb:1246:in `open' > from /usr/lib/ruby/1.8/fileutils.rb:1246:in `copy_file' > from /usr/lib/ruby/1.8/fileutils.rb:1245:in `open' > from /usr/lib/ruby/1.8/fileutils.rb:1245:in `copy_file' > from /usr/lib/ruby/1.8/fileutils.rb:1215:in `copy' > from /usr/lib/ruby/1.8/fileutils.rb:447:in `copy_entry' > from /usr/lib/ruby/1.8/fileutils.rb:1308:in `traverse' > from /usr/lib/ruby/1.8/fileutils.rb:445:in `copy_entry' > ... 38 levels... > from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > command.rb:211:in `run' > from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/ > mongrel_rails:243 > from /usr/bin/mongrel_rails:16:in `load' > from /usr/bin/mongrel_rails:16 > Rails Error: Unable to access log file. Please ensure that /var/www/ > apps/domaine/current/config/../log/production.log exists and is chmod > 0666. The log level has been raised to WARN and the output directed to > STDERR until the problem is fixed. > /usr/lib/ruby/1.8/fileutils.rb:1246:in `initialize': Permission denied > - /var/www/apps/domaine/current/config/../public/blank.html > (Errno::EACCES) > from /usr/lib/ruby/1.8/fileutils.rb:1246:in `open' > from /usr/lib/ruby/1.8/fileutils.rb:1246:in `copy_file' > from /usr/lib/ruby/1.8/fileutils.rb:1245:in `open' > from /usr/lib/ruby/1.8/fileutils.rb:1245:in `copy_file' > from /usr/lib/ruby/1.8/fileutils.rb:1215:in `copy' > from /usr/lib/ruby/1.8/fileutils.rb:447:in `copy_entry' > from /usr/lib/ruby/1.8/fileutils.rb:1308:in `traverse' > from /usr/lib/ruby/1.8/fileutils.rb:445:in `copy_entry' > ... 38 levels... > from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ > command.rb:211:in `run' > from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/ > mongrel_rails:243 > from /usr/bin/mongrel_rails:16:in `load' > from /usr/bin/mongrel_rails:16 > > Changing to other users to run mongrel as (the deploy user, the first > user on installation of the server) makes no difference whatsoever. In > addition, sometimes the file which makes the startup process choke can > be different. > > I haven't touched file rights and permissions, those are set by the > capistrano/deprec recipes. > > Has anyone experienced similar problems? Any help is highly > appreciated. > > TIA, > > /Dimitris --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
