• Plugin & Theme Dev

    I have switched your proposed extra flow with console logs to parallel, and receive these results:

    1
    2.sounds
    5/3 04:54 [31928] - error: [sounds] Could not initialise sounds: EEXIST: file already exists, symlink '/web/overseers/node/forum/public/uploads/sounds/.gitignore' -> '/web/overseers/node/forum/public/sounds/.gitignore'
    2.blaclist
    2.b.minifycss
    2.b.minify
    5/3 04:54 [31928] - info: NodeBB Ready
    5/3 04:54 [31928] - info: Enabling 'trust proxy'
    2.compile
    5/3 04:54 [31928] - info: NodeBB is now listening on: 0.0.0.0:8081
    
  • NodeBB

    Does it work in prod if you disable sounds with this?

    function (next) {
            next();
    	// meta.sounds.init(function (err) {
    	//	console.log('2.sounds');
    	//	next(err);
    	//})
    },
  • NodeBB

    Looks like sounds module is just logging the error but not preventing the flow.

    I suggest switching to async.waterfall and checking the plugins using 'static:app.preload' hook and making sure the server has enough memory.

  • Plugin & Theme Dev

    @baris yep. Sounds are not the problem, the result is the same with the disabled sound step.

    Interesting if memory is an issue now. Yes, it's a 512MB server, for some reason, it's a limit now after 5 years?..
    When I look at htop, it peaks at max memory when forum startups, but it was not an issue before.

    I can try to ask the provider to give more memory to check the hypothesis and let you know if it helped.

  • NodeBB

    Try to setup some swap if you can, and yes memory can be an issue over time if the database is on the same server as well.

    You said you hit step 3 so that means the build was succesfull with async.waterfall it means it is getting stuck in one of the plugins that is using 'static:app.preload' you can find which plugins use it with the above grep command.

  • Plugin & Theme Dev

    Thank you everybody for helping me with forum troubleshooting. The problem has been found. It's memory limit. After a few years of use, 512MB RAM + 256MB swap is not enough anymore (I have some suspicions that swap does not kick in, but it's a topic for a different story).

    If somebody searches, and no changes plugins, core, or hardware, and you do not have plugins that depend on external services - check if it's a memory issue.

Suggested Topics

| |