Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-10757

Document MongoDB error codes

      Using the github.com/go-mgo/mgo driver and the latest stable version of MongoDB, I observe the following error:

      &QueryError

      { Code: 17406, Message: "getMore executor error: CappedPositionLost: CollectionScan died due to failure to restore tailable cursor position. Last seen record id: RecordId(200138)", Assertion: false, }

      I cannot find information about error code 17406 anywhere. More broadly, I cannot find information about MongoDB error codes. This page contains a list of codes: https://github.com/mongodb/mongo/blob/master/src/mongo/base/error_codes.err. However, the highest error code in the file is 13000.

      This page contains exit codes: https://docs.mongodb.com/manual/reference/exit-codes/ However, the highest code provided is code 100.

      Searching Google for 'mongodb error codes' yields the following Google Groups thread: https://groups.google.com/forum/#!topic/mongodb-user/cKV3rJVRfqEhttps://groups.google.com/forum/#!topic/mongodb-user/cKV3rJVRfqE. One of the links (https://github.com/mongodb/mongo/blob/master/docs/errors.md) returns a page not found.

      A list of PostgreSQL error codes is the top result when searching for "Postgres error codes" and can be found here: https://www.postgresql.org/docs/9.6/static/errcodes-appendix.html

      A list of MySQL error codes is the top result when searching for "MySQL error codes" and can be found here: https://dev.mysql.com/doc/refman/5.5/en/error-messages-server.html

      I am curious if a similar list exists for MongoDB. I attempted to ask a question about this on StackOverflow, however it will probably be closed by the time you read this.

      https://stackoverflow.com/q/46064684/329700

            Assignee:
            caleb.thompson@mongodb.com Caleb Thompson
            Reporter:
            kevinburke Kevin Burke
            Votes:
            12 Vote for this issue
            Watchers:
            31 Start watching this issue

              Created:
              Updated:
              Resolved:
              22 weeks, 6 days ago