can't start couchdb service on CouchDB3.2.2

[qiaofeng1227]

I install CouchDB3.2.2 follow the official documentation on ubuntu 20.04.

root@iZj6c1hugdaichrjah6wekZ:/data/logs# systemctl status couchdb
● couchdb.service - Apache CouchDB
     Loaded: loaded (/lib/systemd/system/couchdb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2022-05-09 15:36:16 CST; 14min ago
    Process: 11501 ExecStart=/opt/couchdb/bin/couchdb (code=exited, status=1/FAILURE)
   Main PID: 11501 (code=exited, status=1/FAILURE)

May 09 15:36:15 iZj6c1hugdaichrjah6wekZ systemd[1]: Started Apache CouchDB.
May 09 15:36:16 iZj6c1hugdaichrjah6wekZ couchdb[11501]: {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{\"Failed to create cookie file '/opt/couchdb/.erl>
May 09 15:36:16 iZj6c1hugdaichrjah6wekZ couchdb[11501]: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,auth,{"Failed to create cookie file '/opt/c
May 09 15:36:16 iZj6c1hugdaichrjah6wekZ couchdb[11501]: 
May 09 15:36:16 iZj6c1hugdaichrjah6wekZ couchdb[11501]: Crash dump is being written to: erl_crash.dump...
May 09 15:36:16 iZj6c1hugdaichrjah6wekZ systemd[1]: couchdb.service: Main process exited, code=exited, status=1/FAILURE
May 09 15:36:16 iZj6c1hugdaichrjah6wekZ systemd[1]: couchdb.service: Failed with result 'exit-code'.

I haven't found a good solution for a while. Please help me see if there is this problem

[big-r81]

Hi,

can you show me the content of your vm.args file please?

[qiaofeng1227]

CouchDB3.2.2 is normal On CentOS7.9, I'm very sorry for taking so long to reply.
It have errors in utunbu20.04, this vm.args files:

root@iZj6c5z9rk0wefbur0clbeZ:~# cat /opt/couchdb/etc/vm.args
# Licensed under the Apache License, Version 2.0 (the "License"); you may not
# use this file except in compliance with the License. You may obtain a copy of
# the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations under
# the License.

# Each node in the system must have a unique name. These are specified through
# the Erlang -name flag, which takes the form:
#
#    -name nodename@<FQDN>
#
# or
#
#    -name nodename@<IP-ADDRESS>
#
# CouchDB recommends the following values for this flag:
#
# 1. If this is a single node, not in a cluster, use:
#    -name [email protected]
#
# 2. If DNS is configured for this host, use the FQDN, such as:
#    -name [email protected]
#
# 3. If DNS isn't configured for this host, use IP addresses only, such as:
#    -name [email protected]
#
# Do not rely on tricks with /etc/hosts or libresolv to handle anything
# other than the above 3 approaches correctly. They will not work reliably.
#
# Multiple CouchDBs running on the same machine can use couchdb1@, couchdb2@,
# etc.
-name [email protected]

# All nodes must share the same magic cookie for distributed Erlang to work.
# Uncomment the following line and append a securely generated random value.
-setcookie 

# Which interfaces should the node listen on?
-kernel inet_dist_use_interface {127,0,0,1}

# Tell kernel and SASL not to log anything
-kernel error_logger silent
-sasl sasl_error_logger false

# Use kernel poll functionality if supported by emulator
+K true

# Start a pool of asynchronous IO threads
+A 16

# Comment this line out to enable the interactive Erlang shell on startup
+Bd -noinput

# Force use of the smp scheduler, fixes #1296
-smp enable

# Set maximum SSL session lifetime to reap terminated replication readers
-ssl session_lifetime 300

## TLS Distribution
## Use TLS for connections between Erlang cluster members.
## http://erlang.org/doc/apps/ssl/ssl_distribution.html
##
## Generate Cert(PEM) File
## This is just an example command to generate a certfile (PEM).
## This is not an endorsement of specific expiration limits, key sizes, or algorithms.
##    $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem
##    $ cat key.pem cert.pem > dev/erlserver.pem && rm key.pem cert.pem
##
## Generate a Config File (couch_ssl_dist.conf)
##    [{server,
##      [{certfile, "</path/to/erlserver.pem>"},
##       {secure_renegotiate, true}]},
##     {client,
##      [{secure_renegotiate, true}]}].
##
## CouchDB recommends the following values for no_tls flag:
## 1. Use TCP only, set to true, such as:
##      -couch_dist no_tls true
## 2. Use TLS only, set to false, such as:
##      -couch_dist no_tls false
## 3. Specify which node to use TCP, such as:
##      -couch_dist no_tls \"*@127.0.0.1\"
##
## To ensure search works, make sure to set 'no_tls' option for the clouseau node.
## By default that would be "[email protected]".
## Don't forget to override the paths to point to your certificate(s) and key(s)!
##
#-proto_dist couch
#-couch_dist no_tls \"[email protected]\"

[big-r81]

You didn't set your cookie

# All nodes must share the same magic cookie for distributed Erlang to work.
# Uncomment the following line and append a securely generated random value.
-setcookie 

Please generate a long string with openssl rand -hex 32 or so and add it to your config.

Example (don't use):

# All nodes must share the same magic cookie for distributed Erlang to work.
# Uncomment the following line and append a securely generated random value.
-setcookie 75b5ff56cdc716799f1ff9cbfba96ebb6f524043f88d5809ef577d853039f9ff