couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Eisenmann (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-538) Erlang crashing when log file cannot be written
Date Mon, 19 Oct 2009 16:53:59 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767378#action_12767378
] 

Simon Eisenmann commented on COUCHDB-538:
-----------------------------------------

Thats true yes. But still if for whatever reason they do not exist any more or if the paths
are changed in the configuration file, the user will never guess what the problem is, as there
is no helping error message.

I am not saything that it should not crash or something. Just catch the error and bail with
a meaningful exception.

> Erlang crashing when log file cannot be written
> -----------------------------------------------
>
>                 Key: COUCHDB-538
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-538
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: 0.10
>         Environment: Linux Ubuntu 32bit and 64bit
>            Reporter: Simon Eisenmann
>            Priority: Minor
>
> When couchdb cannot write to its log file erlang just crashes without any hint what is
going wrong. This happens for instance if the log file directory path does not exists.
> In some older releases (0.9) it seemed to have created the missing directories automatically
(if permissions are ok). 0.10 does not even try to create the directories. The log path needs
to exist.
> At least a proper error message should be added to make clear that there is a problem
writing the log file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message