[
https://issues.apache.org/jira/browse/COUCHDB-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141504#comment-13141504
]
Filipe Manana commented on COUCHDB-1326:
----------------------------------------
We do, check the function couch_httpd:error_info/2.
For this particular case, which happens on startup, the code is a bit repeated.
However when handling such an error for a request, we have common code.
Examples from COUCHDB-966
$ curl -H 'X-Couch-Persist: true' -X PUT
http://localhost:5984/_config/couchdb/delayed_commits -d '"false"'
{"error":"file_permission_error","reason":"/home/fdmanana/git/hub/couchdb/etc/couchdb/local_dev.ini"}
For a database file for which we don't have read permission:
$ curl http://localhost:5984/abc
{"error":"file_permission_error","reason":"/home/fdmanana/git/hub/couchdb/tmp/lib/abc.couch"}
Thanks for the report and patch :)
> scanty error message when writing to uri_file fails
> ---------------------------------------------------
>
> Key: COUCHDB-1326
> URL: https://issues.apache.org/jira/browse/COUCHDB-1326
> Project: CouchDB
> Issue Type: Bug
> Reporter: Rogutės Sparnuotos
> Priority: Minor
> Attachments:
> 0001-A-more-useful-error-when-writing-to-uri_file-fails.patch,
> 0001-A-more-useful-error-when-writing-to-uri_file-fails.patch,
> COUCHDB-1326-fdmanana.patch
>
>
> CouchDB crashes when it fails writing to uri_file (set from the [couchdb]
> section). The error message is too vague to understand what's going on:
> "{{badmatch,{error,enoent}}". At least the filename should be mentioned.
> P.S.
> I'd say it's all Erlang's fault, because file:write_file() doesn't report the
> file name on errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
