0.9 Upgrade command failed


  • Plugin & Theme Dev

    Not sure where this come from
    0.8 to 0.9

    ./nodebb upgrade

    1. Bringing base dependencies up to date...
      Error: Command failed: ./Release/.deps/Release/obj.target/lwip_decoder/src/decoder/init.o.d.raw { dev: 2050,
      mode: 33188,
      nlink: 1,
      uid: 0,
      gid: 0,
      rdev: 0,
      blksize: 4096,
      ino: 11404925,
      size: 1093,
      blocks: 8,
      atime: Sat Nov 07 2015 13:06:51 GMT+0100 (CET),
      mtime: Sat Nov 07 2015 13:06:51 GMT+0100 (CET),
      ctime: Sat Nov 07 2015 13:06:51 GMT+0100 (CET) }
      ./Release/.deps/Release/obj.target/lwip_decoder/src/decoder/util.o.d.raw { dev: 2050,
      mode: 33188,
      nlink: 1,
      uid: 0,
      gid: 0,

    etc etc

    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/redisearch requires async@'~0.9.0' but will load
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/async,
    npm WARN unmet dependency which is version 1.4.2
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/grunt requires rimraf@'~2.2.8' but will load
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/rimraf,
    npm WARN unmet dependency which is version 2.4.3
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/request/node_modules/form-data requires async@'~0.9.0' but will load
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/async,
    npm WARN unmet dependency which is version 1.4.2
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-pre-gyp requires semver@'~4.3.3' but will load
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/semver,
    npm WARN unmet dependency which is version 5.0.1
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/grunt/node_modules/js-yaml/node_modules/argparse requires underscore@'~1.7.0' but will load
    npm WARN unmet dependency /home/lastnode/NodeBB/node_modules/underscore,
    npm WARN unmet dependency which is version 1.8.3
    npm ERR! Linux 3.10.23-xxxx-std-ipv6-64
    npm ERR! argv "node" "/usr/local/bin/npm" "i" "--production"
    npm ERR! node v0.10.35
    npm ERR! npm v2.13.3
    npm ERR! code EPEERINVALID

    npm ERR! peerinvalid The package redisearch@0.0.4 does not satisfy its siblings' peerDependencies requirements!
    npm ERR! peerinvalid Peer nodebb-plugin-dbsearch@0.2.17 wants redisearch@^0.0.5

    npm ERR! Please include the following file with any support request:
    npm ERR! /home/lastnode/NodeBB/npm-debug.log


  • Translator

    Is it just me or do we really need to revisit the way on upgrading NodeBB, since these topics keep appearing every time a new milestone comes out.


  • Admin

    @Kowlin Possibly... I made the mistake of using peer dependencies awhile back, and it's been nothing short of a headache. The idea in and of itself is fantastic, but the implementation was not suitable for a project like ours.

    @exodo Run these:

    $ npm unl lwip redisearch
    

    lwip usage removed from NodeBB anyway so removing it will cause no harm, and when you run ./nodebb upgrade again, the proper redisearch version will be installed.

    dbsearch requires a specific version of redisearch that doesn't match the version installed in NodeBB, I'm not entirely sure on the details.


  • Admin

    I'm open to solutions... we could have a pre-release channel that upgrades a week before a new milestone launches, so some users can test it out and report back, but we'd need actual forums willing to run that branch, and I get the feeling many simply stick to the stable release.


  • Translator

    @julian I'm willing to run a few test boards for those.
    Edit: I just need some sample data to backup and break 😉


  • Plugin & Theme Dev

    @julian said:

    @Kowlin Possibly... I made the mistake of using peer dependencies awhile back, and it's been nothing short of a headache. The idea in and of itself is fantastic, but the implementation was not suitable for a project like ours.

    @exodo Run these:

    $ npm unl lwip redisearch
    

    lwip usage removed from NodeBB anyway so removing it will cause no harm, and when you run ./nodebb upgrade again, the proper redisearch version will be installed.

    dbsearch requires a specific version of redisearch that doesn't match the version installed in NodeBB, I'm not entirely sure on the details.

    solved that issue

    not gettign this

    ./nodebb upgrade

    1. Bringing base dependencies up to date... OK
    2. Updating NodeBB data store schema.
      7/11 15:58 [19631] - warn: You have no mongo password setup!
      7/11 15:58 [19631] - info: [database] Checking database indices.
      7/11 15:58 [19631] - info: Beginning database schema update
      7/11 15:58 [19631] - info: [2015/02/08] Clearing reset tokens skipped
      7/11 15:58 [19631] - info: [2015/02/17] renaming home.tpl to categories.tpl skipped
      7/11 15:58 [19631] - info: [2015/2/23] Activating NodeBB Essential Rewards - skipped
      7/11 15:58 [19631] - info: [2015/02/24] Upgrading plugins:active to sorted set skipped
      7/11 15:58 [19631] - info: [2015/02/24] Upgrading privilege groups to system groups skipped
      7/11 15:58 [19631] - info: [2015/02/25] Upgrading menu items to dynamic navigation system skipped
      7/11 15:58 [19631] - info: [2015/05/07] Upgrading uid mappings to sorted set skipped
      7/11 15:58 [19631] - info: [2015/05/08] Fixing emails skipped
      7/11 15:58 [19631] - info: [2015/05/11] Updating widgets to tjs 0.2x skipped
      7/11 15:58 [19631] - info: [2015/05/20] Adding username:sorted and email:sorted skipped
      7/11 15:58 [19631] - info: [2015/06/02] Creating group sorted sets skipped
      7/11 15:58 [19631] - info: [2015/07/03] Enabling default composer plugin skipped
      7/11 15:58 [19631] - info: [2015/08/18] Creating children category sorted sets skipped
      7/11 15:58 [19631] - info: [2015/09/30] Converting default Gravatar image to default User Avatar
      7/11 15:58 [19631] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped
      7/11 15:58 [19631] - info: [2015/11/06] Removing gravatar

    /home/lastnode/NodeBB/node_modules/mongodb/lib/utils.js:97
    process.nextTick(function() { throw err; });
    ^
    Error: Callback was already called.
    at /home/lastnode/NodeBB/node_modules/async/lib/async.js:43:36
    at /home/lastnode/NodeBB/node_modules/async/lib/async.js:694:17
    at /home/lastnode/NodeBB/node_modules/async/lib/async.js:173:37
    at /home/lastnode/NodeBB/src/database/mongo/hash.js:15:4
    at handleCallback (/home/lastnode/NodeBB/node_modules/mongodb/lib/utils.js:95:12)
    at /home/lastnode/NodeBB/node_modules/mongodb/lib/collection.js:659:5
    at /home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:730:13
    at Callbacks.emit (/home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:84:3)
    at null.messageHandler (/home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:219:23)
    at Socket.<anonymous> (/home/lastnode/NodeBB/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:259:22)

    Error: undefined


  • Admin

    @exodo Can you pull latest v0.9.x and try upgrade again?


  • Plugin & Theme Dev

    @julian said:

    @exodo Can you pull latest v0.9.x and try upgrade again?

    git pull
    remote: Counting objects: 22, done.
    remote: Compressing objects: 100% (12/12), done.
    remote: Total 22 (delta 14), reused 18 (delta 10), pack-reused 0
    Unpacking objects: 100% (22/22), done.
    From https://github.com/NodeBB/NodeBB
    f145356..9de8250 master -> origin/master
    79c0049..05ef18f v0.9.x -> origin/v0.9.x
    Updating f145356..9de8250
    Fast-forward
    public/language/es/language.json | 4 ++--
    src/meta/settings.js | 1 +
    src/socket.io/user/picture.js | 8 --------
    3 files changed, 3 insertions(+), 10 deletions(-)
    [root@ns347108 NodeBB]# ./nodebb upgrade

    1. Bringing base dependencies up to date... OK
    2. Updating NodeBB data store schema.
      7/11 18:13 [1573] - warn: You have no mongo password setup!
      7/11 18:13 [1573] - info: [database] Checking database indices.
      7/11 18:13 [1573] - info: Beginning database schema update
      7/11 18:13 [1573] - info: [2015/02/08] Clearing reset tokens skipped
      7/11 18:13 [1573] - info: [2015/02/17] renaming home.tpl to categories.tpl skipped
      7/11 18:13 [1573] - info: [2015/2/23] Activating NodeBB Essential Rewards - skipped
      7/11 18:13 [1573] - info: [2015/02/24] Upgrading plugins:active to sorted set skipped
      7/11 18:13 [1573] - info: [2015/02/24] Upgrading privilege groups to system groups skipped
      7/11 18:13 [1573] - info: [2015/02/25] Upgrading menu items to dynamic navigation system skipped
      7/11 18:13 [1573] - info: [2015/05/07] Upgrading uid mappings to sorted set skipped
      7/11 18:13 [1573] - info: [2015/05/08] Fixing emails skipped
      7/11 18:13 [1573] - info: [2015/05/11] Updating widgets to tjs 0.2x skipped
      7/11 18:13 [1573] - info: [2015/05/20] Adding username:sorted and email:sorted skipped
      7/11 18:13 [1573] - info: [2015/06/02] Creating group sorted sets skipped
      7/11 18:13 [1573] - info: [2015/07/03] Enabling default composer plugin skipped
      7/11 18:13 [1573] - info: [2015/08/18] Creating children category sorted sets skipped
      7/11 18:13 [1573] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped
      7/11 18:13 [1573] - info: [2015/11/06] Removing gravatar
      7/11 18:13 [1573] - info: [2015/11/06] Gravatar pictures removed!
      7/11 18:13 [1573] - info: [upgrade] Schema update complete!
      OK

    NodeBB Upgrade Complete! 😄


  • Gamers

    is there a manual way to update? My dev server is still on 8.1; cannot update. Tried reloading and restarting several times...



  • This should do it...

    git fetch; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log


  • Plugin & Theme Dev

    @scottalanmiller He is on 0.8.1 that won't work. I believe you have to update to latest on 0.8.x before upgrading to 0.9

    @bitspook follow this guide

    https://docs.nodebb.org/en/latest/upgrading/index.html


  • Admin

    @pichalite said:

    I believe you have to update to latest on 0.8.x before upgrading to 0.9

    Yes, this is correct (although right now all of the upgrade scripts are still there, so this is a good reminder for me to remove them, thanks!).



  • Ah sorry, the probably....

    git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log



  • @julian said:

    we could have a pre-release channel that upgrades a week before a new milestone launches, so some users can test it out and report back

    I'd be happy to do this. I already run master locally, and upgrade X.X.X locally before doing anything on my production site.

    How would you let us know something is ready for testing?


  • Admin

    We develop on master, so if you run master you wouldn't experience the issues we'd have as well.

    Ideally it would be a site administrator who runs on stable, but when requested, will duplicate his db, and run the upgrade from, for example, v0.8.2 to v0.9.0


  • FreeBSD/OpenBSD

    @julian said:

    Ideally it would be a site administrator who runs on stable, but when requested, will duplicate his db, and run the upgrade from, for example, v0.8.2 to v0.9.0

    I would not mind doing that. Actually, I already do that. It is part of my upgrade process before upgrading the real forum. I am sure I am not the only one. I am late for the 0.9.0 but I would be OK to give it a try for the next release.



  • @scottalanmiller said:

    Ah sorry, the probably....

    git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

    Sorry for the newb post.....

    I've tried to upgrade 3 times now each time breaking my install. Is the above the way to go????

    Trying to upgrade from v0.7.1-dev to v0.9.0.

    Please help?



    1. Bringing base dependencies up to date... OK

    2. Updating NodeBB data store schema.
      10/11 12:39 [15868] - info: Beginning database schema update
      10/11 12:39 [15868] - error: [upgrade] NodeBB upgrade could not complete, as your database schema is too far out of date.
      10/11 12:39 [15868] - error: [upgrade] Please ensure that you did not skip any minor version upgrades.
      10/11 12:39 [15868] - error: [upgrade] (e.g. v0.1.x directly to v0.3.x)
      OK

                           NodeBB Upgrade Complete!


  • @Phate said:

    @scottalanmiller said:

    Ah sorry, the probably....

    git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

    Sorry for the newb post.....

    I've tried to upgrade 3 times now each time breaking my install. Is the above the way to go????

    Trying to upgrade from v0.7.1-dev to v0.9.0.

    Please help?

    You need to go through the 0.8.x series first.



  • git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.8.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log

    Make sure that things are okay then...

    git fetch; git pull, npm i; ./nodebb upgrade; git checkout v0.9.x; git pull; npm install; ./nodebb stop; ./nodebb upgrade; ./nodebb start; ./nodebb log


Log in to reply
 


Star

Looks like your connection to NodeBB was lost, please wait while we try to reconnect.