Forum completely gone



  • Hi,

    I found my forum like this today:

    alt text

    Logs are fine, redis database is fine, I don't understand what's happening 😞

    I pulled the latest code and upgraded, it didn't change anything, nothing works...

    Would anyone have an idea?


  • Global Moderator

    Have you tried restarting? Rebuilding? Running with ./nodebb slog?



  • cd /home/yourname/nodebb
    ./nodebb stop
    ./nodebb build
    ./nodebb start



  • Thank you for coming back to me,

    Alas, I tried that

    ~/nodebb$ ./nodebb build
    [benchpressjs] Unable to build or find a suitable native module, falling back to JS version
      started
    2019-04-16T11:34:21.841Z [4567/24540] - info: [build] Building in parallel mode
    2019-04-16T11:34:21.842Z [4567/24540] - info: [build]         plugin static dirs  build started
    2019-04-16T11:34:21.845Z [4567/24540] - info: [build]          requirejs modules  build started
    2019-04-16T11:34:21.846Z [4567/24540] - info: [build]           client js bundle  build started
    2019-04-16T11:34:21.847Z [4567/24540] - info: [build]            admin js bundle  build started
    2019-04-16T11:34:21.848Z [4567/24540] - info: [build]         client side styles  build started
    2019-04-16T11:34:21.848Z [4567/24540] - info: [build] admin control panel styles  build started
    2019-04-16T11:34:21.848Z [4567/24540] - info: [build]                  templates  build started
    2019-04-16T11:34:21.849Z [4567/24540] - info: [build]                  languages  build started
    2019-04-16T11:34:21.849Z [4567/24540] - info: [build]                     sounds  build started
    2019-04-16T11:34:21.861Z [4567/24540] - info: [build]         plugin static dirs  build completed in 0.019sec
    2019-04-16T11:34:22.229Z [4567/24540] - info: [build]                     sounds  build completed in 0.38sec
    2019-04-16T11:34:32.839Z [4567/24540] - info: [build]         client side styles  build completed in 10.991sec
    2019-04-16T11:34:41.183Z [4567/24540] - info: [build]           client js bundle  build completed in 19.337sec
    2019-04-16T11:34:41.183Z [4567/24540] - info: [build]            admin js bundle  build completed in 19.336sec
    2019-04-16T11:34:41.200Z [4567/24540] - info: [build]                  languages  build completed in 19.351sec
    2019-04-16T11:34:56.715Z [4567/24540] - info: [build] admin control panel styles  build completed in 34.867sec
    2019-04-16T11:34:57.839Z [4567/24540] - info: [build]                  templates  build completed in 35.991sec
    2019-04-16T11:34:58.452Z [4567/24540] - info: [build]          requirejs modules  build completed in 36.607sec
    2019-04-16T11:34:58.453Z [4567/24540] - info: [build] Asset compilation successful. Completed in 36.61sec.
    
    $ ./nodebb slog
    
    Starting NodeBB with logging output
    Hit Ctrl-C to exit
    The NodeBB process will continue to run in the background
    Use "./nodebb stop" to stop the NodeBB server
    
    Clustering enabled: Spinning up 1 process(es).
    
    2019-04-16T11:35:04.054Z [4567/24580] - info: Initializing NodeBB v1.12.1 https://*******.com
    [benchpressjs] Unable to build or find a suitable native module, falling back to JS version
    2019-04-16T11:35:06.105Z [4567/24580] - info: [socket.io] Restricting access to origin: https://*******.com:*
    2019-04-16T11:35:06.164Z [4567/24580] - info: Routes added
    2019-04-16T11:35:06.181Z [4567/24580] - info: NodeBB Ready
    2019-04-16T11:35:06.184Z [4567/24580] - info: Enabling 'trust proxy'
    2019-04-16T11:35:06.188Z [4567/24580] - info: NodeBB is now listening on: 0.0.0.0:4567
    

    Not luck, it's still just a grey website for now =/

    And if I click login, I can't even log in :s
    alt text



  • @Annihil Could this be contributing to the problem, no up address is attached to the port to listen on?

    info: NodeBB is now listening on: 0.0.0.0:4567


  • Staff Admin

    Make sure the database information in config.json is correct, it seems nodebb is connecting to an empty redis database.



  • @rod
    No that's right. It shows the same message to me, but my forum works just fine.
    the problem is this line
    [benchpressjs] Unable to build or find a suitable native module, falling back to JS version
    it means nodebb is unable to find node_modules, meaning package json file is damaged or missing. I would open the package.json file and add the following line in dependencies.

    "benchpressjs": "^1.2.5",



  • @Tiktak
    After adding "benchpressjs": "^1.2.5" to the package.json, and running npm install, I still have this error:

    [benchpressjs] Unable to build or find a suitable native module, falling back to JS version
    

    I ran ./nodebb build again, still no luck =/

    How could I fix that?

    Edit:

    ~/nodebb$ cat config.json
    {
        "url": "https://*******.com",
        "secret": "********-****-****-****-************",
        "database": "redis",
        "port": 4567,
        "redis": {
            "host": "127.0.0.1",
            "port": "6379",
            "password": "",
            "database": "0"
        }
    }
    

    My config.json seems correct


  • Global Moderator

    @Tiktak you're entirely incorrect about that benchpress warning. It's a warning, not an error. I should make that more clear. It simply means that compiling templates will be slower, so ./nodebb build will take longer.



  • @Annihil said in Forum completely gone:

    Unable to build or find a suitable native module, falling back to JS version

    I saw a similar problem here. perhaps you can try it out?
    https://community.nodebb.org/topic/12981/solved-nodebb-fresh-install-several-issues-upload-dev-mode-rebuild-restart-disabled



  • This post is deleted!


  • Alright, the redis database seemed find at first look (KEYS *), but checking with DBSIZE, the number of keys was only 1300, whereas it was 10 times bigger before, so I rolled back a previous dump, and it's working fine now. Don't know what happened, anyway, it's back to normal 🙂
    Sorry for the trouble!

    And keep up the outstanding work 💪


  • GNU/Linux Admin

    Check your redis logs. I believe there is an issue with your redis config being unable to persist to disk, therefore when your database restarts, everything is lost.


Log in to reply
 

Suggested Topics

  • 14
  • 3
  • 4
  • 8
  • 7
| |