cbcollect_info
The cbcollect_info tool provides detailed statistics for a specific node.
Syntax
The basic syntax is:
cbcollect_info [options] [output-file]
where output-file is the name of the .zip file containing the diagnostic information.
Description
The cbcollect_info command gathers statistics from an individual node in the cluster.
To collect diagnostic information for an entire cluster, run the command for every node that exists in that cluster. If you are experiencing problems with multiple nodes in a cluster, you may need to run it on all nodes in a cluster.
A root account is required to run this command and collect all the server information. There are internal server files and directories that this tool accesses that require root privileges.
To use this command, remotely connect to the machine which contains the Couchbase Server then issue the command with appropriate options. This command is typically run under the direction of technical support at Couchbase and generates a large .zip file. This archive contains files which contain performance statistics and server logs.
cbcollect_info is one of the most important diagnostic tools.
Run cbcollect_info on all nodes in the cluster, and upload all of the resulting files to Couchbase technical support .
|
This tool is at the following locations:
| Operating System | Location |
|---|---|
Linux |
/opt/couchbase/bin/cbcollect_info |
Windows |
C:\Program Files\Couchbase\Server\bin\cbcollect_info |
Mac OS X |
/Applications/Couchbase Server.app/Contents/Resources/couchbase-core/bin/cbcollect_info |
The tool creates the following log files in the output archive:
| File | Log Contents |
|---|---|
|
Contains system-level information, primarily the result of shell commands. Generated at collection-time. |
|
Contains the design documents for each bucket in json format, taken from the view file on disk. |
|
A diagnostic summary of the cluster manager, obtained by downloading |
|
A dump of all ini configuration files. |
|
Contains information relating to the core memcached component, including DCP stream requests and slow operations. |
|
Troubleshooting log for the babysitter process which is responsible for spawning all Couchbase Server processes and respawning them where necessary. |
|
Troubleshooting log for the couchdb subsystem which underlies map-reduce and spatial views |
|
Debug-level troubleshooting for the cluster management component. |
|
Error-level troubleshooting log for the cluster management component. |
|
Troubleshooting logs for the full-text search service. |
|
Troubleshooting log for the cross datacenter replication (XDCR) component used in Couchbase Server versions after 4.0. |
|
The admin access log records server requests (including administrator logins) to the REST API or Couchbase Server web console. It is output in common log format and contains several important fields such as remote client IP, timestamp, GET/POST request and resource requested, HTTP status code, and so on. |
|
The admin access log records internal server requests (including administrator logins) to the REST API or Couchbase Server web console. It is output in common log format and contains several important fields such as remote client IP, timestamp, GET/POST request and resource requested, HTTP status code, and so on. |
|
Troubleshooting log for the indexing and storage subsystem. |
|
Info-level troubleshooting log for the cluster management component. |
|
JavaScript and other view-processing errors are reported in this file. |
|
Troubleshooting log for the metakv store, a cluster-wide metadata store. |
|
Contains information related to starting up the CouchDB subsystem. |
|
Troubleshooting log for the projector process which is responsible for sending appropriate mutations from Data nodes to Index nodes. |
|
Contains progress and crash reports for the Erlang processes. Due to the nature of Erlang, processes crash and restart upon an error. |
|
Troubleshooting log for the ssl proxy spawned by the cluster manager. |
|
Contains periodic statistic dumps from the cluster management component. |
|
Troubleshooting log for the view engine, predominantly focussing on the changing of partition states. |
|
Troubleshooting log for the cross datacenter replication (XDCR) component used in Couchbase Server versions prior to 4.0. |
|
Error-level troubleshooting log for the cross datacenter replication (XDCR) component used in Couchbase Server versions prior to 4.0. |
|
Trace-level troubleshooting log for the cross datacenter replication (XDCR) component used in Couchbase Server versions prior to 4.0. Unless trace-level logging is explicitly turned on this log is empty. |
|
Goroutine dump captured for the projector process. A goroutine dump is the equivalent of a full thread dump in other languages and can give valuable insight into what a process is doing at that time. |
|
Contains output from various cbstats commands. Generated at collection-time. |
|
Archive of various system-level logs. |
Options
The following are the command options:
| Parameter | Description |
|---|---|
|
Shows help information. |
|
Root directory.
Default to |
|
Increases verbosity level.
If specified, debugging information for |
|
Gathers only product-related information. |
|
Dumps a list of commands that |
|
Skips collecting breakpad crash dumps if set to |
|
Runs only those tasks that match the specified regexp. (This flag is provided for debugging purposes.) |
|
Specifies the tmp directory that is used during data-processing.
This setting overrides any existing setting of the |
|
The server |
|
Collects on a per node basis, diagnostics on just this node. The default is all reachable nodes. |
|
Fully-qualified domain name of the host you want the logs uploaded to.
The protocol prefix of the domain name, |
|
Customer name. This value is a string with a maximum length of 50 characters that contains only the following characters: [A-Za-z0-9_.-]. If any other characters are included in the string, the request is rejected. |
|
Couchbase support ticket number.
This value is a string with a maximum length of 7 character that contains only digits 0-9.
The ticket number is optional and is used only in conjunction with the |
Sharing files with Couchbase support
Run the command below, replacing FILE-NAME and COMPANY-NAME, to upload a file to our cloud storage on Amazon AWS.
Make sure to include the last slash ("/") character after the company name.
curl --upload-file <FILE-NAME> https://s3.amazonaws.com/customers.couchbase.com/<COMPANY-NAME>/
Examples
To create a diagnostics .zip file, log onto the node and run the cbcollect_info tool.
On Linux, run as root or use sudo:
sudo /opt/couchbase/bin/cbcollect_info <node_name>.zip
On Windows, run as Administrator:
C:\Program Files\Couchbase\Server\bin\cbcollect_info <node_name>.zip
Response
The following example response shows partial output when running the cbcollect_info command.
uname (uname -a) - OK time and TZ (date; date -u) - OK raw /etc/sysconfig/clock (cat /etc/sysconfig/clock) - OK raw /etc/timezone (cat /etc/timezone) - Exit code 1 System Hardware (lshw -json || lshw) - Exit code 127 ... adding: /tmp/tmpMYbSyD/couchbase.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/couchbase.log adding: /tmp/tmpMYbSyD/ns_server.xdcr.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.xdcr.log adding: /tmp/tmpMYbSyD/ns_server.couchdb.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.couchdb.log adding: /tmp/tmpMYbSyD/stats.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/stats.log adding: /tmp/tmpMYbSyD/ini.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ini.log adding: /tmp/tmpMYbSyD/ns_server.error.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.error.log adding: /tmp/tmpMYbSyD/ns_server.ssl_proxy.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.ssl_proxy.log adding: /tmp/tmpMYbSyD/ns_server.views.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.views.log adding: /tmp/tmpMYbSyD/ns_server.info.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.info.log adding: /tmp/tmpMYbSyD/ns_server.xdcr_errors.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.xdcr_errors.log adding: /tmp/tmpMYbSyD/ns_server.mapreduce_errors.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.mapreduce_errors.log adding: /tmp/tmpMYbSyD/diag.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/diag.log adding: /tmp/tmpMYbSyD/ns_server.http_access.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.http_access.log adding: /tmp/tmpMYbSyD/syslog.tar.gz -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/syslog.tar.gz adding: /tmp/tmpMYbSyD/ns_server.debug.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.debug.log adding: /tmp/tmpMYbSyD/ddocs.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ddocs.log adding: /tmp/tmpMYbSyD/ns_server.reports.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.reports.log adding: /tmp/tmpMYbSyD/memcached.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/memcached.log adding: /tmp/tmpMYbSyD/ns_server.babysitter.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.babysitter.log adding: /tmp/tmpMYbSyD/ns_server.stats.log -> cbcollect_info_ns_1@10.5.2.117_20141209-024045/ns_server.stats.log