Bug 1914990
| Summary: | CouchDB 3.1.1 fails to start with init terminating in do_boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | benjamin.schaefer |
| Component: | couchdb | Assignee: | Orphan Owner <extras-orphan> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | erik, lemenkov |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-30 19:16:24 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: | |||
I can confirm this.
When I start couchdb I get
$ couchdb
cat: /usr/bin/../releases/start_erl.data: No such file or directory
/usr/bin/couchdb: line 47: /usr/bin/../erts-/bin/erlexec: No such file or directory
Is there a workaround?
There is also a question about this here: https://unix.stackexchange.com/questions/603808/cant-start-couchdb-due-to-deprecation-of-scheduler-bind-type-in-erlang-otp-18
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: CouchDB fails to start with message "init terminating in do_boot" Version-Release number of selected component (if applicable): 3.1.1 How reproducible: Steps to Reproduce: 1. Install couchdb (dnf install couchdb) 2. Start couchdb (sudo systemctl start couchdb.service) Actual results: CouchDB fails to start Expected results: CouchDB start normally Additional info: Jan 11 18:05:44 hostname systemd[1]: Starting CouchDB Server... Jan 11 18:05:44 hostname couchdb[21677]: {"init terminating in do_boot",{{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{file,"src/couch.erl"},{line,42}]},{init,start_em,1,[]},{init,do_boot,3,> Jan 11 18:05:44 hostname couchdb[21677]: init terminating in do_boot ({{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{_},{_}]},{init,start_em,1,[]},{init,do_boot,3,[]}]}) Jan 11 18:05:44 hostname couchdb[21677]: Jan 11 18:05:44 hostname couchdb[21677]: Crash dump is being written to: erl_crash.dump... Jan 11 18:05:44 hostname systemd[1]: couchdb.service: Main process exited, code=exited, status=1/FAILURE Jan 11 18:05:44 hostname systemd[1]: couchdb.service: Failed with result 'exit-code'. Jan 11 18:05:44 hostname systemd[1]: Failed to start CouchDB Server. Jan 11 18:05:44 hostname systemd[1]: couchdb.service: Scheduled restart job, restart counter is at 1. Jan 11 18:05:44 hostname systemd[1]: Stopped CouchDB Server.