You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Frank (JIRA)" <ji...@apache.org> on 2010/04/26 17:08:33 UTC

[jira] Updated: (COUCHDB-538) Erlang crashing when log file cannot be written

     [ https://issues.apache.org/jira/browse/COUCHDB-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frank updated COUCHDB-538:
--------------------------

    Attachment: COUCHDB-538.patch

Patch description: If there is an error with opening the log file, the logger gives a reasonable error message and stops afterwards. The supervisor tries to restart a few times, but finally gives up and crashes couchdb. 


> 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
>             Fix For: 0.12
>
>         Attachments: COUCHDB-538.patch
>
>
> 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.