Home/ Questions/Q 8181455
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T00:31:43+00:00

I’m trying to upgrade my Node application from 0.4 to 0.6 along with all

  • 0

I’m trying to upgrade my Node application from 0.4 to 0.6 along with all modules. I think I’ve got everything correct, but MongoHQ returns:

db assertion failure

on every find/distinct call (connecting goes without errors)

Here’s my package.json, I’ve fixed all modules to one specific version, because I initially had some differences between local and Heroku. The only difference right now is that I’m running Node 0.6.19 local and Heroku runs 0.6.18:

{ "name": "expensesspreadsheet"
, "version": "0.0.1"
, "engines":
  { "node" : "0.6.18"
  , "npm"  : "1.1.9"
  } 
, "main": "server.js"
, "dependencies":
  { "ejs":             "0.7.1"
  , "ejs-ext":         "0.1.1"
  , "express":         "2.5.10"
  , "railway":         "0.2.17-pre3"
  , "jugglingdb":      "0.1.10"
  , "yaml":            "0.2.3"
  , "coffee-script":   "1.3.3"
  , "mime":            "1.2.5"
  , "qs":              "0.5.0"
  , "mongoose":        "2.7.0"
  , "mongodb":         "1.0.2"
  , "connect-mongodb": "1.1.4"
  , "connect-auth":    "0.5.2"
  , "moment" :         "1.6.2"
  , "connect-heroku-redis" : "0.1.5"
  , "node-markdown" :  "0.1.0"
  , "recaptcha" :      "1.1.0"
  , "sendgrid":        "0.2.1"
  }
, "scripts":
  { "test": "nodeunit test/*/*"
  }
}

I’m using Mongoose to define a schema. Connecting to MongoHQ works fine (no errors in the callback). Let me know if you like to see that code, but it’s very standard, almost straight from the Mongoose site.

However as discussed above, whenever I try to actually find any data, I get this nondescript error.

I’ve already manually connected to the database and executed the queries: works fine.
I’ve connected my local environment to my mongohq: works fine.

All of this still work on Node 0.4 with mongoose 2.3.13 and mongodb driver 0.9.6-7

So my questions:

  • Does any one know how to debug this “db assertion failure” error?
  • Any other ideas what might be wrong?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    After investigating this with MongoHQ support, this turned out to be an authentication problem.

    The MongoHQ URL supplied by Heroku was out of sync with the password on MongoHQ.

    In the old version of the application I was using a manually constructed URL, which explains why that one worked.

    How we figured that out? By looking at the MongoDB logs, these contained a clear authentication error. Sadly the returned JSON only contained the generic “db assertion failure” message with no additional detail.

    • 0