Can't start CouchDB service

ProtoTech · 2017-06-07 01:38:58

I just installed CouchDB for the first time and I cannot seem to successfully start the CouchDB service. If I execute `sudo systemctl start couchdb.service` and then execute `sudo systemctl status couchdb.service` I get the output of:

● couchdb.service - CouchDB Server
   Loaded: loaded (/usr/lib/systemd/system/couchdb.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2017-06-07 01:30:13 UTC; 1min 2s ago
  Process: 14273 ExecStart=/usr/lib/couchdb/bin/couchdb (code=exited, status=1/FAILURE)
 Main PID: 14273 (code=exited, status=1/FAILURE)

Jun 07 01:30:12 devin-arch couchdb[14273]: 2017-06-07 01:30:12 inet_parse:~p:~p: erroneous line, SKIPPED~n
Jun 07 01:30:12 devin-arch couchdb[14273]:         "/etc/resolv.conf"
Jun 07 01:30:12 devin-arch couchdb[14273]:         3
Jun 07 01:30:12 devin-arch couchdb[14273]: [os_mon] memory supervisor port (memsup): Erlang has closed
Jun 07 01:30:12 devin-arch couchdb[14273]: [os_mon] cpu supervisor port (cpu_sup): Erlang has closed
Jun 07 01:30:13 devin-arch couchdb[14273]: {"Kernel pid terminated",application_controller,"{application_start_failure,couch_epi,{{shutdown,{failed_to_start_child,\"couch_epi|chttpd_auth|keeper\",{undef,[{crypto,
Jun 07 01:30:13 devin-arch couchdb[14273]: Kernel pid terminated (application_controller) ({application_start_failure,couch_epi,{{shutdown,{failed_to_start_child,"couch_epi|chttpd_auth|keeper",{undef,[{crypto,md5
Jun 07 01:30:13 devin-arch systemd[1]: couchdb.service: Main process exited, code=exited, status=1/FAILURE
Jun 07 01:30:13 devin-arch systemd[1]: couchdb.service: Unit entered failed state.
Jun 07 01:30:13 devin-arch systemd[1]: couchdb.service: Failed with result 'exit-code'.

Last edited by ProtoTech (2017-06-07 02:24:13)

jasonwryan · 2017-06-07 01:41:09

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

Moving to NC...

ProtoTech · 2017-06-07 02:27:34

I updated the post to include code tags.

Another note is that my resolve.conf was generated with resolvconf. Everything looks in order and I tried to regenerate my resolv.conf with the same results. If I can provide any more useful information, let me know.

jasonwryan · 2017-06-07 02:33:03

Please paste your couch config and your resolv.conf

ProtoTech · 2017-06-07 12:13:53

Here you go. I left the CouchDB configuration the default as the wiki didn't notate that I had to modify anything to get basic functionality.

My CouchDB local.ini:

; CouchDB Configuration Settings

; Custom settings should be made in this file. They will override settings
; in default.ini, but unlike changes made to default.ini, this file won't be
; overwritten on server upgrade.

[couchdb]
;max_document_size = 4294967296 ; bytes
;os_process_timeout = 5000

[couch_peruser]
; If enabled, couch_peruser ensures that a private per-user database
; exists for each document in _users. These databases are writable only
; by the corresponding user. Databases are in the following form:
; userdb-{hex encoded username}
;enable = true
; If set to true and a user is deleted, the respective database gets
; deleted as well.
;delete_dbs = true

[chttpd]
;port = 5984
;bind_address = 127.0.0.1
; Options for the MochiWeb HTTP server.
;server_options = [{backlog, 128}, {acceptor_pool_size, 16}]
; For more socket options, consult Erlang's module 'inet' man page.
;socket_options = [{recbuf, 262144}, {sndbuf, 262144}, {nodelay, true}]

[httpd]
; NOTE that this only configures the "backend" node-local port, not the
; "frontend" clustered port. You probably don't want to change anything in
; this section.
; Uncomment next line to trigger basic-auth popup on unauthorized requests.
;WWW-Authenticate = Basic realm="administrator"

; Uncomment next line to set the configuration modification whitelist. Only
; whitelisted values may be changed via the /_config URLs. To allow the admin
; to change this value over HTTP, remember to include {httpd,config_whitelist}
; itself. Excluding it from the list would require editing this file to update
; the whitelist.
;config_whitelist = [{httpd,config_whitelist}, {log,level}, {etc,etc}]

[query_servers]
;nodejs = /usr/local/bin/couchjs-node /path/to/couchdb/share/server/main.js


[httpd_global_handlers]
;_google = {couch_httpd_proxy, handle_proxy_req, <<"http://www.google.com">>}

[couch_httpd_auth]
; If you set this to true, you should also uncomment the WWW-Authenticate line
; above. If you don't configure a WWW-Authenticate header, CouchDB will send
; Basic realm="server" in order to prevent you getting logged out.
; require_valid_user = false

[os_daemons]
; For any commands listed here, CouchDB will attempt to ensure that
; the process remains alive. Daemons should monitor their environment
; to know when to exit. This can most easily be accomplished by exiting
; when stdin is closed.
;foo = /path/to/command -with args

[daemons]
; enable SSL support by uncommenting the following line and supply the PEM's below.
; the default ssl port CouchDB listens on is 6984
; httpsd = {couch_httpd, start_link, [https]}

[ssl]
;cert_file = /full/path/to/server_cert.pem
;key_file = /full/path/to/server_key.pem
;password = somepassword
; set to true to validate peer certificates
;verify_ssl_certificates = false
; Set to true to fail if the client does not send a certificate. Only used if verify_ssl_certificates is true.
;fail_if_no_peer_cert = false
; Path to file containing PEM encoded CA certificates (trusted
; certificates used for verifying a peer certificate). May be omitted if
; you do not want to verify the peer.
;cacert_file = /full/path/to/cacertf
; The verification fun (optional) if not specified, the default
; verification fun will be used.
;verify_fun = {Module, VerifyFun}
; maximum peer certificate depth
;ssl_certificate_max_depth = 1
;
; Reject renegotiations that do not live up to RFC 5746.
;secure_renegotiate = true
; The cipher suites that should be supported.
; Can be specified in erlang format "{ecdhe_ecdsa,aes_128_cbc,sha256}"
; or in OpenSSL format "ECDHE-ECDSA-AES128-SHA256".
;ciphers = ["ECDHE-ECDSA-AES128-SHA256", "ECDHE-ECDSA-AES128-SHA"]
; The SSL/TLS versions to support
;tls_versions = [tlsv1, 'tlsv1.1', 'tlsv1.2']

; To enable Virtual Hosts in CouchDB, add a vhost = path directive. All requests to
; the Virual Host will be redirected to the path. In the example below all requests
; to http://example.com/ are redirected to /database.
; If you run CouchDB on a specific port, include the port number in the vhost:
; example.com:5984 = /database
[vhosts]
;example.com = /database/

[update_notification]
;unique notifier name=/full/path/to/exe -with "cmd line arg"

; To create an admin account uncomment the '[admins]' section below and add a
; line in the format 'username = password'. When you next start CouchDB, it
; will change the password to a hash (so that your passwords don't linger
; around in plain-text files). You can add more admin accounts with more
; 'username = password' lines. Don't forget to restart CouchDB after
; changing this.
[admins]
;admin = mysecretpassword

and my resolv.conf:

# Generated by resolvconf
nameserver 192.168.1.1
nameserver fe80::f6f5:e8ff:fe6e:5e4b%eno1
nameserver 2605:a601:91c:3600::1

jasonwryan wrote:

Please paste your couch config and your resolv.conf

Any ideas?

Last edited by ProtoTech (2017-06-08 20:43:11)

ProtoTech · 2017-06-10 04:28:02

Bump

I was able to execute the couchdb binary manually and got this output.

2017-06-09 23:34:56 inet_parse:~p:~p: erroneous line, SKIPPED~n
	"/etc/resolv.conf"
	3
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
{"Kernel pid terminated",application_controller,"{application_start_failure,couch_epi,{{shutdown,{failed_to_start_child,\"couch_epi|chttpd_auth|keeper\",{undef,[{crypto,md5,[<<131,106>>],[]},{couch_epi_util,hash,1,[{file,\"src/couch_epi_util.erl\"},{line,25}]},{couch_epi_functions,data,1,[{file,\"src/couch_epi_functions.erl\"},{line,33}]},{couch_epi_module_keeper,do_reload_if_updated,1,[{file,\"src/couch_epi_module_keeper.erl\"},{line,116}]},{gen_server,init_it,6,[{file,\"gen_server.erl\"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,247}]}]}}},{couch_epi_app,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,couch_epi,{{shutdown,{failed_to_start_child,"couch_epi|chttpd_auth|keeper",{undef,[{crypto,md5,[<<131,106>>],[]},{couch_epi_u

Crash dump is being written to: erl_crash.dump...[

I'm not sure where this erl_crash.dump file is located, but if I can find it I will post its contents.

Last edited by ProtoTech (2017-06-10 04:36:54)

jasonwryan · 2017-06-10 04:40:13

Don't do that: https://wiki.archlinux.org/index.php/Co … ct#Bumping

I don't use couchdb, so this is conjecture, but based on the error it is choking on your IPv6 entry in resolv conf. According to the documentation, you have to set a specific bind address http://docs.couchdb.org/en/2.0.0/config/http.html

Arch Linux

#1 2017-06-07 01:38:58

Can't start CouchDB service

#2 2017-06-07 01:41:09

Re: Can't start CouchDB service

#3 2017-06-07 02:27:34

Re: Can't start CouchDB service

#4 2017-06-07 02:33:03

Re: Can't start CouchDB service

#5 2017-06-07 12:13:53

Re: Can't start CouchDB service

#6 2017-06-10 04:28:02

Re: Can't start CouchDB service

#7 2017-06-10 04:40:13

Re: Can't start CouchDB service

Board footer