Common errors encountered include issues when starting Couchbase server for the first time.
This page will attempt to describe and resolve some common errors that are encountered when using Couchbase. It will be a living document as new problems and resolutions are discovered.
Problems Starting Couchbase Server for the first time
If you are having problems starting Couchbase Server on Linux for the first time, there are two very common causes of this that are actually quite related. When the /etc/init.d/couchbase-server script runs, it tries to set the file descriptor limit and core file size limit:
> ulimit -n 10240 ulimit -c unlimited
Depending on the defaults of your system, this may or may not be allowed. If Couchbase Server is failing to start, you can look through the logs and pick out one or both of these messages:
ns_log: logging ns_port_server:0:Port server memcached on node 'email@example.com' exited with status 71. » Restarting. Messages: failed to set rlimit for open files. » Try running as root or requesting smaller maxconns value.
Alternatively, you may additionally see or optionally see:
ns_port_server:0:info:message - Port server memcached on node 'firstname.lastname@example.org' exited with status 71. » Restarting. Messages: failed to ensure corefile creation
The resolution to these is to edit the /etc/security/limits.conf file and add these entries:
couchbase hard nofile 10240 couchbase hard core unlimited