couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1326) scanty error message when writing to uri_file fails
Date Tue, 01 Nov 2011 19:53:32 GMT


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"' 

For a database file for which we don't have read permission: 

$ curl http://localhost:5984/abc 

Thanks for the report and patch :)
> scanty error message when writing to uri_file fails
> ---------------------------------------------------
>                 Key: COUCHDB-1326
>                 URL:
>             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 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:!default.jspa
For more information on JIRA, see:


View raw message