Description of problem: Version-Release number of selected component (if applicable): couchdb-3.0.0-1.fc31.x86_64 Steps to Reproduce and Actual results: ``` asedsami@localhost ~> couchdb -h 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 ``` ``` asedsami@localhost ~> sudo systemctl start couchdb.service Job for couchdb.service failed because the control process exited with error code. See "systemctl status couchdb.service" and "journalctl -xe" for details. ``` ``` asedsami@localhost ~> sudo journalctl -u couchdb.service -- Logs begin at Mon 2020-08-10 15:45:10 +04, end at Mon 2020-08-10 21:43:55 +04. -- Aug 10 17:19:19 localhost.localdomain systemd[1]: /usr/lib/systemd/system/couchdb.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/couchdb/couchdb.pid → /run/couchdb/couchdb.pid; please update th> Aug 10 17:19:19 localhost.localdomain systemd[1]: Starting CouchDB Server... Aug 10 17:19:21 localhost.localdomain couchdb[7787]: =WARNING REPORT==== 10-Aug-2020::17:19:20.983499 === Aug 10 17:19:21 localhost.localdomain couchdb[7787]: A call to erlang:system_flag(scheduler_bind_type, _) was Aug 10 17:19:21 localhost.localdomain couchdb[7787]: made. The scheduler_bind_type argument is deprecated and Aug 10 17:19:21 localhost.localdomain couchdb[7787]: scheduled for removal in Erlang/OTP 18. For more Aug 10 17:19:21 localhost.localdomain couchdb[7787]: information see the erlang:system_flag/2 documentation. Aug 10 17:19:21 localhost.localdomain couchdb[7787]: {"init terminating in do_boot",{{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{file,"src/couch.erl"},{line,43}]},{init,start_em,1,[]},{init,do_boot,3,[]}]}} Aug 10 17:19:21 localhost.localdomain couchdb[7787]: init terminating in do_boot ({{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{_},{_}]},{init,start_em,1,[]},{init,do_boot,3,[]}]}) Aug 10 17:19:21 localhost.localdomain couchdb[7787]: [1B blob data] Aug 10 17:19:21 localhost.localdomain couchdb[7787]: Crash dump is being written to: erl_crash.dump... Aug 10 17:19:21 localhost.localdomain systemd[1]: couchdb.service: Main process exited, code=exited, status=1/FAILURE Aug 10 17:19:21 localhost.localdomain systemd[1]: couchdb.service: Failed with result 'exit-code'. Aug 10 17:19:21 localhost.localdomain systemd[1]: Failed to start CouchDB Server. Aug 10 17:19:21 localhost.localdomain systemd[1]: couchdb.service: Scheduled restart job, restart counter is at 1. Aug 10 17:19:21 localhost.localdomain systemd[1]: Stopped CouchDB Server. Aug 10 17:19:21 localhost.localdomain systemd[1]: Starting CouchDB Server... Aug 10 17:19:21 localhost.localdomain couchdb[7817]: =WARNING REPORT==== 10-Aug-2020::17:19:21.559759 === Aug 10 17:19:21 localhost.localdomain couchdb[7817]: A call to erlang:system_flag(scheduler_bind_type, _) was Aug 10 17:19:21 localhost.localdomain couchdb[7817]: made. The scheduler_bind_type argument is deprecated and Aug 10 17:19:21 localhost.localdomain couchdb[7817]: scheduled for removal in Erlang/OTP 18. For more Aug 10 17:19:21 localhost.localdomain couchdb[7817]: information see the erlang:system_flag/2 documentation. Aug 10 17:19:21 localhost.localdomain couchdb[7817]: {"init terminating in do_boot",{{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{file,"src/couch.erl"},{line,43}]},{init,start_em,1,[]},{init,do_boot,3,[]}]}} Aug 10 17:19:21 localhost.localdomain couchdb[7817]: init terminating in do_boot ({{nocatch,{error,{app_would_not_start,sasl}}},[{couch,start,0,[{_},{_}]},{init,start_em,1,[]},{init,do_boot,3,[]}]}) Aug 10 17:19:21 localhost.localdomain couchdb[7817]: [1B blob data] Aug 10 17:19:21 localhost.localdomain couchdb[7817]: Crash dump is being written to: erl_crash.dump... ``` Expected results: couchdb running Additional info: I followed some blog posts guiding how to install couchdb, all of them said to install epel-release first which I couldn't install and I don't remember how did I install couchdb. a gentleman on [stackexchange](https://unix.stackexchange.com/questions/603808/cant-start-couchdb-due-to-deprecation-of-scheduler-bind-type-in-erlang-otp-18) advised me to open a bug report here. thanks in advance.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.