Must I run sgadmin.sh after restart ES everytime?

#1

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

#2

This is strange. It should be enough to run the sgadmin script once. The Search Guard index gets populated and then replicated just like any other index.

Can you open an issue on our github page please, and give us some steps to reproduce this behaviour? Also, please state which version of ES (and thus SG) you are using. Are you seeing anything strange in the logfiles? And, can you please set the loglevel to DEBUG, then run sgadmin, and attach the logfile to the isuue?

To set the loglevel, add

com.floragunn: DEBUG

to

logging.yml

Thanks!

···

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

#3

I found the same problem:
"Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.

"

···

On Thu, Jul 21, 2016 at 5:41 PM, info@search-guard.com wrote:

This is strange. It should be enough to run the sgadmin script once. The Search Guard index gets populated and then replicated just like any other index.

Can you open an issue on our github page please, and give us some steps to reproduce this behaviour? Also, please state which version of ES (and thus SG) you are using. Are you seeing anything strange in the logfiles? And, can you please set the loglevel to DEBUG, then run sgadmin, and attach the logfile to the isuue?

https://github.com/floragunncom/search-guard/issues

To set the loglevel, add

com.floragunn: DEBUG

to

logging.yml

Thanks!

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

You received this message because you are subscribed to the Google Groups “Search Guard” 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/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

GDG Hangzhou | @zooboa
Email: zooboa@gmail.com
杭州GDG: www.hzgdg.org

#4

I get that too, but usually if I wait about a minute for the cluster to warm up it’ll work.

···

On Thu, Jul 21, 2016 at 3:46 AM, zooboa zooboa@gmail.com wrote:

I found the same problem:
"Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.

"

You received this message because you are subscribed to the Google Groups “Search Guard” 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/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

On Thu, Jul 21, 2016 at 5:41 PM, info@search-guard.com wrote:

This is strange. It should be enough to run the sgadmin script once. The Search Guard index gets populated and then replicated just like any other index.

Can you open an issue on our github page please, and give us some steps to reproduce this behaviour? Also, please state which version of ES (and thus SG) you are using. Are you seeing anything strange in the logfiles? And, can you please set the loglevel to DEBUG, then run sgadmin, and attach the logfile to the isuue?

https://github.com/floragunncom/search-guard/issues

To set the loglevel, add

com.floragunn: DEBUG

to

logging.yml

Thanks!

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

You received this message because you are subscribed to the Google Groups “Search Guard” 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/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


GDG Hangzhou | @zooboa
Email: zooboa@gmail.com
杭州GDG: www.hzgdg.org

#5

I did also notice that if I force the number of replicas to exist on EVERY node in the cluster this doesn’t happen.

···

On Thu, Jul 21, 2016 at 9:39 AM, Daniel Kasen djtecha@gmail.com wrote:

I get that too, but usually if I wait about a minute for the cluster to warm up it’ll work.

On Thu, Jul 21, 2016 at 3:46 AM, zooboa zooboa@gmail.com wrote:

I found the same problem:
"Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.

"

You received this message because you are subscribed to the Google Groups “Search Guard” 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/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

On Thu, Jul 21, 2016 at 5:41 PM, info@search-guard.com wrote:

This is strange. It should be enough to run the sgadmin script once. The Search Guard index gets populated and then replicated just like any other index.

Can you open an issue on our github page please, and give us some steps to reproduce this behaviour? Also, please state which version of ES (and thus SG) you are using. Are you seeing anything strange in the logfiles? And, can you please set the loglevel to DEBUG, then run sgadmin, and attach the logfile to the isuue?

https://github.com/floragunncom/search-guard/issues

To set the loglevel, add

com.floragunn: DEBUG

to

logging.yml

Thanks!

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

You received this message because you are subscribed to the Google Groups “Search Guard” 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/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


GDG Hangzhou | @zooboa
Email: zooboa@gmail.com
杭州GDG: www.hzgdg.org

#6

ok

在 2016年7月21日星期四 UTC+8下午5:41:04,in…@search-guard.com写道:

···

This is strange. It should be enough to run the sgadmin script once. The Search Guard index gets populated and then replicated just like any other index.

Can you open an issue on our github page please, and give us some steps to reproduce this behaviour? Also, please state which version of ES (and thus SG) you are using. Are you seeing anything strange in the logfiles? And, can you please set the loglevel to DEBUG, then run sgadmin, and attach the logfile to the isuue?

https://github.com/floragunncom/search-guard/issues

To set the loglevel, add

com.floragunn: DEBUG

to

logging.yml

Thanks!

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

#7

[2016-07-22 10:05:44,373][DEBUG][com.floragunn.searchguard.configuration.SearchGuardIndexSearcherWrapperModule] FLS/DLS not enabled

[2016-07-22 10:05:44,408][DEBUG][com.floragunn.searchguard.configuration.SearchGuardIndexSearcherWrapperModule] FLS/DLS not enabled

[2016-07-22 10:05:44,906][DEBUG][com.floragunn.searchguard.configuration.SearchGuardIndexSearcherWrapperModule] FLS/DLS not enabled

[2016-07-22 10:05:44,952][DEBUG][com.floragunn.searchguard.configuration.SearchGuardIndexSearcherWrapperModule] FLS/DLS not enabled

[2016-07-22 10:07:40,410][ERROR][com.floragunn.searchguard.auth.BackendRegistry] Not yet initialized

[2016-07-22 10:13:09,239][ERROR][com.floragunn.searchguard.auth.BackendRegistry] Not yet initialized

see the last two log, it didn’t work after about 6 minutes. i’m crazy.

在 2016年7月22日星期五 UTC+8上午12:39:43,djtecha写道:

···

I get that too, but usually if I wait about a minute for the cluster to warm up it’ll work.

On Thu, Jul 21, 2016 at 3:46 AM, zooboa zoo...@gmail.com wrote:

I found the same problem:
"Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.

"

On Thu, Jul 21, 2016 at 5:41 PM, in...@search-guard.com wrote:

This is strange. It should be enough to run the sgadmin script once. The Search Guard index gets populated and then replicated just like any other index.

Can you open an issue on our github page please, and give us some steps to reproduce this behaviour? Also, please state which version of ES (and thus SG) you are using. Are you seeing anything strange in the logfiles? And, can you please set the loglevel to DEBUG, then run sgadmin, and attach the logfile to the isuue?

https://github.com/floragunncom/search-guard/issues

To set the loglevel, add

com.floragunn: DEBUG

to

logging.yml

Thanks!

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

You received this message because you are subscribed to the Google Groups “Search Guard” group.

To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.

To post to this group, send email to search...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


GDG Hangzhou | @zooboa
Email: zoo...@gmail.com
杭州GDG: www.hzgdg.org

You received this message because you are subscribed to the Google Groups “Search Guard” group.

To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.

To post to this group, send email to search...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

#8

i tried, but it doesn’t work.

在 2016年7月22日星期五 UTC+8上午12:47:38,djtecha写道:

···

I did also notice that if I force the number of replicas to exist on EVERY node in the cluster this doesn’t happen.

On Thu, Jul 21, 2016 at 9:39 AM, Daniel Kasen djt...@gmail.com wrote:

I get that too, but usually if I wait about a minute for the cluster to warm up it’ll work.

On Thu, Jul 21, 2016 at 3:46 AM, zooboa zoo...@gmail.com wrote:

I found the same problem:
"Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.

"

On Thu, Jul 21, 2016 at 5:41 PM, in...@search-guard.com wrote:

This is strange. It should be enough to run the sgadmin script once. The Search Guard index gets populated and then replicated just like any other index.

Can you open an issue on our github page please, and give us some steps to reproduce this behaviour? Also, please state which version of ES (and thus SG) you are using. Are you seeing anything strange in the logfiles? And, can you please set the loglevel to DEBUG, then run sgadmin, and attach the logfile to the isuue?

https://github.com/floragunncom/search-guard/issues

To set the loglevel, add

com.floragunn: DEBUG

to

logging.yml

Thanks!

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

You received this message because you are subscribed to the Google Groups “Search Guard” group.

To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.

To post to this group, send email to search...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


GDG Hangzhou | @zooboa
Email: zoo...@gmail.com
杭州GDG: www.hzgdg.org

You received this message because you are subscribed to the Google Groups “Search Guard” group.

To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.

To post to this group, send email to search...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

#9

see https://github.com/floragunncom/search-guard/issues/182

···

On Thursday, 21 July 2016 11:34:38 UTC+2, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

#10

With ES v2.4.1 and corresponding SG+SSL and SG versions, the cluster just recovers after a few iterations, without having to rerun sgadmin.sh

···

On Thursday, July 21, 2016 at 5:34:38 AM UTC-4, Clifford wrote:

Everytime I restart ES node, the api returns “Search Guard not initialized(SG11)”. it works after i run sgadmin.sh.
I always thought that the script run only one time after SG is installed.
Is there some setting can do this automatically? Because i don’t know when the node initializes ok and joins the cluster.

#11

We have the same issue: SG11 after restart, and we are unsure if we should run sgadmin.sh or just wait. Is it expected that the cluster comes back with an SG11 after restart and then initializes itself? And is there a way to tell if it is working on it?

#12

We will look into this …

#13

We will shortly release v25.1 where this issue should be fixed …

1 Like
#14

We released v25.1 yesterday. This should fix any issues. See https://docs.search-guard.com/6.x-25/changelog-searchguard-6-x-25_1