Community

noddebb upgrade script timeout

Technical Support
  • S 
      version:  1.10.1
  Node ver: v8.11.3
  git hash: c1e98eefa7fe93431ac312ecc0d90314db2c49b1

  database: mongo
        version: 3.6.3
        engine:  wiredTiger

    Parsing upgrade scripts...
OK | 4 script(s) found, 53 skipped
  → [2017/6/22] Hash all IP addresses stored in Recent IPs zset...
    [###########  ] (686800/802153) 85% Error occurred
Error occurred during upgrade: MongoError: cursor id 23654971494 not found
    at /home/alaa/Nodebb/forum/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:598:61
    at authenticateStragglers (/home/alaa/Nodebb/forum/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:516:16)
    at Connection.messageHandler (/home/alaa/Nodebb/forum/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:552:5)
    at emitMessageHandler (/home/alaa/Nodebb/forum/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:309:10)
    at Socket.<anonymous> (/home/alaa/Nodebb/forum/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:452:17)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)

/home/alaa/Nodebb/forum/node_modules/mongodb/lib/utils.js:132
      throw err;

    https://github.com/NodeBB/NodeBB/issues/6661

    0

Suggested Topics

  • FrankMF
    ●

    Error after upgrading to v1.13.1

    Technical Support
    0 Votes
    5 Posts
    275 Views

    FrankMF

    I am on Debian Buster 10

  • Aaron MurrayA
    ●

    NodeBB Crashed after upgrade

    Technical Support
    0 Votes
    11 Posts
    1429 Views

    DravereD

    Good to hear. Just in case you need it in the future.

    MongoDB has very good documentation and you can find it here: https://docs.mongodb.com/

    Dropping the database would be described here: https://docs.mongodb.com/manual/reference/method/db.dropDatabase/index.html

    Thus probably would be something along the line of:

    use nodebb db.dropDatabase()
  • M
    ●

    NodeBB Upgrade caused issues

    Technical Support
    0 Votes
    3 Posts
    1029 Views

    M

    I've found the cause, the Wordpress SSO plugin was causing issues.

  • J
    ●

    Need some help, upgrade error.

    Technical Support
    0 Votes
    4 Posts
    814 Views

    J

    @baris problem solved, many thanks!

  • rodR
    ●

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

    Technical Support
    0 Votes
    1 Posts
    630 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?

| | | |
Copyright © 2023 NodeBB | Contributors