Buy Hosting

NodeBB won't start after upgrade

Technical Support
  • Hawks CastH

    0_1539845513760_c2dadba5-8d48-4b84-8fd9-85bd6a810b5b-image.png

    And then immediately it states that NodeBB is not running.

    0_1539846085639_3d01a3bc-c9de-4376-9c4e-6f3c7fcd6881-image.png

    0_1539846176983_89e4aa9e-dd52-4f9b-9fd3-5aeb5f352c25-image.png

    When I load my site, it just states:

    0_1539846233522_f3fc660b-6823-49de-8624-9644345df82e-image.png

    0
  • Hawks CastH

    This is the Nodebb Log

    • at _combinedTickCallback (internal/process/next_tick.js:77:11)
      at Immediate._tickCallback (internal/process/next_tick.js:104:9)
      at runCallback (timers.js:672:20)
      at tryOnImmediate (timers.js:645:5)
      at processImmediate [as _immediateCallback] (timers.js:617:5)
      [cluster] Child Process (6699) has exited (code: 1, signal: null)
      [cluster] Spinning up another process...
      [cluster] Child Process (6693) has exited (code: 1, signal: null)
      [cluster] Spinning up another process...
      2018-10-18T07:08:50.033Z [6731] - info: Initializing NodeBB v1.10.2 https://forum.hawkscast.com
      2018-10-18T07:08:55.238Z [6731] - info: [socket.io] Restricting access to origin: https://forum.hawkscast.com馃槝
      2018-10-18T07:08:55.243Z [6725] - info: [socket.io] Restricting access to origin: https://forum.hawkscast.com馃槝
      2018-10-18T07:08:56.164Z [6725] - info: Routes added
      2018-10-18T07:08:56.172Z [6731] - info: Routes added
      2018-10-18T07:08:56.174Z [6725] - info: NodeBB Ready
      2018-10-18T07:08:56.181Z [6731] - info: NodeBB Ready
      2018-10-18T07:08:56.192Z [6725] - info: Enabling 'trust proxy'
      2018-10-18T07:08:56.199Z [6731] - info: Enabling 'trust proxy'
      2018-10-18T07:08:56.203Z [6725] - error: NodeBB address in use, exiting... message=listen EADDRINUSE 0.0.0.0:4568, stack=Error: listen EADDRINUSE 0.0.0.0:4568
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4568
      2018-10-18T07:08:56.209Z [6725] - error: message=listen EADDRINUSE 0.0.0.0:4568, stack=Error: listen EADDRINUSE 0.0.0.0:4568
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4568
      2018-10-18T07:08:56.212Z [6725] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      2018-10-18T07:08:56.214Z [6725] - error: message=Not running, stack=Error: Not running
      at Server.<anonymous> (net.js:1501:12)
      at Server.g (events.js:292:16)
      at emitNone (events.js:91:20)
      at Server.emit (events.js:185:7)
      at emitCloseNT (net.js:1552:8)
      at _combinedTickCallback (internal/process/next_tick.js:77:11)
      at Immediate._tickCallback (internal/process/next_tick.js:104:9)
      at runCallback (timers.js:672:20)
      at tryOnImmediate (timers.js:645:5)
      at processImmediate [as _immediateCallback] (timers.js:617:5)
      2018-10-18T07:08:56.215Z [6731] - error: NodeBB address in use, exiting... message=listen EADDRINUSE 0.0.0.0:4567, stack=Error: listen EADDRINUSE 0.0.0.0:4567
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4567
      2018-10-18T07:08:56.218Z [6731] - error: message=listen EADDRINUSE 0.0.0.0:4567, stack=Error: listen EADDRINUSE 0.0.0.0:4567
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4567
      2018-10-18T07:08:56.223Z [6731] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      2018-10-18T07:08:56.224Z [6731] - error: message=Not running, stack=Error: Not running
      at Server.<anonymous> (net.js:1501:12)
      at Server.g (events.js:292:16)
      at emitNone (events.js:91:20)
      at Server.emit (events.js:185:7)
      at emitCloseNT (net.js:1552:8)
      at _combinedTickCallback (internal/process/next_tick.js:77:11)
      at Immediate._tickCallback (internal/process/next_tick.js:104:9)
      at runCallback (timers.js:672:20)
      at tryOnImmediate (timers.js:645:5)
      at processImmediate [as _immediateCallback] (timers.js:617:5)
      [cluster] Child Process (6725) has exited (code: 1, signal: null)
      [cluster] Spinning up another process...
      [cluster] Child Process (6731) has exited (code: 1, signal: null)
      [cluster] Spinning up another process...
      2018-10-18T07:08:56.941Z [6766] - info: Initializing NodeBB v1.10.2 https://forum.hawkscast.com
      2018-10-18T07:09:02.078Z [6766] - info: [socket.io] Restricting access to origin: https://forum.hawkscast.com馃槝
      2018-10-18T07:09:02.245Z [6764] - info: [socket.io] Restricting access to origin: https://forum.hawkscast.com馃槝
      2018-10-18T07:09:03.032Z [6766] - info: Routes added
      2018-10-18T07:09:03.037Z [6766] - info: NodeBB Ready
      2018-10-18T07:09:03.055Z [6766] - info: Enabling 'trust proxy'
      2018-10-18T07:09:03.067Z [6766] - error: NodeBB address in use, exiting... message=listen EADDRINUSE 0.0.0.0:4567, stack=Error: listen EADDRINUSE 0.0.0.0:4567
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4567
      2018-10-18T07:09:03.069Z [6766] - error: message=listen EADDRINUSE 0.0.0.0:4567, stack=Error: listen EADDRINUSE 0.0.0.0:4567
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4567
      2018-10-18T07:09:03.070Z [6766] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      2018-10-18T07:09:03.072Z [6766] - error: message=Not running, stack=Error: Not running
      at Server.<anonymous> (net.js:1501:12)
      at Server.g (events.js:292:16)
      at emitNone (events.js:91:20)
      at Server.emit (events.js:185:7)
      at emitCloseNT (net.js:1552:8)
      at _combinedTickCallback (internal/process/next_tick.js:77:11)
      at Immediate._tickCallback (internal/process/next_tick.js:104:9)
      at runCallback (timers.js:672:20)
      at tryOnImmediate (timers.js:645:5)
      at processImmediate [as _immediateCallback] (timers.js:617:5)
      [cluster] Child Process (6766) has exited (code: 1, signal: null)
      [cluster] Spinning up another process...
      2018-10-18T07:09:03.206Z [6764] - info: Routes added
      2018-10-18T07:09:03.212Z [6764] - info: NodeBB Ready
      2018-10-18T07:09:03.227Z [6764] - info: Enabling 'trust proxy'
      2018-10-18T07:09:03.239Z [6764] - error: NodeBB address in use, exiting... message=listen EADDRINUSE 0.0.0.0:4568, stack=Error: listen EADDRINUSE 0.0.0.0:4568
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4568
      2018-10-18T07:09:03.241Z [6764] - error: message=listen EADDRINUSE 0.0.0.0:4568, stack=Error: listen EADDRINUSE 0.0.0.0:4568
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4568
      2018-10-18T07:09:03.242Z [6764] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      2018-10-18T07:09:03.243Z [6764] - error: message=Not running, stack=Error: Not running
      at Server.<anonymous> (net.js:1501:12)
      at Server.g (events.js:292:16)
      at emitNone (events.js:91:20)
      at Server.emit (events.js:185:7)
      at emitCloseNT (net.js:1552:8)
      at _combinedTickCallback (internal/process/next_tick.js:77:11)
      at Immediate._tickCallback (internal/process/next_tick.js:104:9)
      at runCallback (timers.js:672:20)
      at tryOnImmediate (timers.js:645:5)
      at processImmediate [as _immediateCallback] (timers.js:617:5)
      [cluster] Child Process (6764) has exited (code: 1, signal: null)
      [cluster] Spinning up another process...
      2018-10-18T07:09:03.789Z [6794] - info: Initializing NodeBB v1.10.2 https://forum.hawkscast.com
      2018-10-18T07:09:08.829Z [6794] - info: [socket.io] Restricting access to origin: https://forum.hawkscast.com馃槝
      2018-10-18T07:09:09.142Z [6802] - info: [socket.io] Restricting access to origin: https://forum.hawkscast.com馃槝
      2018-10-18T07:09:09.742Z [6794] - info: Routes added
      2018-10-18T07:09:09.751Z [6794] - info: NodeBB Ready
      2018-10-18T07:09:09.766Z [6794] - info: Enabling 'trust proxy'
      2018-10-18T07:09:09.779Z [6794] - error: NodeBB address in use, exiting... message=listen EADDRINUSE 0.0.0.0:4567, stack=Error: listen EADDRINUSE 0.0.0.0:4567
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4567
      2018-10-18T07:09:09.781Z [6794] - error: message=listen EADDRINUSE 0.0.0.0:4567, stack=Error: listen EADDRINUSE 0.0.0.0:4567
      at Object.exports._errnoException (util.js:1018:11)
      at exports._exceptionWithHostPort (util.js:1041:20)
      at Server._listen2 (net.js:1258:14)
      at listen (net.js:1294:10)
      at net.js:1404:9
      at _combinedTickCallback (internal/process/next_tick.js:83:11)
      at process._tickCallback (internal/process/next_tick.js:104:9), code=EADDRINUSE, errno=EADDRINUSE, syscall=listen, address=0.0.0.0, port=4567
      2018-10-18T07:09:09.782Z [6794] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      2018-10-18T07:09:09.783Z [6794] - error: message=Not running, stack=Error: Not running
      at Server.<anonymous> (net.js:1501:12)
      at Server.g (events.js:292:16)
      at emitNone (events.js:91:20)
      at Server.emit (events.js:185:7)
      at emitCloseNT (net.js:1552:8)
      at _combinedTickCallback (internal/process/next_tick.js:77:11)
      at Immediate._tickCallback (internal/process/next_tick.js:104:9)
      at runCallback (timers.js:672:20)
      at tryOnImmediate (timers.js:645:5)
      at processImmediate [as _immediateCallback] (timers.js:617:5)
      6 restarts in 10 seconds, most likely an error on startup. Halting.
    0
  • barisB

    Looks like NodeBB is already running on port 4567 and 4568 try stopping it with either ./nodebb stop or killing those procs. Then start again.

    1

Suggested Topics

  • C

    讘注讬讬讛 讘注专讬讻转 讗讬诪讜讙讬'

    Technical Support
    0 Votes
    6 Posts
    434 Views
    C

    @pitaj 讗谞讬 诪爪诇讬讞 诇讛讬讻谞住 诇驻讗谞诇. 讛讘注讬讛 砖讗讬谞谞讬 讬讻讜诇 诇注专讜讱
    39c6e38f-f603-4efe-a193-71b2a0fec860-转诪讜谞讛.png

    讻讗砖专 讗谞讬 诇讞讜抓 注诇 讛诇讞爪谉, 诇讗 谞注砖讛 讚讘专

  • A

    Variable's reference in tpl files

    Technical Support
    0 Votes
    2 Posts
    262 Views
    PitaJP

    @arc002 ajaxify.data is just the data the template was run with. Changing it does nothing to the already rendered page.

    What you want is to add a hook for filter:topics.getand modify the data there.

    https://github.com/NodeBB/NodeBB/blob/dbb59228f2ded01ee5829bbd71363ccbd568e6b5/src/topics/index.js#L142

  • I

    NodeBB 1.13.3 - OSSEC issue

    Technical Support
    0 Votes
    2 Posts
    298 Views
    I

    I have resolved this issue by adding the following rule to local_rules.xml.

    <rule id="100014" level="0">
    <if_sid>31533</if_sid>
    <url>^/socket.io/</url>
    <description>Ignoring NodeBB (socket.io).</description>
    </rule>

  • rodR

    v1.0.1: Upgrade fails during 'adding message to chat room'

    Technical Support
    0 Votes
    1 Posts
    657 Views
    rodR

    I had this problem going from v0.9.4 -> v1.0.0 and now still have it going from v0.9.4 -> v1.0.1 but now I have additional information about it. See here for my original post.

    The tl;dr is

    $ ./nodebb upgrade 1. Bringing base dependencies up to date... OK 2. Checking installed plugins for updates... OK 3. Updating NodeBB data store schema... 18/3 15:15 [1511] - info: Beginning database schema update 18/3 15:15 [1511] - info: [2015/09/30] Converting default Gravatar image to default User Avatar skipped 18/3 15:15 [1511] - info: [2015/11/06] Gravatar removal skipped 18/3 15:15 [1511] - info: [2015/12/15] Upgrading chats 18/3 15:15 [1511] - info: adding message 1 to new roomID 1 18/3 15:15 [1511] - info: adding message 2 to existing roomID 2 18/3 15:15 [1511] - info: adding message 3 to existing roomID 2 18/3 15:15 [1511] - info: adding message 4 to new roomID 2 18/3 15:15 [1511] - info: adding message 5 to new roomID 3 18/3 15:15 [1511] - error: [upgrade] Errors were encountered while updating the NodeBB schema: ERR value is not a valid float OK NodeBB Upgrade Complete!

    Before deleting the "message:x" keys from my redis database (to attempt the upgrade again) I noticed that message:5 was different than the other message keys. Specifically it seems the upgrader is choking on message:5

    "Bad" Message 5 key:
    0_1458338042461_redis-message5.png

    "Good" message key:
    0_1458338006166_redis-message6.png

    So it appears that the NodeBB upgrader does not like messages that do not have a touid or fromuid or possibly timestamp information. Should this be reported as a bug?

  • JenklerJ

    Latest pull breaks NodeBB, packages are out-of-date?

    Technical Support
    0 Votes
    14 Posts
    4k Views
    W

    Even running ./nodebb upgrade on a working 0.9.1 installation produces the problem

    It happened on my sandbox as well as on the production system.

    Well, the upgrade is done, and there is no reason for me to worry about it. I just wanted to mention it, in case it's others had the same problem and to enable the developers to investigate, if needed

Copyright 漏 2023 NodeBB | Contributors