Upgrading nodebb from v0.5 to v0.8 (problems)



  • Hi Guys!

    So I know this is a large upgrade, but after Googling for about a week and reading up on other's mistakes/fallbacks with upgrading I thought I knew what to do. Apparently something went wrong.

    I started with v0.5.4 with redis 2.8.4 and followed these upgrade steps:

    1. Backup dump.rdb
    2. Backup nodebb/public/uploads
    3. Upgraded redis to 3.0.4 (stable)
    4. Copied saved dump.rdb to overwrite the new dump.rdb created by the redis installation
    5. Updated to latest version of nodebb v0.5
      a. git remote add upstream https://github.com/NodeBB/NodeBB.git (because my origin branch is a personal hack on Bitbucket)
      b. git fetch upstream
      c. git pull upstream v0.5.x <-- at this point there will be conflicts
      d. git checkout --theirs ..files.. <-- resolve conflicts
      e. git commit -a <-- commit merged files
      f. node app --upgrade
    6. Updated to latest version of nodebb v0.6
      a. git checkout v0.6.x
      b. npm install
      c. For some reason I have to install redis and connect-redis packages before running node app?
      d. npm install redis connect-redis
      e. node app --upgrade
    7. Updated to latest version of nodebb v0.7
      a. git checkout v0.7.x
      b. npm install
      c. node app --upgrade
    8. Updated to latest version of nodebb v0.8
      a. git checkout v0.8.x
      b. npm install
      c. ./nodebb upgrade

    Now, except for the random missing dependencies on branch v0.6.x, there are no errors during the above process. Once I get to branch v0.8.x and try to run node app, I get the following log:

    29/9 15:22 [31122] - info: NodeBB v0.8.2 Copyright (C) 2013-2014 NodeBB Inc.
    29/9 15:22 [31122] - info: This program comes with ABSOLUTELY NO WARRANTY.
    29/9 15:22 [31122] - info: This is free software, and you are welcome to redistribute it under certain conditions.
    29/9 15:22 [31122] - info:
    29/9 15:22 [31122] - info: Time: Tue Sep 29 2015 15:22:32 GMT-0400 (EDT)
    29/9 15:22 [31122] - info: Initializing NodeBB v0.8.2
    29/9 15:22 [31122] - info: NodeBB Ready
    29/9 15:22 [31122] - info: Enabling 'trust proxy'
    29/9 15:22 [31122] - info: NodeBB is now listening on: 127.0.0.1:4567
    29/9 15:22 [31122] - error: TypeError: Object socket.io#piR7li has no method 'split'
        at Redis.onmessage (/var/gamers-tavern/node_modules/socket.io-redis/index.js:92:26)
        at RedisClient.emit (events.js:106:17)
        at RedisClient.return_reply (/var/gamers-tavern/node_modules/redis/index.js:624:22)
        at RedisClient.<anonymous> (/var/gamers-tavern/node_modules/redis/index.js:284:18)
        at process._tickCallback (node.js:448:13)
    TypeError: Object socket.io#piR7li has no method 'split'
        at Redis.onmessage (/var/gamers-tavern/node_modules/socket.io-redis/index.js:92:26)
        at RedisClient.emit (events.js:106:17)
        at RedisClient.return_reply (/var/gamers-tavern/node_modules/redis/index.js:624:22)
        at RedisClient.<anonymous> (/var/gamers-tavern/node_modules/redis/index.js:284:18)
        at process._tickCallback (node.js:448:13)
    29/9 15:22 [31122] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    29/9 15:22 [31122] - info: [app] Database connection closed.
    29/9 15:22 [31122] - info: [app] Web server closed to connections.
    29/9 15:22 [31122] - info: [app] Shutdown complete.
    

    Thoughts?


  • Plugin & Theme Dev

    Downgrade redis npm module.



  • @hek said:

    Downgrade redis npm module.

    Downgrade to which version? And you are referring to the socket.io-redis module, correct?


  • Plugin & Theme Dev



  • Thank you for that link! So oddly enough, the redis module was not install but when I ran npm install redis@1.0.0 my forum started correctly. Thanks!


  • Admin

    @hek said:

    Downgrade redis npm module.

    Wow, that was awfully specific! How did you know? :smile:


  • Global Moderator

    @julian Obviously magic


Log in to reply
 


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