Anyone help to upgrade who hosted in Heroku

Technical Support

Suggested Topics


  • Help !

    Technical Support
    0 Votes
    1 Posts
    407 Views

    Hello !
    I'm a bit nil and I'd like to get into nodebb with my linux, I followed the installation steps as it should, but going on my forum link it does not work ... In local it works very Well, if I could get help from you, I'll be very thankful, thanks in advance...
    0_1527006440056_Capture du 2018-05-22 18-22-10.png

  • 0 Votes
    6 Posts
    3k Views

    @hukadan THANKS!!!

  • 0 Votes
    1 Posts
    658 Views

    I had this problem going from v0.9.4 -> v1.0.0 and now still have it going from v0.9.4 -> v1.0.1 but now I have additional information about it. See here for my original post.

    The tl;dr is

    $ ./nodebb upgrade 1. Bringing base dependencies up to date... OK 2. Checking installed plugins for updates... OK 3. Updating NodeBB data store schema... 18/3 15:15 [1511] - info: Beginning database schema update 18/3 15:15 [1511] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped 18/3 15:15 [1511] - info: [2015/11/06] Gravatar removal skipped 18/3 15:15 [1511] - info: [2015/12/15] Upgrading chats 18/3 15:15 [1511] - info: adding message 1 to new roomID 1 18/3 15:15 [1511] - info: adding message 2 to existing roomID 2 18/3 15:15 [1511] - info: adding message 3 to existing roomID 2 18/3 15:15 [1511] - info: adding message 4 to new roomID 2 18/3 15:15 [1511] - info: adding message 5 to new roomID 3 18/3 15:15 [1511] - error: [upgrade] Errors were encountered while updating the NodeBB schema: ERR value is not a valid float OK NodeBB Upgrade Complete!

    Before deleting the "message:x" keys from my redis database (to attempt the upgrade again) I noticed that message:5 was different than the other message keys. Specifically it seems the upgrader is choking on message:5

    "Bad" Message 5 key:
    0_1458338042461_redis-message5.png

    "Good" message key:
    0_1458338006166_redis-message6.png

    So it appears that the NodeBB upgrader does not like messages that do not have a touid or fromuid or possibly timestamp information. Should this be reported as a bug?

  • 0 Votes
    12 Posts
    5k Views

    @julian fantastic that works 🙂

    Thanks a lot.

    Great community 😊. Hope this issue could help some folks like me not really fit with git and npm 😊.

    Have a nice day.

  • 0 Votes
    11 Posts
    5k Views

    Thanks @navid @a_5mith ... Heroku installs are finicky at best, will reply with my thoughts in PR.