couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rogutės Sparnuotos (Commented) (JIRA) <>
Subject [jira] [Commented] (COUCHDB-1326) scanty error message when writing to uri_file fails
Date Tue, 01 Nov 2011 19:41:33 GMT


Rogutės Sparnuotos commented on COUCHDB-1326:

1) Sorry about indentation - not sure how I didn't notice.
2) Ok.
3) The message is much easier to notice with the logger.
4) Error messages in CouchDB are cryptic overall. Nice to see that you care.

Fun facts:
1. The first time I installed CouchDB I saw an eaccess error and couldn't understand it.
2. This patch came after I accidentally pointed uri_file to a directory. I noticed the 'eisdir'
error but it was hard to find out where it was coming from.

I think that it would be best (more user friendly) if such startup errors were handled in
a cleaner fashion. Would it be possible to throw({known_startup_error}) and catch it before
Erlang decides to crash and write a crash dump?

It was nice of you to ask a CouchDB newbie for feedback. You should commit your 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