I installed CouchDB from the Fedora repository, launched it using “systemctl enable couchdb” and “systemctl start couchdb” and it fails to start. “systemctl status couchdb” gives the following unhelpful message:
× couchdb.service - CouchDB Server
Loaded: loaded (/usr/lib/systemd/system/couchdb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2021-11-21 18:19:51 PST; 12s ago
Process: 419931 ExecStart=/usr/libexec/couchdb +Bd -noinput -sasl errlog_type error +K true +A 4 -couch_ini /etc/couchdb/default.ini /etc/couchdb/default.d/ /etc/couchdb/local.d/ /etc/couch>
Main PID: 419931 (code=exited, status=1/FAILURE)
CPU: 348ms
Nov 21 18:19:51 brutus-riesenhaus-local systemd[1]: couchdb.service: Scheduled restart job, restart counter is at 5.
Nov 21 18:19:51 brutus-riesenhaus-local systemd[1]: Stopped CouchDB Server.
Nov 21 18:19:51 brutus-riesenhaus-local systemd[1]: couchdb.service: Start request repeated too quickly.
Nov 21 18:19:51 brutus-riesenhaus-local systemd[1]: couchdb.service: Failed with result 'exit-code'.
Nov 21 18:19:51 brutus-riesenhaus-local systemd[1]: Failed to start CouchDB Server.
“journalctl -xeu couchdb.service” gives messages like the following:
The unit couchdb.service has entered the 'failed' state with result 'exit-code'.
Nov 21 18:19:51 brutus-riesenhaus-local systemd[1]: Failed to start CouchDB Server.
░░ Subject: A start job for unit couchdb.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit couchdb.service has finished with a failure.
░░
░░ The job identifier is 372889 and the job result is failed.
l
…plus the possibly more helpful…
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: =WARNING REPORT==== 21-Nov-2021::18:19:50.758701 ===
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: A call to erlang:system_flag(scheduler_bind_type, _) was
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: made. The scheduler_bind_type argument is deprecated and
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: scheduled for removal in Erlang/OTP 18. For more
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: information see the erlang:system_flag/2 documentation.
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: {"init terminating in do_boot",{{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{file,"src/couch.erl"},{line,42}]},{init,s>
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: init terminating in do_boot ({{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{_},{_}]},{init,start_em,1,[]},{init,do_boot>
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]:
Nov 21 18:19:50 brutus-riesenhaus-local couchdb[419893]: Crash dump is being written to: erl_crash.dump...
Nov 21 18:19:50 brutus-riesenhaus-local systemd[1]: couchdb.service: Main process exited, code=exited, status=1/FAILURE
I am running couchdb-3.1.1-4.fc35.x86_64. The couchdb account exists as does the home directory, /var/lib/couchdb. The manpage suggests creating the latter by copying a directory that doesn’t appear to be part of the package into place, so I copied /etc/skel instead.
The troubleshooting procedures suggested in the manpage indicate that crypto:md5_init(). is unavailable, but I have no idea which package provides that.
How shall I proceed?