error during cap deploy: unable to access log file
bear opened this issue · comments
*** [err :: localhost] Rails Error: Unable to access log file. Please ensure that /home/kochiku-web/kochiku/releases/20130908071331/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.
*** [err :: localhost] rake aborted!
*** [err :: localhost] No such file or directory - /home/kochiku-web/kochiku/releases/20130908071331/log/bullet.log
why does it not create the log directory itself?
also, seriously, chmod 666 ?
turns out this may be a rails bug (but I'm not a ruby or rails person anymore) - it sure looks like this:
http://stackoverflow.com/questions/632592/rails-unable-to-access-log-file
but since the release dir is removed when it fails, I am not sure
Does running cap deploy:cold on your first deploy fix this and #4 ?
If so, we should edit the installation instructions to suggest that.
Agree that 0666 sounds like a bad solution; a pull request to Rails (or Capistrano or whatever prints that message may be in order, if they haven't already fixed it).
That stackoverflow doesn't look like it because I didn't find config.log_level in the kochiku sources.
cap deploy:cold does seem to get past the directory error but it still fails with the access log error.
Running cap deploy:setup fixed this for me.
this is probably a docs issue, standard cap first time builds are cap deploy:setup deploy:cold and then cap deploy thereafter
also, you shouldn't need to cap deploy to run it locally, can't you just rails server it?
That would have been good to know :-) the instructions read like a deploy
was required
not at desk, terse verse observed
On Sep 10, 2013 8:49 PM, "Aaron Jensen" notifications@github.com wrote:
also, you shouldn't need to cap deploy to run it locally, can't you just rails
server it?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-24205954
.
Is the week now accurate? In particular, is cap deploy:setup enough or does one also need to run cap deploy: cold?
My experience was that cap deploy:setup and cap:deploy were enough. But then you might also want cap deploy:create_symlink after that, to make the 'latest release' symlink.
Pretty sure that cap deploy:create_symlink is part of cap deploy. Anyway, I'm closing this issue; if there is anything else left we can open new ones.