NodeBB v1.0.4-auto.2 many crashes

Bug Reports
  • NodeBB v1.0.4-auto.2

    29/5 02:45 [782] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    29/5 02:45 [779] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    (node) warning: possible EventEmitter memory leak detected. 11 connect listeners added. Use emitter.setMaxListeners() to increase limit.
    29/5 02:45 [774] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    Trace
        at Socket.addListener (events.js:252:17)
        at Socket.Readable.on (_stream_readable.js:673:33)
    29/5 02:45 [779] - info: [app] Database connection closed.
    29/5 02:45 [774] - info: [app] Database connection closed.
        at Socket.once (events.js:278:8)
    29/5 02:45 [779] - info: [app] Web server closed to connections.
    29/5 02:45 [774] - info: [app] Web server closed to connections.
        at Socket.unref (net.js:1013:10)
    29/5 02:45 [779] - info: [app] Shutdown complete.
    29/5 02:45 [774] - info: [app] Shutdown complete.
        at Connection.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/connection.js:453:23)
        at /home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:189:7
        at Array.forEach (native)
        at Pool.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:182:15)
        at Server.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/topologies/server.js:1072:31)
        at Server.close (/home/wing/nodebb/node_modules/mongodb/lib/server.js:417:17)
    29/5 02:45 [782] - info: [app] Database connection closed.
    29/5 02:45 [782] - info: [app] Web server closed to connections.
    29/5 02:45 [782] - info: [app] Shutdown complete.
    [cluster] Child Process (774) has exited (code: 0, signal: null)
    [cluster] Child Process (779) has exited (code: 0, signal: null)
    [cluster] Child Process (782) has exited (code: 0, signal: null)
    

Suggested Topics


  • v1.4.2 problem

    Bug Reports
    0 Votes
    4 Posts
    3k Views

    @JulianD Problems with permission. I'm having trouble making changes with root.

  • 0 Votes
    5 Posts
    2k Views

    Same entry in logs. The header content contains invalid characters. We've tried to add МойОфис both manually and via copy/paste so there's no possibility of adding some special symbols exept cyrillic.

  • Merge conflicts in 0.6.1

    Bug Reports
    0 Votes
    7 Posts
    3k Views

    @Shaun said:

    Have tried git reset --hard

    So the resolution for me was:

    git reset --hard 4686ae992318eeaaff1945868ee4cc094dcda17d
    git pull

    Wasn't sure where to find the hash, but git put it in the package.json file. I did not alter this file or any other after installing 0.6.0, so I'm very confused about how this conflict arose. The conflicting line was the version number, which in my local file was, apparently, 0.7.0-dev (I believe). Again, no clue how that got in there.

  • 0 Votes
    6 Posts
    1k Views

    Try running bash first

  • [Solved] Updating to 0.4.3

    Bug Reports
    0 Votes
    10 Posts
    2k Views

    I can for the first time say..

    Upgraded without any problems. 2 minutes in Terminal and I was rolling in .4.3 🙂

    But that's more on me, than on you guys.