Error Reporting#
Description#
Many C Driver functions report errors by returning false or -1 and filling out a bson_error_t structure with an error domain, error code, and message. Use domain to determine which subsystem generated the error, and code for the specific error. message is a human-readable error description.
See also
Code |
Description |
|
|---|---|---|
|
|
You tried to send a message larger than the server’s max message size. |
|
Wrong credentials, or failure sending or receiving authentication messages. |
|
|
You tried an TLS connection but the driver was not built with TLS. |
|
|
You began iterating an exhaust cursor, then tried to begin another operation with the same mongoc_client_t. |
|
|
Failure related to creating or using a logical session. |
|
|
Failure related to arguments passed when initializing In-Use Encryption. |
|
|
Failure related to In-Use Encryption. |
|
|
You attempted to connect to a MongoDB server behind a load balancer, but the server does not advertize load balanced support. |
|
|
|
DNS failure. |
|
Timeout communicating with server, or connection closed. |
|
|
Failed to connect to server. |
|
|
|
Corrupt response from server. |
|
The server version is too old or too new to communicate with the driver. |
|
|
|
You passed bad arguments to mongoc_collection_find_with_opts(), or you called mongoc_cursor_next() on a completed or failed cursor, or the cursor timed out on the server. |
|
A resume token was not returned in a document found with mongoc_change_stream_next() |
|
|
|
Error API Version 1: Server error from command or query. The server error message is in |
|
|
Error API Version 2: Server error from command or query. The server error message is in |
|
A SASL error code. |
|
|
|
You passed an invalid or oversized BSON document as a parameter, or called mongoc_collection_create_index() with invalid keys, or the server reply was corrupt. |
|
|
You tried to create a collection with an invalid name. |
|
|
Many functions set this error code when passed bad parameters. Print the error message for details. |
|
You tried to use a command option the server does not support. |
|
|
An insert or update failed because because of a duplicate |
|
|
The operation failed because maxTimeMS expired. |
|
|
The |
|
|
Error API Version 1: Server error from a command. The server error message is in |
|
|
Error API Version 2: Server error from a command. The server error message is in |
|
|
|
Invalid or empty input to mongoc_collection_insert_one(), mongoc_collection_insert_bulk(), mongoc_collection_update_one(), mongoc_collection_update_many(), mongoc_collection_replace_one(), mongoc_collection_delete_one(), or mongoc_collection_delete_many(). |
|
Error API Version 1: Server error from mongoc_collection_insert_one(), mongoc_collection_insert_bulk(), mongoc_collection_update_one(), mongoc_collection_update_many(), mongoc_collection_replace_one(), |
|
|
Error API Version 2: Server error from mongoc_collection_insert_one(), mongoc_collection_insert_bulk(), mongoc_collection_update_one(), mongoc_collection_update_many(), mongoc_collection_replace_one(), |
|
|
|
The GridFS file is missing a document in its |
|
A data inconsistency was detected in GridFS. |
|
|
You passed a NULL filename to mongoc_gridfs_remove_by_filename(). |
|
|
You called mongoc_gridfs_file_set_id() after mongoc_gridfs_file_save(), or tried to write on a closed GridFS stream. |
|
|
A GridFS file is missing from |
|
|
An error occurred on a stream created from a GridFS operation like mongoc_gridfs_bucket_upload_from_stream(). |
|
|
|
Failure in SCRAM-SHA-1 or SCRAM-SHA-256 authentication. |
|
|
No replica set member or mongos is available, or none matches your read preference, or you supplied an invalid mongoc_read_prefs_t. |
|
There was a write concern error or timeout from the server. |
|
|
|
You attempted to start a transaction when one is already in progress, or commit or abort when there is no transaction. |
|
Error code produced by libmongocrypt. |
An error occurred in the library responsible for In-Use Encryption |
|
|
An Azure HTTP service responded with an error status |
|
An Azure service responded with invalid JSON data |
|
|
|
A GCP HTTP service responded with an error status |
|
A GCP service responded with invalid JSON data |
Error Labels#
In some cases your application must make decisions based on what category of error the driver has returned, but these categories do not correspond perfectly to an error domain or code. In such cases, error labels provide a reliable way to determine how your application should respond to an error.
Any C Driver function that has a bson_t out-parameter named reply may include error labels to the reply, in the form of a BSON field named “errorLabels” containing an array of strings:
{ "errorLabels": [ "TransientTransactionError" ] }
Use mongoc_error_has_label() to test if a reply contains a specific label. See mongoc_client_session_start_transaction() for example code that demonstrates the use of error labels in application logic.
The following error labels are currently defined. Future versions of MongoDB may introduce new labels.
TransientTransactionError#
Within a multi-document transaction, certain errors can leave the transaction in an unknown or aborted state. These include write conflicts, primary stepdowns, and network errors. In response, the application should abort the transaction and try the same sequence of operations again in a new transaction.
UnknownTransactionCommitResult#
When mongoc_client_session_commit_transaction() encounters a network error or certain server errors, it is not known whether the transaction was committed. Applications should attempt to commit the transaction again until: the commit succeeds, the commit fails with an error not labeled “UnknownTransactionCommitResult”, or the application chooses to give up.
Setting the Error API Version#
The driver’s error reporting began with a design flaw: when the error domain is MONGOC_ERROR_COLLECTION, MONGOC_ERROR_QUERY, or MONGOC_ERROR_COMMAND, the error code might originate from the server or the driver. An application cannot always know where an error originated, and therefore cannot tell what the code means.
For example, if mongoc_collection_update_one() sets the error’s domain to MONGOC_ERROR_COLLECTION and its code to 24, the application cannot know whether 24 is the generic driver error code MONGOC_ERROR_COLLECTION_UPDATE_FAILED or the specific server error code “LockTimeout”.
To fix this flaw while preserving backward compatibility, the C Driver 1.4 introduces “Error API Versions”. Version 1, the default Error API Version, maintains the flawed behavior. Version 2 adds a new error domain, MONGOC_ERROR_SERVER. In Version 2, error codes originating on the server always have error domain MONGOC_ERROR_SERVER or MONGOC_ERROR_WRITE_CONCERN. When the driver uses Version 2 the application can always determine the origin and meaning of error codes. New applications should use Version 2, and existing applications should be updated to use Version 2 as well.
Error Source |
API Version 1 |
API Version 2 |
|
|
|
mongoc_client_command_with_opts(), mongoc_database_command_with_opts(), and other command functions |
|
|
mongoc_collection_count_with_opts() mongoc_client_get_database_names_with_opts(), and other command helper functions |
|
|
mongoc_collection_insert_one() mongoc_collection_insert_bulk() mongoc_collection_update_one() mongoc_collection_update_many() mongoc_collection_replace_one() mongoc_collection_delete_one() mongoc_collection_delete_many() |
|
|
|
|
|
Write-concern timeout |
|
|
The Error API Versions are defined with MONGOC_ERROR_API_VERSION_LEGACY and MONGOC_ERROR_API_VERSION_2. Set the version with mongoc_client_set_error_api() or mongoc_client_pool_set_error_api().
See also