Community

Visiting administrator users pages crashes the Nodebb - 503

Technical Support
  • Pramvir RatheeP

    i am using nodebb 1.0.3, everything was working fine when did a new install, but when i imported BBpress data, about 0.1 million posts,
    now visiting the pages of admin only Crashesh the nodeBB, 503 excessive load error, what to do now ?

    0
  • Pramvir RatheeP

    @julian
    Upgraded it to 1.4.2, same problem.

    1. only visiting amin users pages gived error 503
    2. Loged in users whio visit amin user profile crash the nodebb
    3. Logout browsing of forum is smooth.
    4. when i click topic tools, or new topic, same problem, Nodebb get hang and gives error 503.
      Here are mongo errors
    2017-01-07T19:14:47.312-0500 I COMMAND  [conn18] command anil3.objects command: getMore { getMore: 25063041612, collection: "objects", batchSize: 1000 } cursorid:25063041612 keyUpdates:0 writeConflicts:0 numYields:11 nreturned:1000 reslen:41990 locks:{ Global: { acquireCount: { r: 24 } }, Database: { acquireCount: { r: 12 } }, Collection: { acquireCount: { r: 12 } } } protocol:op_query 103ms
2017-01-07T19:14:47.328-0500 I COMMAND  [conn14] command anil3.objects command: getMore { getMore: 21957663447, collection: "objects", batchSize: 1000 } cursorid:21957663447 keyUpdates:0 writeConflicts:0 numYields:11 nreturned:1000 reslen:41990 locks:{ Global: { acquireCount: { r: 24 } }, Database: { acquireCount: { r: 12 } }, Collection: { acquireCount: { r: 12 } } } protocol:op_query 114ms
2017-01-07T19:14:47.975-0500 I COMMAND  [conn14] command anil3.objects command: getMore { getMore: 21957663447, collection: "objects", batchSize: 1000 } cursorid:21957663447 keyUpdates:0 writeConflicts:0 numYields:13 nreturned:1000 reslen:41990 locks:{ Global: { acquireCount: { r: 28 } }, Database: { acquireCount: { r: 14 } }, Collection: { acquireCount: { r: 14 } } } protocol:op_query 180ms
2017-01-07T19:14:47.976-0500 I COMMAND  [conn18] command anil3.objects command: getMore { getMore: 25063041612, collection: "objects", batchSize: 1000 } cursorid:25063041612 keyUpdates:0 writeConflicts:0 numYields:13 nreturned:1000 reslen:41990 locks:{ Global: { acquireCount: { r: 28 } }, Database: { acquireCount: { r: 14 } }, Collection: { acquireCount: { r: 14 } } } protocol:op_query 200ms
2017-01-07T19:14:47.976-0500 I COMMAND  [conn17] command anil3.objects command: getMore { getMore: 22924441636, collection: "objects", batchSize: 1000 } cursorid:22924441636 keyUpdates:0 writeConflicts:0 numYields:12 nreturned:1000 reslen:41990 locks:{ Global: { acquireCount: { r: 26 } }, Database: { acquireCount: { r: 13 } }, Collection: { acquireCount: { r: 13 } } } protocol:op_query 185ms
    0
  • julianJ

    Hi there,

    Can you please provide the following information to help us debug?

    1. Server or client operating system (if applicable)
    2. NodeBB version and hash
      • To get the hash, run git rev-parse HEAD from the root of your NodeBB folder
    3. Any crash logs from your running NodeBB process.

    Thanks!

    Pramvir RatheeP 1 Reply
    1
  • Pramvir RatheeP

    @julian said in Visiting administrator users pages crashes the Nodebb - 503:

    Hi there,

    Can you please provide the following information to help us debug?

    1. Server or client operating system (if applicable)
    2. NodeBB version and hash
      • To get the hash, run git rev-parse HEAD from the root of your NodeBB folder
    3. Any crash logs from your running NodeBB process.

    Thanks!

    unbuntu 14 64 bit 8gb ram 4 cpus
    git rev-parse Head output - 376e0319280a986eedadc0127c4580c6f6610e41

    Type Ctrl-C to exit

9/1 00:19 [1738] - warn: [plugins] Unable to parse library for: nodebb-plugin-import-wordpress

9/1 00:19 [1738] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
  * nodebb-plugin-import
  * nodebb-plugin-import-wordpress

9/1 00:20 [1738] - info: NodeBB Ready
9/1 00:20 [1738] - info: Enabling 'trust proxy'
9/1 00:20 [1738] - info: NodeBB is now listening on: 0.0.0.0:4567
9/1 00:20 [1738] - info: [plugins/spam-be-gone] Settings loaded
    • Even after removing these two plugin, issue persists.
    • even after upgrading the nodebb to the latest 1.4.2
    • please note 55k posts are created by single user.
    • visiting the admin users url hangs nodebb.

    Here is log captured on starting.

    
Type Ctrl-C to exit

9/1 00:39 [1835] - info: NodeBB Ready
9/1 00:39 [1835] - info: Enabling 'trust proxy'
9/1 00:39 [1835] - info: NodeBB is now listening on: 0.0.0.0:4567
9/1 00:39 [1835] - info: [plugins/spam-be-gone] Settings loaded
Clustering enabled: Spinning up 1 process(es).

9/1 00:43 [1873] - info: Time: Mon Jan 09 2017 00:43:49 GMT-0500 (EST)
9/1 00:43 [1873] - info: Initializing NodeBB v1.0.3
9/1 00:43 [1873] - warn: You have no mongo password setup!
9/1 00:43 [1873] - info: [database] Checking database indices.
9/1 00:43 [1873] - error: Error: ENOENT, no such file or directory '../package.j                      son'
    at Object.fs.openSync (fs.js:432:18)
    at Object.fs.readFileSync (fs.js:286:15)
    at Object.readFileSync (/var/www/nodebb/forums/node_modules/nodebb-plugin-im                      port-wordpress/node_modules/fs-extra/node_modules/jsonfile/index.js:66:20)
    at Object.<anonymous> (/var/www/nodebb/forums/node_modules/nodebb-plugin-imp                      ort-wordpress/admin/index.js:5:11)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.Plugins.requireLibrary (/var/www/nodebb/forums/src/plugins.js:42:3                      3)
    at registerHooks (/var/www/nodebb/forums/src/plugins/load.js:88:13)
    at /var/www/nodebb/forums/src/plugins/load.js:31:6
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:718:13
    at async.forEachOf.async.eachOf (/var/www/nodebb/forums/node_modules/async/l                      ib/async.js:233:13)
    at _parallel (/var/www/nodebb/forums/node_modules/async/lib/async.js:717:9)
    at Object.async.parallel (/var/www/nodebb/forums/node_modules/async/lib/asyn                      c.js:731:9)
    at /var/www/nodebb/forums/src/plugins/load.js:29:10
    at /var/www/nodebb/forums/src/plugins/load.js:291:5
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:726:13
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:52:16
    at done (/var/www/nodebb/forums/node_modules/async/lib/async.js:246:17)
9/1 00:43 [1873] - warn: [plugins] Unable to parse library for: nodebb-plugin-im                      port-wordpress

9/1 00:43 [1873] - warn: [plugins/load] The following plugins may not be compati                      ble with your version of NodeBB. This may cause unintended behaviour or crashing                      . In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb re                      set -p PLUGINNAME` to disable it.
  * nodebb-plugin-import
  * nodebb-plugin-import-wordpress

9/1 00:44 [1873] - info: NodeBB Ready
9/1 00:44 [1873] - info: Enabling 'trust proxy'
9/1 00:44 [1873] - error:  Error: listen EADDRINUSE
    at errnoException (net.js:901:11)
    at Server._listen2 (net.js:1039:14)
    at listen (net.js:1061:10)
    at Server.listen (net.js:1135:5)
    at listen (/var/www/nodebb/forums/src/webserver.js:181:17)
    at /var/www/nodebb/forums/src/webserver.js:58:3
    at EventEmitter.<anonymous> (/var/www/nodebb/forums/src/emitter.js:17:5)
    at EventEmitter.emit (events.js:92:17)
    at /var/www/nodebb/forums/src/meta/css.js:117:14
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:726:13
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:52:16
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:269:32
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:44:16
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:723:17
    at /var/www/nodebb/forums/node_modules/async/lib/async.js:167:37
    at /var/www/nodebb/forums/src/meta/css.js:202:8
    at /var/www/nodebb/forums/src/meta/css.js:165:4
    at /var/www/nodebb/forums/node_modules/nodebb-plugin-import-wordpress/node_modules/fs-extra/node_modules/jsonfile/node_modules/graceful-fs/graceful-fs.js:43:10
    at /usr/lib/nodejs/graceful-fs/graceful-fs.js:103:5
    at /var/www/nodebb/forums/node_modules/less/node_modules/graceful-fs/graceful-fs.js:43:10
    at Object.oncomplete (fs.js:107:15)
9/1 00:44 [1873] - error: NodeBB address in use, exiting...
[cluster] Child Process (1873) has exited (code: 0, signal: null)

    Also post edit button hangs nodebb.

    0
  • julianJ

    Sounds like you may need to disable import-wordpress plugin.

    Pramvir RatheeP 1 Reply
    0
  • Pramvir RatheeP

    @julian
    it persists even after disabling it
    Yes the problem was with plugin, but my data did not got imported completly, after 57k topics now its impoting only 1 topic in 1 minute. What should i do now ?

    0

Suggested Topics

  • D

    How to call an API call from NodeBB theme?

    Unsolved Technical Support
    0 Votes
    4 Posts
    500 Views

    PitaJP

    @dogs themes are plugins, so everything you suggested can also be done in their theme.

  • B

    Write API - Adding users to groups

    Technical Support
    0 Votes
    1 Posts
    128 Views

    B

    Hello,

    I wonder if you can help.

    We are currently in the process of integrating NodeBB into our game server, when a player creates an organisation, adds members, deletes organisation, we are making the corresponding calls to NodeBB write api to do the above.

    We only want groups to be managed from game side rather than nodebb side (unless absolutely necessary by admins if there is an issue).

    Unfortunately, when we add a member to group, it gives them the group owner 'star' and allows them to manage the group on the forum.

    Is there a way to disable this?

    Thanks in advance.

  • emccaE

    Password will not save between user side and admin area.

    Technical Support
    0 Votes
    1 Posts
    318 Views

    emccaE

    I am using Heroku to host a nodeBB instance. When using the heroku supplied subdomain (and setting it in the config.json), everything works fine. I can log in as admin account, use admin GUI, and everything works well.

    When I set up custom domain (.me tld if that matters), configure it in Heroku, config.json, and DNS, I can get to the site, log in, but when I try to go to the admin area, it asks me to sign in. Once I sign in, it brings me back to the homepage (not admin GUI).

    I am using cloudflare for DNS and have tried with no plugins, vanilla install. I am using redis. I have tried both proxying through cloudflare "orange cloud" and not proxying "grey cloud" record.

    Any ideas?

  • ApxukocA

    "Recent cards" not working, NodeBB 1.4.5

    Solved Technical Support
    0 Votes
    3 Posts
    1918 Views

    ApxukocA

    @BuZz said in "Recent cards" not working, NodeBB 1.4.5:

    you need to use v 0.3.1 for nodebb v1.4.5
    npm i [email protected] --save

    Thanks!
    It is working!

  • SergioNGS

    Running NodeBB on IIS

    Technical Support
    0 Votes
    5 Posts
    3976 Views

    C

    Hi all,

    I realize this is an old topic, but given that I'm dealing with exactly the same problem, I figured it would be sensible to reply here. Essentially, I've followed the advice of @pichalite and created a simple IIS forward proxy for my NodeBB server. Unfortunately this solution does not yield the desired result, as many requests for resources are not being made to the correct directory - instead, requests are being made to the root level of the IIS Web server (e.g., GET http//website.ca/stylesheet.css?4210ebb0-9225-4237-b2ad-87d88b61756b), and not to the specified port where NodeBB is being hosted (e.g., http://website.ca:4567 or http://localhost:4567).

    Any ideas? I've played around with reverse proxies and outbound rules to route all outgoing traffic from http://localhost:4567 to the same URL I've specified for the proxy rule (e.g., http//website.ca/associates-hub) to no avail... If more info or screenshots are needed, they can be provided. I've been banging my head against the wall trying to cycle through all possible solutions to this problem. Any insight would be GREATLY appreciated.

    Thanks,

    Cam

Copyright © 2023 NodeBB | Contributors