too connection lost error

[sanatisharif]

only mobile users have such problem.

[julian]

Hm, that's interesting...

While your forum is running, can you run ./nodebb log and keep it running for awhile? It looks like NodeBB is crashing, and you are getting that MongoError whenever it happens.

Please confirm that this is always the same error you see.

[sanatisharif]

@julian I have this warning message

26/8 01:14:51 [22766] - warn: [nodebb-plugin-blog-comments] Origin (http://sanatisharif.ir) does not match hostUrls: sanatisharif.ir, orduetalaee.ir

and this error message:

26/8 01:00:00 [22765] - error:  MongoError: WiredTigerIndex::insert: key too large to index, failing  1581 { : "errors:404", : "/A%20%20%20%20%20%20%20%DA%A9%D8%A7%D8%B1%D9%86%D8%A7%D9%85%D9%87%20%D9%87%D8%A7%DB%8C%20%D8%A7%D8%B2%D9%85%D9%88%D9%86%D9%87%D8%A7%DB%8C%20%D8%A2%D8%..." }
    at Function.MongoError.create (/home/nodeBB/forum/node_modules/mongodb-core/lib/error.js:31:11)
    at /home/nodeBB/forum/node_modules/mongodb-core/lib/connection/pool.js:497:72
    at authenticateStragglers (/home/nodeBB/forum/node_modules/mongodb-core/lib/connection/pool.js:443:16)
    at null.messageHandler (/home/nodeBB/forum/node_modules/mongodb-core/lib/connection/pool.js:477:5)
    at Socket.<anonymous> (/home/nodeBB/forum/node_modules/mongodb-core/lib/connection/connection.js:321:22)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at TCP.onread (net.js:536:20)

But why only mobile users have such a problem(Connection lost) ??

[sanatisharif]

@julian new error after enabling a plugin (ignore-users pluging)

26/8 01:39:19 [30335] - error:  TypeError: callFn.apply is not a function
    at /home/nodeBB/forum/node_modules/async/dist/async.js:421:16
    at next (/home/nodeBB/forum/node_modules/async/dist/async.js:5278:29)
    at /home/nodeBB/forum/node_modules/async/dist/async.js:906:16
    at /home/nodeBB/forum/src/topics/unread.js:146:5
    at nextTask (/home/nodeBB/forum/node_modules/async/dist/async.js:5273:14)
    at next (/home/nodeBB/forum/node_modules/async/dist/async.js:5280:9)
    at /home/nodeBB/forum/node_modules/async/dist/async.js:906:16
    at fireFilterHook (/home/nodeBB/forum/src/plugins/hooks.js:112:11)
    at Object.Plugins.fireHook (/home/nodeBB/forum/src/plugins/hooks.js:96:4)
    at /home/nodeBB/forum/src/topics/unread.js:138:13
    at nextTask (/home/nodeBB/forum/node_modules/async/dist/async.js:5273:14)
    at next (/home/nodeBB/forum/node_modules/async/dist/async.js:5280:9)
    at /home/nodeBB/forum/node_modules/async/dist/async.js:906:16
    at /home/nodeBB/forum/node_modules/async/dist/async.js:421:16
    at next (/home/nodeBB/forum/node_modules/async/dist/async.js:5278:29)
    at /home/nodeBB/forum/node_modules/async/dist/async.js:906:16

[julian]

... why are you activating new plugins?

[sanatisharif]

@julian said in too connection lost error:

... why are you activating new plugins?

I disabled it again, we needed to nodebb-ignore-users plugin.

[PitaJ]

I assume that the reason he asked is because you were already having issues, so why introduce even more variables into the mix? Fix one issue before moving on to the next.

[sanatisharif]

@pitaj @julian

at the time, I unistalled it immediately and now I am waiting for you to say what to do.
Thanks a lot

[sanatisharif]

@julian
new error

28/8 02:35:04 [27587] - error:  TypeError: Cannot read property 'toString' of null
    at /home/nodeBB/forum/node_modules/nodebb-plugin-mentions/library.js:135:41
    at Array.filter (native)
    at /home/nodeBB/forum/node_modules/nodebb-plugin-mentions/library.js:128:83
    at Array.forEach (native)
    at /home/nodeBB/forum/node_modules/nodebb-plugin-mentions/library.js:127:33
    at /home/nodeBB/forum/node_modules/async/dist/async.js:3838:9
    at /home/nodeBB/forum/node_modules/async/dist/async.js:421:16
    at iterateeCallback (/home/nodeBB/forum/node_modules/async/dist/async.js:928:24)
    at /home/nodeBB/forum/node_modules/async/dist/async.js:906:16
    at /home/nodeBB/forum/node_modules/async/dist/async.js:3835:13
    at /home/nodeBB/forum/node_modules/nodebb-plugin-mentions/library.js:231:4
    at /home/nodeBB/forum/node_modules/async/dist/async.js:1074:9
    at /home/nodeBB/forum/node_modules/async/dist/async.js:421:16
    at iteratorCallback (/home/nodeBB/forum/node_modules/async/dist/async.js:998:13)
    at /home/nodeBB/forum/node_modules/async/dist/async.js:906:16
    at /home/nodeBB/forum/node_modules/async/dist/async.js:1071:13

[sanatisharif]

@julian
git head:
b2c16b2ba0aa0e91b55692fb59a809d8d6c551f9

[sanatisharif]

up..............

[julian]

Disable all plugins except those that NodeBB requires to run (mentions, markdown, composer-default, widget-essentials)

[sanatisharif]

@julian said in too connection lost error:

Disable all plugins except those that NodeBB requires to run (mentions, markdown, composer-default, widget-essentials)

we are on production mod not dev!!!
every thing was good about 3 month ago with this plugins that we are use:

1. nodebb-plugin-assign-newuser-to-group
2. nodebb-plugin-browsing-users
3. nodebb-plugin-composer-default
4. nodebb-plugin-emailer-mailgun
5. nodebb-plugin-emoji-apple
6. nodebb-plugin-emoji-extended
7. nodebb-plugin-emoji-one
8. nodebb-plugin-google-analytics
9. nodebb-plugin-katex
10. nodebb-plugin-markdown
11. nodebb-plugin-mega-colors
12. nodebb-plugin-mentions
13. nodebb-plugin-question-and-answer
14. nodebb-plugin-recent-cards
15. nodebb-plugin-shortcuts
16. nodebb-plugin-solr
17. nodebb-plugin-soundpack-default
18. nodebb-plugin-spam-be-gone
19. nodebb-plugin-sso-google
20. nodebb-plugin-sso-instagram
21. nodebb-plugin-topic-tags
22. nodebb-rewards-essentials
23. nodebb-theme-persona
24. nodebb-widget-essentials

[julian]

@sanatisharif it doesn't matter, you will want to set up a duplicate instance for these sorts of things before pushing to live.

You can set one up now for debug.

[sanatisharif]

I change this line in config.json fixes my problem

"port": [4567,4568,4569]

to

"port": "4567"

why we can't use nodebb in cluster mod ?

[julian]

There is no problem with using nodebb in a cluster setup, so this config change is likely unrelated

[pichalite]

@sanatisharif use "port": ["4567", "4568", "4569"]

[sanatisharif]

@pichalite said in too connection lost error:

@sanatisharif use "port": ["4567", "4568", "4569"]

in cluster mod I have lots of connection lost err in front end ( for mobile users )