Forum hangs automatically in between


  • GNU/Linux

    I cannot confirm but it happen since I handed over admin access to a friend which I revoked later on when this issue popped up. I was under the impression that he was unknowingly pressing the " Restart " button. But it somehow happens that it is getting hung due to unknown reason. When I use restart command on terminal it won't work. I have to stop NodeBB and start it again. As @a_5mith mention, I tried to get a log only to get the terminal hung. Please help.



  • @meetdilip hey though it is hard to figure out the exact issue by the given symptoms but try running in dev mode by

    ./nodebb dev
    

    and keep an eye on the log screen, it has the feature of restarting automatically after any error or failure. See the log for errors (in red) to figure out which plugin or script is causing the problem then you will be much closer to solving your problem.


  • GNU/Linux

    Thanks @vatsal . 👍


  • GNU/Linux

    I got this

    root@install:~/home/nodebb# ./nodebb dev
    Launching NodeBB in "development" mode.
    To run the production build of NodeBB, please use "forever".
    More Information: https://docs.nodebb.org/en/latest/running/index.html
    info: NodeBB v0.5.1 Copyright (C) 2013-2014 NodeBB Inc.
    info: This program comes with ABSOLUTELY NO WARRANTY.
    info: This is free software, and you are welcome to redistribute it under certain conditions.
    info:
    info: Time: Wed Oct 15 2014 02:40:39 GMT+0000 (UTC)
    info: Initializing NodeBB v0.5.1
    info: * using configuration stored in: /root/home/nodebb/config.json
    info: * using redis store at 127.0.0.1:6379
    info: * using themes stored in: /root/home/nodebb/node_modules
    info: Base Configuration OK.
    Warning: Redis server does not require a password, but a password was supplied.
    morgan deprecated morgan(options): use morgan("default", options) instead src/logger.js:128:22
    morgan deprecated default format: use combined format src/logger.js:128:22
    info: [notifications.init] Registering jobs.
    info: [user.startJobs] Registering User Jobs
    Warning: Redis server does not require a password, but a password was supplied.
    Warning: Redis server does not require a password, but a password was supplied.
    Warning: Redis server does not require a password, but a password was supplied.
    info: [themes] Using theme nodebb-theme-lavender
    info: [plugins] Initializing plugins system
    info: Middlewares loaded.
    warn: [plugins/nodebb-plugin-featured-threads] staticDir is deprecated, use staticDirs instead
    info: [plugins] Found 1 CSS file(s) for plugin nodebb-plugin-featured-threads
    info: [plugins] Found 1 LESS file(s) for plugin nodebb-plugin-youtube-lite
    info: [plugins] Found 2 js file(s) for plugin nodebb-plugin-youtube-lite
    info: [plugins] Found 1 LESS file(s) for plugin nodebb-plugin-registration-question
    info: [plugins] Found 1 js file(s) for plugin nodebb-plugin-registration-question
    info: [plugins] Found 2 LESS file(s) for plugin nodebb-plugin-poll
    info: [plugins] Found 6 js file(s) for plugin nodebb-plugin-poll
    info: [plugins] Found 1 LESS file(s) for plugin nodebb-plugin-mentions
    info: [plugins] Found 2 js file(s) for plugin nodebb-plugin-mentions
    info: [plugins] Found 1 CSS file(s) for plugin nodebb-plugin-youtube
    info: [plugins] Found 1 LESS file(s) for plugin nodebb-plugin-markdown
    info: [plugins] Found 2 js file(s) for plugin nodebb-plugin-markdown
    info: [plugins] Found 1 CSS file(s) for plugin nodebb-widget-essentials
    info: [plugins] Found 3 js file(s) for plugin nodebb-theme-lavender
    info: [plugins] Loaded plugin: nodebb-plugin-featured-threads
    info: [plugins] Loaded plugin: nodebb-plugin-youtube-lite
    info: [plugins] Loaded plugin: nodebb-plugin-flipkart-iframe
    info: [plugins] Loaded plugin: nodebb-plugin-registration-question
    info: [plugins] Loaded plugin: nodebb-plugin-poll
    info: [plugins] Loaded plugin: nodebb-plugin-mentions
    info: [plugins] Loaded plugin: nodebb-plugin-flipkart
    info: [plugins] Loaded plugin: nodebb-plugin-emailer-local
    info: [plugins] Loaded plugin: nodebb-plugin-youtube
    info: [plugins] Loaded plugin: nodebb-plugin-markdown
    info: [plugins] Loaded plugin: nodebb-plugin-imgbed
    info: [plugins] Loaded plugin: nodebb-plugin-imgur
    info: [plugins] Loaded plugin: nodebb-plugin-dbsearch
    info: [plugins] Loaded plugin: nodebb-widget-essentials
    info: [plugins] Loaded plugin: nodebb-theme-lavender
    info: [plugins] Sorting hooks to fire in priority sequence
    warn: [plugins] The action:app.load hook is deprecated in favour of static:app.load, please notify the developers of the following plugins:

    • nodebb-plugin-featured-threads
    • nodebb-plugin-poll
    • nodebb-plugin-flipkart
      info: [hotswap] Router with id plugins replaced successfully
      info: [plugins] All plugins reloaded and rerouted
      info: [plugins] Plugins OK
      info: [meta/css] Minifying LESS/CSS
      info: [hotswap] Router with id auth replaced successfully
      warn: [meta/css] File not found! nodebb-plugin-featured-threads/css/main.css
      info: NodeBB attempting to listen on: 0.0.0.0:80
      error: NodeBB address in use, exiting...
      info: [sounds] Sounds OK
      [cluster] Child Process (7771) has exited (code: 0)

  • Admin

    Looks like there might be a problem with nodebb-plugin-featured-threads (which unfortunately is my plugin, I guess I haven't updated it to 0.5x yet)

    Try uninstalling, are you still running into the same problem?



  • The address in use that's seen there is really annoying and I can't reproduce it. Running stop, restart etc does nothing. I have to log into digital Ocean and reboot the droplet. Think @Ted has similar issues.
    could be that.



  • This happens to me on occasion - haven't tracked the plugin down responsible, as we aren't using featured threads.
    If I spot it, I'll but sure to make a note of it here. It seems that the only way to correct the issue is a quick sudo init 6 to reboot the server, then restarting NodeBB after the fact.



  • @meetdilip I agree with @Ted your node process is hanged due to uncertain shutdown just restart your machine or do following

     ps aux | grep -i node
    

    will show th list of all process running with name "node" note the process id and kill each one

    kill -9 process_id
    

    you don't need to restart the server 👍



  • @vatsal, to each his own.
    I run my NodeBB in a non-traditional configuration, so I have a 15 second downtime at most once I execute the server reboot and then the relaunch of the platform. While there are other ways, this works for me; plus, it's simple to do from my mobile if necessary.


  • GNU/Linux

    I must admit that I remember disabling the Featured Threads plugin before I gave access. I have disabled it and let it run. So far now downtime. Thanks you all. 💯


Log in to reply
 

Suggested Topics

| |