Dear searchguard developer：
I have been using searchguard and its security has brought me convenience. But there is a problem that has troubled me for a long time. We use the 2.4.1 version of elasticsearch, two nodes, configured as follows. Sometimes, the server will report to the searchguard not initialized problem after an accident due to a power failure or memory overflow. The execution of sgadmin.sh is not successful. I guess it is because the cluster status is red and cannot be recovered, but after the searchguard is removed, The cluster slowly resumes its green status. At this point, the searchguard plugin is moved in and it still cannot be restored…May I know what is the reason? Is there a solution? Look forward to your reply!
BTW,Due to business issues, unable to upgrade version。
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
both are 2.4.1
- Installed and used enterprise modules, if any
temporarily no, may use dlsfls module later
- JVM version and operating system version
1.8
searchguard not initialized
- Other installed Elasticsearch or Kibana plugins, if any
no
Can you share the elastic search logs. As in my production environment I too have used elasticsearch 2.4 and search guard both are working fine .
···
On Mon 4 Jun, 2018, 07:50 , 775878550@qq.com wrote:
Dear searchguard developer：
I have been using searchguard and its security has brought me convenience. But there is a problem that has troubled me for a long time. We use the 2.4.1 version of elasticsearch, two nodes, configured as follows. Sometimes, the server will report to the searchguard not initialized problem after an accident due to a power failure or memory overflow. The execution of sgadmin.sh is not successful. I guess it is because the cluster status is red and cannot be recovered, but after the searchguard is removed, The cluster slowly resumes its green status. At this point, the searchguard plugin is moved in and it still cannot be restored…May I know what is the reason? Is there a solution? Look forward to your reply!
BTW,Due to business issues, unable to upgrade version。
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
both are 2.4.1
- Installed and used enterprise modules, if any
temporarily no, may use dlsfls module later
- JVM version and operating system version
1.8
- Search Guard configuration files
- Elasticsearch log messages on debug level
searchguard not initialized
- Other installed Elasticsearch or Kibana plugins, if any
no
–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com.
To post to this group, send email to search-guard@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/67f8efd8-8bbc-40c4-9261-2654f6b21191%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
