Errors & Exceptions Reference
The standardized error codes returned by the Couchbase Ruby SDK, from cloud connection to sub-document.
All exceptions derive from a common base Couchbase exception. Exceptions (errors) are broken into different classifications:
Shared Exceptions — exceptions or errors thrown or returned by any service.
Specific Exceptions — exceptions or errors thrown by a service and specific to the service that threw or returned them.
Internal Exceptions — exceptions intended to be handled internally by the SDK and not exposed to the application.
The base exception,
CouchbaseException, has two properties — an
ErrorContext and an optional Cause.
ErrorContext provides extensive debugging information in JSON format.
Below are the exceptions, categorised by service.
ID Range: 1-99
Raised when a request cannot be completed until the user-defined timeout fires.
Note, this is a base class for #13 and #14 (Ambiguous and Unambiguous).
Raised when a request is cancelled and cannot be resolved in a non-ambiguous way. Most likely the request is in-flight on the socket and the socket gets closed.
Raised when it is unambiguously determined that the error was caused because of invalid arguments from the user. Usually only thrown directly when doing request arg validation on KV and sub-doc. Also commonly used as a parent class for many service-specific exceptions (see below).
Raised when it can be determined from the config unambiguously that a given service is not available. I.e. no query node in the config, or a memcached bucket is accessed and views or n1ql queries should be performed.
* Analytics: Errors: 23000, 23003.
* KV: Error code
ERR_EXISTS (0x02) when replace or remove with CAS.
* Query: code 12009.
Raised when a request is made but the current collection (including scope) is not found.
Raised when a timeout occurs and we aren’t sure if the underlying operation has completed. This normally occurs because we sent the request to the server successfully, but timed out waiting for the response. Note that idempotent operations should never return this, as they do not have ambiguity.
Raised when a timeout occurs and we are confident that the operation could not have succeeded. This normally would occur because we received confident failures from the server, or never managed to successfully dispatch the operation.
Raised when encoding of a user object failed while trying to write it to the cluster.
ID Range 100 - 199
Raised when the document requested was not found on the server — KV Code
Raised when in
getAllReplicas returns an empty stream because all the individual errors are dropped (i.e. all returned a
Raised when the value that was sent was too large to store (typically > 20MB); KV Code
Raised when an operation which relies on the document not existing fails because the document existed; KV Code
Raised when the specified durability level is invalid; KV Code
Raised when the specified durability requirements are not currently possible (for example, there are an insufficient number of replicas online); KV Code
Raised when A sync-write has not completed in the specified time and has an ambiguous result - it may have succeeded or failed, but the final result is not yet known. A SEQNO OBSERVE operation is performed and the vbucket UUID changes during polling. KV Code 0xa3
Raised when A durable write is attempted against a key which already has a pending durable write. KV Code 0xa2
Raised when The server is currently working to synchronize all replicas for previously performed durable operations (typically occurs after a rebalance). KV Code 0xa4
Raised when the path provided for a sub-document operation was not found; KV Code
The path provided for a sub-document operation did not match the actual structure of the document; KV Code
Raised when the path provided for a sub-document operation was not syntactically correct; KV Code
Raised when the path provided for a sub-document operation is too long, or contains too many independent components; KV Code
Raised when the value provided, if inserted into the document, would cause the document to become too deep for the server to accept; KV Code
Raised when the value provided for a sub-document operation would invalidate the JSON structure of the document if inserted as requested; KV Code
Raised when a Sub-Document operation is performed on a non-JSON document; KV Code
Raised when the existing number is outside the valid range for arithmetic operations; KV Code
Raised when the delta value specified for an operation is too large; KV Code
Raised when a sub-document operation which relies on a path not existing encountered a path which exists; KV Code
Raised when a macro was used which the server did not understand; KV Code:
Raised when a Sub-Document operation attempts to access multiple xattrs in one operation; KV Code:
Raised when a sub-document operation attempts to access a virtual attribute; KV Code:
Raised when a Sub-Document operation attempts to modify a virtual attribute; KV Code:
ID Range 200 - 299
Query: Raised when code range 4xxx other than those explicitly covered.
Query: Raised when codes 4040, 4050, 4060, 4070, 4080, 4090.
ID Range 300 - 399
Raised when error range 24xxx (excluded are specific codes in the errors below).
Raised when error code 23007.
Raised when error codes 24044, 24045, 24025.
Raised when error code 24034.
Raised when 24040.
Raised when 24039.
Raised when 24006.
ID Range 400 - 499
There are no specific errors for Search; see the Shared Error Definitions section for errors that apply to Search.
ID Range 600 - 699
ID Range 700 - 799
Note, in SDK 3.0, Field Level Encryption is only available as a Developer Preview with the Java SDK.
Generic cryptography failure. Inherits from CouchbaseException (=== # 0). Parent Type for all other Field-Level Encryption errors.
CryptoManager.encrypt() when encryption fails for any reason.
Should have one of the other Field-Level Encryption errors as a cause.
CryptoManager.decrypt() when decryption fails for any reason.
Should have one of the other Field-Level Encryption errors as a cause.
Raised by an encrypter or decrypter when the key does not meet expectations (for example, if the key is the wrong size).
Raised when a message cannot be decrypted because there is no decrypter registered for the algorithm.
Raised when a message cannot be encrypted because there is no encrypter registered under the requested alias.
Although the SDK and client application should be located in the same LAN-like environment (or cloud availability zone), and this is the only network configuration supported, we recognise that this set-up may not be possible during development. In particular, you may be developing against Couchbase Cloud from a laptop in a small or home office, where DNS-SRV may cause problems.
In order for your application to connect to your cloud, Couchbase Cloud creates a special kind of DNS record, called a Service record, or DNS-SRV record. DNS SRV records are widely supported and used frequently in systems like XMPP, and Kubernetes services. Occasionally, some DNS providers can run into issues with large DNS SRV records. This can manifest as a host not found issue. The actual problem is (a typically older) DNS server that cannot handle large responses which converts the error to host not found. This has frequently been observed when working from home with a service provider router that embeds a caching DNS Server.
Below is a list of log messages that you may see if you hit DNS SRV issues. These examples have been created in the circumstance that the SRV record is too long for the DNS provider to handle, and are included here so that they are findable by search, and you can then go to our cloud connection troubleshooting page.