Bug 965637

Summary: CouchDB fails to start
Product: [Fedora] Fedora Reporter: Eetu Huisman <eh>
Component: couchdbAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: lemenkov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: couchdb-1.2.2-2.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-09 03:30:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eetu Huisman 2013-05-21 13:01:33 UTC
Description of problem:

After installing CouchDB on Fedora 19, starting it with systemctl and by running the executable directly fails.

Version-Release number of selected component (if applicable):

1.2.2-1.fc19.x86_64

How reproducible:

Every time.

Steps to Reproduce:
1. Install couchdb
2. Enable and run couchdb as root (systemctl start couchdb.service)
3. See the status as root (systemctl status couchdb.service)

Actual results:

Output with irrelevant stuff removed:

couchdb.service - CouchDB Server
   Loaded: loaded (/usr/lib/systemd/system/couchdb.service; disabled)
   Active: failed (Result: start-limit) since ti 2013-05-21 15:45:00 EEST; 4s ago
  Process: 27184 ExecStart=/usr/bin/erl +Bd -noinput -sasl errlog_type error +K true +A 4 -couch_ini /etc/couchdb/default.ini /etc/couchdb/local.ini -s couch -pidfile /var/run/couchdb/couchdb.pid -heart (code=exited, status=1/FAILURE)

systemd[1]: couchdb.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Unit couchdb.service entered failed state.
systemd[1]: couchdb.service holdoff time over, scheduling restart.
systemd[1]: Stopping CouchDB Server...
systemd[1]: Starting CouchDB Server...
systemd[1]: couchdb.service start request repeated too quickly, refusing to start.
systemd[1]: Failed to start CouchDB Server.
systemd[1]: Unit couchdb.service entered failed state.

Expected results:

A success message.

Additional info:

Running the executable directly gives the following error message:

{"init terminating in do_boot",{{badmatch,{error,{{app_would_not_start,mochiweb},{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,[]}]}}
init terminating in do_boot ()

I was able to get CouchDB running by first manually starting mochiweb from the Erlang command line (after first starting all of its dependencies), so the issue might be related to the erlang-mochiweb package rather than couchdb itself.

Comment 1 Fedora Update System 2013-05-31 13:36:23 UTC
couchdb-1.2.2-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/couchdb-1.2.2-2.fc19

Comment 2 Peter Lemenkov 2013-05-31 13:39:28 UTC
The issue is confirmed fixed (hopefully w/o adding a new ones). Sorry for this mess - I should have test all Erlang applications before upgrading to R16B.

Could you please test the build mentioned in the above comment?

Comment 3 Fedora Update System 2013-05-31 18:12:11 UTC
Package couchdb-1.2.2-2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing couchdb-1.2.2-2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9763/couchdb-1.2.2-2.fc19
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-06-09 03:30:12 UTC
couchdb-1.2.2-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.