[
https://issues.apache.org/jira/browse/COUCHDB-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690254#comment-13690254
]
Dave Cottlehuber commented on COUCHDB-1833:
-------------------------------------------
I tracked it down, *ssl* depends on asn1 via public_key. As we're not doing OTP
releases, this needs to be managed in couch_app.erl. I'll put this into master,
and the various COUCHDB-1696 branches I have.
diff --git i/src/couchdb/couch_app.erl w/src/couchdb/couch_app.erl
index 24b2f3a..9644877 100644
--- i/src/couchdb/couch_app.erl
+++ w/src/couchdb/couch_app.erl
@@ -20,7 +20,7 @@
start(_Type, DefaultIniFiles) ->
IniFiles = get_ini_files(DefaultIniFiles),
- case start_apps([crypto, public_key, sasl, inets, oauth, ssl, ibrowse,
syntax_tools, compiler, xmerl, mochiweb, os_mon]) of
+ case start_apps([crypto, asn1, public_key, sasl, inets, oauth, ssl,
ibrowse, syntax_tools, compiler, xmerl, mochiweb, os_mon]) of
ok ->
couch_server_sup:start_link(IniFiles);
{error, Reason} ->
> 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ńczak
>
> 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 2013
> 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,ssl},{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 administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
