# Must I run sgadmin.sh after restart ES everytime? **URL:** \ **Category:** Search Guard\ **Created:** [July 21, 2016, 9:34am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240 "2016-07-21T09:34:38Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Clifford](https://avatars.discourse-cdn.com/v4/letter/c/e56c9b/32.png) [@Clifford](https://forum.search-guard.com/u/Clifford)\ **Post date:** [July 21, 2016, 9:34am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/1 "2016-07-21T09:34:38Z")
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. ---
**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\ **Post date:** [July 21, 2016, 9:41am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/2 "2016-07-21T09:41:04Z")
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? > **[Issues · floragunncom/search-guard](https://github.com/floragunncom/search-guard/issues)** > > Search Guard Plugin - Security for Elasticsearch. Contribute to floragunncom/search-guard development by creating an account on GitHub. 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. ---
**Author:** ![zooboa](https://avatars.discourse-cdn.com/v4/letter/z/898d66/32.png) [@zooboa](https://forum.search-guard.com/u/zooboa)\ **Post date:** [July 21, 2016, 10:46am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/3 "2016-07-21T10:46:11Z")
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](mailto: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](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](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > – > > GDG Hangzhou | @zooboa > Email: [zooboa@gmail.com](mailto:zooboa@gmail.com) > 杭州GDG: [www.hzgdg.org](http://www.hzgdg.org) ---
**Author:** ![Daniel\_Kasen](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@Daniel\_Kasen](https://forum.search-guard.com/u/Daniel_Kasen)\ **Post date:** [July 21, 2016, 4:39pm UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/4 "2016-07-21T16:39:42Z")
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](mailto: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](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > On Thu, Jul 21, 2016 at 5:41 PM, [info@search-guard.com](mailto: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](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](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > – > GDG Hangzhou | @zooboa > Email: [zooboa@gmail.com](mailto:zooboa@gmail.com) > 杭州GDG: [www.hzgdg.org](http://www.hzgdg.org) ---
**Author:** ![Daniel\_Kasen](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@Daniel\_Kasen](https://forum.search-guard.com/u/Daniel_Kasen)\ **Post date:** [July 21, 2016, 4:47pm UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/5 "2016-07-21T16:47:36Z")
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](mailto: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](mailto: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](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > On Thu, Jul 21, 2016 at 5:41 PM, [info@search-guard.com](mailto: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](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](mailto:search-guard+unsubscribe@googlegroups.com). > > > > To post to this group, send email to [search-guard@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > – > GDG Hangzhou | @zooboa > Email: [zooboa@gmail.com](mailto:zooboa@gmail.com) > 杭州GDG: [www.hzgdg.org](http://www.hzgdg.org) ---
**Author:** ![Clifford](https://avatars.discourse-cdn.com/v4/letter/c/e56c9b/32.png) [@Clifford](https://forum.search-guard.com/u/Clifford)\ **Post date:** [July 22, 2016, 2:30am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/6 "2016-07-22T02:30:40Z")
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](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. ---
**Author:** ![Clifford](https://avatars.discourse-cdn.com/v4/letter/c/e56c9b/32.png) [@Clifford](https://forum.search-guard.com/u/Clifford)\ **Post date:** [July 22, 2016, 2:36am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/7 "2016-07-22T02:36:52Z")
[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](mailto: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](mailto: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](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](mailto:search-guard...@googlegroups.com). > > > > > > > > To post to this group, send email to [search...@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > – > > > GDG Hangzhou | @zooboa > > > Email: [zoo...@gmail.com](mailto:zoo...@gmail.com) > > > 杭州GDG: [www.hzgdg.org](http://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](mailto:search-guard...@googlegroups.com). > > > > > > To post to this group, send email to [search...@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com?utm_medium=email&utm_source=footer). > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > ---
**Author:** ![Clifford](https://avatars.discourse-cdn.com/v4/letter/c/e56c9b/32.png) [@Clifford](https://forum.search-guard.com/u/Clifford)\ **Post date:** [July 22, 2016, 2:43am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/8 "2016-07-22T02:43:03Z")
[![](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/2X/7/70518f77ee5aada98802a1b607525289383046af.png)](https://lh3.googleusercontent.com/-e8etF04kkAk/V5GHXES6Y7I/AAAAAAAAAAM/eli_Fdh9BzU3og6cN7ykWH0JPpM3WG_7wCLcB/s1600/QQ%25E6%2588%25AA%25E5%259B%25BE20160722103858.png) 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](mailto: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](mailto: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](mailto: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](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](mailto:search-guard...@googlegroups.com). > > > > > > > > > > To post to this group, send email to [search...@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/2170c993-c7fb-4010-b586-b70c866d0770%40googlegroups.com?utm_medium=email&utm_source=footer). > > > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > > > > – > > > > GDG Hangzhou | @zooboa > > > > Email: [zoo...@gmail.com](mailto:zoo...@gmail.com) > > > > 杭州GDG: [www.hzgdg.org](http://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](mailto:search-guard...@googlegroups.com). > > > > > > > > To post to this group, send email to [search...@googlegroups.com](mailto: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](https://groups.google.com/d/msgid/search-guard/CAJOEc444oL9G%2Bf3eFFXA2x4vwGs%2B5_-O8bc%2B3atMa91uBdWgzQ%40mail.gmail.com?utm_medium=email&utm_source=footer). > > > > > > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > > > > > > ---
**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\ **Post date:** [July 28, 2016, 8:28pm UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/9 "2016-07-28T20:28:54Z")
see [https://github.com/floragunncom/search-guard/issues/182](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. ---
**Author:** ![ZillaYT](https://avatars.discourse-cdn.com/v4/letter/z/4da419/32.png) [@ZillaYT](https://forum.search-guard.com/u/ZillaYT)\ **Post date:** [November 3, 2016, 9:29pm UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/10 "2016-11-03T21:29:38Z")
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. ---
**Author:** ![ynux](https://avatars.discourse-cdn.com/v4/letter/y/919ad9/32.png) [@ynux](https://forum.search-guard.com/u/ynux)\ **Post date:** [April 26, 2019, 4:23pm UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/11 "2019-04-26T16:23:25Z")
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? ---
**Author:** ![cstaley](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/cstaley/32/463_2.png) [@cstaley](https://forum.search-guard.com/u/cstaley)\ **Post date:** [April 30, 2019, 8:56pm UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/12 "2019-04-30T20:56:39Z")
We will look into this … ---
**Author:** ![cstaley](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/cstaley/32/463_2.png) [@cstaley](https://forum.search-guard.com/u/cstaley)\ **Post date:** [May 8, 2019, 11:34am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/13 "2019-05-08T11:34:40Z")
We will shortly release v25.1 where this issue should be fixed … ---
**Author:** ![cstaley](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/cstaley/32/463_2.png) [@cstaley](https://forum.search-guard.com/u/cstaley)\ **Post date:** [May 9, 2019, 11:07am UTC](https://forum.search-guard.com/t/must-i-run-sgadmin-sh-after-restart-es-everytime/240/14 "2019-05-09T11:07:36Z")
We released v25.1 yesterday. This should fix any issues. See [Search Guard 6.x-25.1 | Elasticsearch Security | Search Guard](https://docs.search-guard.com/6.x-25/changelog-searchguard-6-x-25_1)