couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-538) Erlang crashing when log file cannot be written
Date Mon, 26 Apr 2010 15:08:33 GMT

     [ 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.


Mime
View raw message