Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD2087EA6 for ; Tue, 1 Nov 2011 19:41:56 +0000 (UTC) Received: (qmail 78508 invoked by uid 500); 1 Nov 2011 19:41:54 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 78453 invoked by uid 500); 1 Nov 2011 19:41:54 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 78400 invoked by uid 99); 1 Nov 2011 19:41:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 19:41:54 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 19:41:53 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 30FC732C523 for ; Tue, 1 Nov 2011 19:41:33 +0000 (UTC) Date: Tue, 1 Nov 2011 19:41:33 +0000 (UTC) From: =?utf-8?Q?Rogut=C4=97s_Sparnuotos_=28Commented=29_=28JIRA=29?= To: dev@couchdb.apache.org Message-ID: <2050937061.47102.1320176493202.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1192190801.39184.1320025472237.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (COUCHDB-1326) scanty error message when writing to uri_file fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1326?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13= 141494#comment-13141494 ]=20 Rogut=C4=97s 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 u= nderstand 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 w= ere handled in a cleaner fashion. Would it be possible to throw({known_star= tup_error}) and catch it before Erlang decides to crash and write a crash d= ump? It was nice of you to ask a CouchDB newbie for feedback. You should commit = your patch :) =20 > 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=C4=97s Sparnuotos > Priority: Minor > Attachments: 0001-A-more-useful-error-when-writing-to-uri_file-fa= ils.patch, 0001-A-more-useful-error-when-writing-to-uri_file-fails.patch, C= OUCHDB-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 administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira