Eu tentei iniciar o couchdb:
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.
que não conseguiu iniciar.
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
Tentei então obter o log completo:
asedsami@localhost ~> sudo journalctl -u couchdb.service
Aug 10 17:19:22 localhost.localdomain systemd[1]: couchdb.service: Main process exited, code=exited, status=1/FAILURE
Aug 10 17:19:22 localhost.localdomain systemd[1]: couchdb.service: Failed with result 'exit-code'.
Aug 10 17:19:22 localhost.localdomain systemd[1]: Failed to start CouchDB Server.
Aug 10 17:19:22 localhost.localdomain systemd[1]: couchdb.service: Scheduled restart job, restart counter is at 4.
Aug 10 17:19:22 localhost.localdomain systemd[1]: Stopped CouchDB Server.
Aug 10 17:19:22 localhost.localdomain systemd[1]: Starting CouchDB Server...
Aug 10 17:19:23 localhost.localdomain couchdb[7903]: =WARNING REPORT==== 10 Aug-2020::17:19:23.063486 ===
Aug 10 17:19:23 localhost.localdomain couchdb[7903]: A call to erlang:system_flag(scheduler_bind_type, _) was
Aug 10 17:19:23 localhost.localdomain couchdb[7903]: made. The scheduler_bind_type argument is deprecated and
Aug 10 17:19:23 localhost.localdomain couchdb[7903]: scheduled for removal in Erlang/OTP 18. For more
Aug 10 17:19:23 localhost.localdomain couchdb[7903]: information see the erlang:system_flag/2 documentation.
Aug 10 17:19:23 localhost.localdomain couchdb[7903]: {"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:23 localhost.localdomain couchdb[7903]: 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:23 localhost.localdomain couchdb[7903]: [1B blob data]
Aug 10 17:19:23 localhost.localdomain couchdb[7903]: Crash dump is being written to: erl_crash.dump...
Aug 10 17:19:23 localhost.localdomain systemd[1]: couchdb.service: Main process exited, code=exited, status=1/FAILURE
Aug 10 17:19:23 localhost.localdomain systemd[1]: couchdb.service: Failed with result 'exit-code'.
Aug 10 17:19:23 localhost.localdomain systemd[1]: Failed to start CouchDB Server.
Aug 10 17:19:23 localhost.localdomain systemd[1]: couchdb.service: Scheduled restart job, restart counter is at 5.
Aug 10 17:19:23 localhost.localdomain systemd[1]: Stopped CouchDB Server.
Aug 10 17:19:23 localhost.localdomain systemd[1]: couchdb.service: Start request repeated too quickly.
Aug 10 17:19:23 localhost.localdomain systemd[1]: couchdb.service: Failed with result 'exit-code'.
Aug 10 17:19:23 localhost.localdomain systemd[1]: Failed to start CouchDB Server.
portanto, há um problema de scheduler_bind_typedescontinuação em Erlang/OTP 18 que não sei como consertar e agradeço qualquer ajuda que você possa fornecer.
Responder1
Você provavelmente obteria a melhor resposta preenchendo umrelatório de erroao mantenedor do pacote Fedora. O mantenedor, Peter Lemenkov, também mantém os pacotes erlang no Fedora e deve ser capaz de fornecer informações.