[solved] Don't migrated NodeBB

Technical Support
  • I copied NodeBB folder and installed all what needed:

    sudo apt-get install git nodejs nodejs-legacy npm redis-server imagemagick
    

    next step:

    sudo service redis-server stop; sudo cp dump.rdb /var/lib/redis/; sudo service redis-server start
    

    What else should I do?

    nodebb dev:

    Clustering enabled: Spinning up 1 process(es).
    
    27/4 01:03 [2441] - info: Time: Mon Apr 27 2015 01:03:30 GMT+0300 (MSK)
    27/4 01:03 [2441] - info: Initializing NodeBB v0.7.0-dev
    27/4 01:03 [2441] - verbose: * using configuration stored in: /home/nodebb/config.json
    27/4 01:03 [2441] - verbose: * using redis store at 127.0.0.1:6379
    27/4 01:03 [2441] - verbose: * using themes stored in: /home/nodebb/node_modules
    [cluster] Child Process (2441) has exited (code: null, signal: SIGSEGV)
    [cluster] Spinning up another process...
    

    last line nodebb upgrade:

    ./nodebb: line 26:  2502 Segmentation fault      (core dumped) "$node" app --upgrade
    

    I have done several times nodebb setup.

  • Not sure if this is your issue, but you don't want to use "service redis-server stop", this doesn't actually check to see if the data has been written to disk, and it could mean your dump.rdb is corrupted. Use "redis-cli shutdown" instead.

  • @sergej-saveljev said:

    I copied NodeBB folder and installed all what needed:

    sudo apt-get install git nodejs nodejs-legacy npm redis-server imagemagick
    

    next step:

    sudo service redis-server stop; sudo cp dump.rdb /var/lib/redis/; sudo service redis-server start
    

    What else should I do?

    nodebb dev:

    Clustering enabled: Spinning up 1 process(es).
    
    27/4 01:03 [2441] - info: Time: Mon Apr 27 2015 01:03:30 GMT+0300 (MSK)
    27/4 01:03 [2441] - info: Initializing NodeBB v0.7.0-dev
    27/4 01:03 [2441] - verbose: * using configuration stored in: /home/nodebb/config.json
    27/4 01:03 [2441] - verbose: * using redis store at 127.0.0.1:6379
    27/4 01:03 [2441] - verbose: * using themes stored in: /home/nodebb/node_modules
    [cluster] Child Process (2441) has exited (code: null, signal: SIGSEGV)
    [cluster] Spinning up another process...
    

    last line nodebb upgrade:

    ./nodebb: line 26:  2502 Segmentation fault      (core dumped) "$node" app --upgrade
    

    I have done several times nodebb setup.

    Docs.nodebb.org

  • I installed NodeBB again and all is well. I will work in this vein. Thanks!

  • Excuse me please. Something went wrong when copying files from one server to another, in connection with which the files were corrupted.

    Redis database can be copied as I said above, but before that need to run redis-cli -a mypassword SAVE. I did not understand what the command redis-cli shutdown, sorry.

  • redis-cli shutdown is just a shortcut for redis-cli save and redis-server stop

    But unless your forum is very active, it's unlikely this is how it was corrupted.

  • @yariplus Strangely, I tried to run this command but redis-server does not turn off.


Suggested Topics


  • 0 Votes
    9 Posts
    150 Views

    @DownPW of you're not already serving static assets with nginx, I'd recommend doing that. You should be able to set a separate rate limit for that while still protecting NodeBB.

    It may also be possible to whitelist cloudflare so it can bypass the rate limit.

  • 0 Votes
    1 Posts
    213 Views

    כאשר אני לוחץ על בנה נכסי אימוגי',
    אני מקבל את השגיאה הזו:
    2fa1266c-2b43-491b-b1cc-2c5fef66526d-תמונה.png

  • 0 Votes
    9 Posts
    2k Views

    @baris tried right after you posted it yesterday and it worked, thank you!

    @julian it was definitely staying at 3.2.1 for me, both in the admin panel and through SSH. Were the commands I've used correct?

  • 1 Votes
    1 Posts
    1k Views

    When trying to boot NodeBB on new server i get

    at Function.MongoError.create (/home/***/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/error.js:31:11) at /home/***/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:754:66 at Callbacks.emit (/home/***/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:95:3) at null.messageHandler (/home/***/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:243:23) at Socket.<anonymous> (/home/***/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:262:22) at Socket.emit (events.js:107:17) at readableAddChunk (_stream_readable.js:163:16) at Socket.Readable.push (_stream_readable.js:126:10) at TCP.onread (net.js:538:20)

    Any tips on best practices for migrating servers?

  • 0 Votes
    2 Posts
    1k Views

    @FreshPrince Whether a role management library has been created?