0.8.0 Partial not loaded

Technical Support

Suggested Topics

  • 0 Votes
    31 Posts

    Finally made it from v0.6.0 to v1.4.1

    This was my upgrade route (hosted on DigitalOcean and with a mongo database - shell 2.6.7, node v0.10.38)

    *v0.6 to v0.6.1 git fetch git reset --hard origin/v0.6.x git describe --tags ./nodebb upgrade *v0.6.1 to v0.7.0 git checkout v0.7.0 ./nodebb upgrade npm install touch npm install minimist npm install colors *v0.7.0 to v0.7.3 git reset --hard origin/v0.7.x git describe --tags ./nodebb upgrade node app --upgrade *install nvm curl https://raw.githubusercontent.com/creationix/nvm/v0.11.1/install.sh | bash *Restart terminal nvm install v0.10.39 * Change index.js in /root/"yourfoldername"/node_modules/connect-mongo from *module.exports = require('./src'); *to *module.exports = require('connect-mongo/es5'); *edit /etc/mongod.conf, to uncomment auth = true line service mongod restart mongo use admin db.createUser({user: "adminname", pwd: "yourpassword", roles: ["readWrite"]}) use *name of the db where nodebb is installed* db.updateUser( "adminname", { roles : [ { role : "dbAdmin", db : "*name of the db where nodebb is installed*" }, { role : "readWrite", db : "*name of the db where nodebb is installed*" } ] } ) ./nodebb upgrade ./nodebb start ./nodebb stop *v0.7.3 to v0.8.x git checkout v0.8.x git pull ./nodebb upgrade ./nodebb start ./nodebb stop *v0.8.2 to v0.9.x git checkout v0.9.x git pull ./nodebb upgrade ./nodebb start ./nodebb stop *v0.9.4 to v1.4.1 git checkout v1.x.x git pull nvm install v6.2.1 nvm use v6.2.1 ./nodebb upgrade *edit /etc/mongod.conf, to uncomment noauth=true line

    This should help to avoid any issue with mmmagic, kerberos, bluebird and the key_1_value_-1 already exist error.

    Et voilà !

    Thanks again for your help Julian !

  • 0 Votes
    14 Posts

    @scottalanmiller said in 503 - temporarily unavailable due to excessive load:

    So our daily views (as reported by NodeBB) is 32K - 98K.

    It sounds like I should be a little amazed that 512 MB of memory works...

    I'll have to scale up my Digital Ocean tonight...

  • 0 Votes
    8 Posts

    I have updated to 0.9.2 now and it seams fine 😉

  • 0 Votes
    1 Posts

    I have a problem, yet again...

    So recently, I have discovered that when I start NodeBB, the page only loads the top bar. http://prntscr.com/7jts5k If anybody knows how to fix this, your input would be appreciated.

    FIX: Stop the following services: redis-server & redis_6379. Run redis-server in the terminal to restart it. Restart nodebb.


  • 1 Votes
    1 Posts

    Hi guys!

    I have previous 0.5.0-2 version of forum on Heroku. It works fine. When I updated NodeBB to 0.6.1 version it crashed with error. Any ideas?

    2015-04-30T06:31:05.151177+00:00 heroku[web.1]: State changed from crashed to starting
    2015-04-30T06:31:12.946261+00:00 heroku[web.1]: Starting process with command npm start
    2015-04-30T06:31:16.159469+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
    2015-04-30T06:31:16.159494+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
    2015-04-30T06:31:16.817884+00:00 app[web.1]:
    2015-04-30T06:31:16.817890+00:00 app[web.1]: > [email protected] start /app
    2015-04-30T06:31:16.817892+00:00 app[web.1]: > ./nodebb start
    2015-04-30T06:31:16.817893+00:00 app[web.1]:
    2015-04-30T06:31:16.854535+00:00 app[web.1]: sh: 1: ./nodebb: Permission denied
    2015-04-30T06:31:16.873738+00:00 app[web.1]: npm ERR! Linux 3.13.0-49-generic
    2015-04-30T06:31:16.878037+00:00 app[web.1]: npm ERR! code ELIFECYCLE
    2015-04-30T06:31:16.878041+00:00 app[web.1]: npm ERR! [email protected] start: ./nodebb start
    2015-04-30T06:31:16.878043+00:00 app[web.1]: npm ERR! Exit status 126
    2015-04-30T06:31:16.878044+00:00 app[web.1]: npm ERR!
    2015-04-30T06:31:16.878046+00:00 app[web.1]: npm ERR! Failed at the [email protected] start script './nodebb start'.
    2015-04-30T06:31:16.878048+00:00 app[web.1]: npm ERR! This is most likely a problem with the nodebb package,
    2015-04-30T06:31:16.878049+00:00 app[web.1]: npm ERR! not with npm itself.
    2015-04-30T06:31:16.878050+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
    2015-04-30T06:31:16.878052+00:00 app[web.1]: npm ERR! ./nodebb start
    2015-04-30T06:31:16.878054+00:00 app[web.1]: npm ERR! You can get their info via:
    2015-04-30T06:31:16.878693+00:00 app[web.1]: npm ERR! npm owner ls nodebb
    2015-04-30T06:31:16.878696+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
    2015-04-30T06:31:16.889120+00:00 app[web.1]:
    2015-04-30T06:31:16.899848+00:00 app[web.1]: npm ERR! /app/npm-debug.log
    2015-04-30T06:31:16.866363+00:00 app[web.1]:
    2015-04-30T06:31:16.874577+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
    2015-04-30T06:31:16.875101+00:00 app[web.1]: npm ERR! node v0.12.2
    2015-04-30T06:31:16.876089+00:00 app[web.1]: npm ERR! npm v2.7.4
    2015-04-30T06:31:16.897668+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
    2015-04-30T06:31:17.925842+00:00 heroku[web.1]: Process exited with status 1
    2015-04-30T06:31:17.938969+00:00 heroku[web.1]: State changed from starting to crashed