Elasticsearch Search for NodeBB

PitaJ

sanatisharif

@pitaj I have this error
Could not establish a connection to the Elasticsearch search engine.
My ElasticServer is public: http://5.239.244.126:8080/ and I set it in plugin setting page.

after restarting nodebb I have this error:

2017-12-27T21:30:01.480Z [29733] - error:  RangeError: Maximum call stack size exceeded
    at Function.EventEmitter.listenerCount (events.js:480:38)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:482:20)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:482:20)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:482:20)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:482:20)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:482:20)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:482:20)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:482:20)
    at Log.listenerCount (/home/Nodebb/forum/node_modules/elasticsearch/src/lib/log.js:68:25)
2017-12-27T21:30:01.480Z [29733] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
2017-12-27T21:30:01.481Z [29733] - info: [app] Database connection closed.
2017-12-27T21:30:01.482Z [29733] - info: [app] Web server closed to connections.
2017-12-27T21:30:01.482Z [29733] - info: [app] Shutdown complete.

sanatisharif

up .............
please help we are in production mod

PitaJ

You can disable the plugin by running

./nodebb reset -p search-elasticsearch

This will enable NodeBB to run assuming that the plugin error was preventing it.

sanatisharif

@pitaj said in Elasticsearch Search for NodeBB:

You can disable the plugin by running
./nodebb reset -p search-elasticsearch
This will enable NodeBB to run assuming that the plugin error was preventing it.

Can you fix nodebb-plugin-search-elasticsearch please ?
we have elastic search server and we want connect NodeBB to Elastic

julian

@sanatisharif I don't believe the plugin is maintained right now. The dbsearch plugin is our search engine of choice

Bri

Or the solr plugin.

@sanatisharif I really wouldn’t leave your cluster wide open like that, especially now that you’ve advertised it. Anyone can just come by and start using your server resources or delete your indexes. Do you at least have security on it (the shield plugin for Elasticsearch?)

sanatisharif

@bri said in Elasticsearch Search for NodeBB:

Or the solr plugin.

@sanatisharif I really wouldn’t leave your cluster wide open like that, especially now that you’ve advertised it. Anyone can just come by and start using your server resources or delete your indexes. Do you at least have security on it (the shield plugin for Elasticsearch?)

Elastic is on dev mod After it's done, we'll apply security to it.
Although we do not know how to do it at the moment.

We want enable elastic search on our forum, any body can help us?
Our forum language is persion( Farsi ) so dbsearch and apache search don't good at full text search on FARSI.

Atayz

@julian said in Elasticsearch Search for NodeBB:

@sanatisharif I don't believe the plugin is maintained right now. The dbsearch plugin is our search engine of choice

Yet the dbsearch doesn't support non-Roman alphabet languages for some reason

Juan G.

@atayz said:

Yet the dbsearch doesn't support non-Roman alphabet languages for some reason

You can try the NodeBB plugin for Solr search (open source), that supports a large number of languages, including Chinese, Japanese, Arabic, etc. See step by step details.