@PitaJ
I use nginx just according to the documentation, its a fresh nodebb install from The documents, Brwsing with public/no admin accounts is fast, but with admin accounts it does not work, if click the admin tools under the topic, it gives error 503.

I recently successfully imported about Half million TOPICS = Posts in Nodebb Forum, As the nodebb forum goes bigger and Bigger these two very seviour issue start, can somebody tell me how to fix this.
No errors were found on forum startup, It occurs in every version i tried. As the forum goes heavy these two common things happen This is related to my last post.

• A single category having more than 50k topics start hanging, forum just frequently crashes, so i Devide the topics in two cats. It works okay till 30K. Removing the import plugin garbage also does not help.
• IF so many topics are imported, more than 150K the Browsing forum with any admin account is immposible.

Configuration of my server are
8GB RAM + 8GB SWAP
4 CPU'S
MONGODB 3.2.7
UBUNTU 14 64 BIT

No errors were found on forum startup, It occurs in every version i tried.
@julian @a_5mith @psychobunny @baris @pichalite @yariplus @PitaJ Please look at this issue.

Found the solution, importing too much topics in a single category hangs the nodebb, import some data than move it to some temporary category. Thasn import remaining data, meanwhile delete mongodb import Garbaze in using these mongo commands

db.objects.update({},{$unset: {_imported_tid:1}},{multi: true});
db.objects.update({},{$unset: {_imported_uid:1}},{multi: true});
db.objects.update({},{$unset: {_imported_cid:1}},{multi: true});
db.objects.update({},{$unset: {_imported_slug:1}},{multi: true});
db.objects.update({},{$unset: {_imported_locked:1}},{multi: true});
db.objects.update({},{$unset: {_imported_path:1}},{multi: true});
db.objects.update({},{$unset: {_imported_title:1}},{multi: true});
db.objects.update({},{$unset: {_imported_content:1}},{multi: true});
db.objects.update({},{$unset: {_imported_guest:1}},{multi: true});
db.objects.update({},{$unset: {_imported_ip:1}},{multi: true});
db.objects.update({},{$unset: {_imported_user_slug:1}},{multi: true});
db.objects.update({},{$unset: {_imported_user_path:1}},{multi: true});
db.objects.update({},{$unset: {_imported_category_path:1}},{multi: true});
db.objects.update({},{$unset: {_imported_category_slug:1}},{multi: true});

But keep in mind this will also delete the history of import will result in duplicate categories get imported or the posts, to prevent this keep writing post ids and category ids which you imported and delete them from the old database.

I recentrly Imported big data in one of my nodebb forum, but now it is very very very slow in importing, even after 8 GB ram and 4cpu's. I think i can make it faster if i purge all extra data created by import plugin, please note the button at bottom, "delete all changes what this plugin had made..." is not working.

@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 ?

@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.

@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

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 ?

@ludam So you tried nodebb + mongo on your huge community or not ? Because i want same, have a millions pages, 50 gb data community, do not know how much RAM mongo will require for this data.
Anyone here have any idea ?

@JaredBusch said in New install leaves me with session mismatch + invalid csrf:

proxy_set_header X-Forwarded-Proto $scheme;

 server {
    listen 80;

    server_name www.docfindy.com;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:4567/;
        proxy_redirect off;
        proxy_set_header X-Forwarded-Proto $scheme;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}
server {
    listen       80;
    server_name  docfindy.com;
    return       301 http://www.docfindy.com$request_uri;
}

I am using Mongo 3.2 and Nodebb 1.4.2, this is my nginx config file, session mismatch still present, plaase help.
@JaredBusch @julian