Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Fri, 21 Jun 2013 09:38:20 +0000 (UTC)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12654106.1371802584032.154228.1371807500379@arcas>
In-Reply-To: <JIRA.12654106.1371802584032@arcas>
References: <JIRA.12654106.1371802584032@arcas>
Subject: [jira] [Commented] (COUCHDB-1833) Couchdb not starting on erlang
 R16B01
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COUCHDB-1833?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13=
690152#comment-13690152 ]=20

Robert Newson commented on COUCHDB-1833:
----------------------------------------

hm, we should only need to depend on "crypto", but ok. With that solved, it=
 still won't work because of the parameterized module stuff, right?
               =20
> Couchdb not starting on erlang R16B01
> -------------------------------------
>
>                 Key: COUCHDB-1833
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1833
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>            Reporter: Dawid Ja=C5=84czak
>
> CouchDB version: 1.2.2
> Erlang version: R16B01
> system: Linux work 3.9.6-1-ARCH #1 SMP PREEMPT Fri Jun 14 08:12:55 CEST 2=
013 x86_64 GNU/Linux
> Hi!
> My package manager decided to upgrade Erlang yesterday and CouchDB won't =
start after reboot. Here is the message I get when running /usr/bin/couchdb=
 manually:
> {"init terminating in do_boot",{{badmatch,{error,{{app_would_not_start,ss=
l},{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local=
.ini"]]}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,=
1,[]},{init,start_em,1,[]}]}}
> Crash dump was written to: erl_crash.dump
> init terminating in do_boot ()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira