[
https://issues.apache.org/jira/browse/COUCHDB-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671703#action_12671703
]
Jan Lehnardt commented on COUCHDB-153:
--------------------------------------
Hi Ulises, thanks for the patch, we're getting there, but we're not quite there
yet.
- tabs -> spaces.
- there's a ?LOG_ERROR statement and an io:format() saying the same. I assume
we only need the ?LOG_ERROR.
- we're bailing out after the pretty error message gets logged. I don't think
there's a need to return a pretty State record and instead just stop() us,
which in turn stops couch_server_sup():
?LOG_ERROR("Couldn't create/access ~p (reason:~p)~n", [RootDir, Error]),
stop() % terminate CouchDB
- this still creates the rather ugly:
{"init terminating in
do_boot",{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{erl_eval,do_apply,5},{erl_eval,exprs,5},{init,start_it,1},{init,start_em,1}]}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
The badmatch happens in the Erlang application do_boot function and I don't
know if there's a way to catch errors there and the we've got to live with this
error, but it might be worth looking into options to make this nicer.
Again, thanks for your efforts. If you or anyone wants to pick this up, that'd
be great.
> Erlang should warn about log/data file permissions
> --------------------------------------------------
>
> Key: COUCHDB-153
> URL: https://issues.apache.org/jira/browse/COUCHDB-153
> Project: CouchDB
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Noah Slater
> Assignee: Jan Lehnardt
> Priority: Critical
> Attachments: issue-153.patch
>
>
> CouchDB is installed as root for most people, and hence without remembering
> to change the permissions on the log/data directories, errors are very
> common. The problems caused by incorrect permissions can be very confusing.
> We should re-add the checks for these that used to be in the init script, but
> place them in CouchDB core. We need to do this so that the multiple
> configuration settings will be taken account for.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
