Hi Boaz. I know this is an old thread but I can't find anything newer and it seems very related to this issue.
Is there documentation anywhere on how to script installation of the license initially? We have not yet run Marvel in production and we do not allow manual steps in our deployment process. We'd like to be able to deploy Marvel to a completely clean box and have the license already present at the end of the deploy. Can you point me to an example curl (dummy values, obviously)? On Monday, October 13, 2014 at 8:48:45 AM UTC-4, Boaz Leskes wrote: > > > .marvel-kibana now has a 'state-2' file inside it. and obv for now > since i didnt restart or do anything of that nature i am not asked for the > license details. I wonder if what I see is that .marvel-kibana is only > stored with one primary and one replica and when i reload the cluster > sometimes i happen to load the nodes first which dont have .marvel-kibana > so thats why i get that question about the license. > > The order in which you restart the nodes shouldn't really matter. Try > searching `GET .marvel-kibana/_search` and see that you get the license > document back? > > >Anyways, where would marvel should me how to add the license from the > command line? I'd like to see that cause I haven't run into such a prompt > yet. > > Marvel only shows it if it fails to save it to the cluster. If you want > the command, it's not a problem but please reach out off list with your > details. > > > > On Fri, Oct 10, 2014 at 9:13 PM, Daniel Schonfeld <downwi...@gmail.com > <javascript:>> wrote: > >> Boaz, >> >> .marvel-kibana now has a 'state-2' file inside it. and obv for now since >> i didnt restart or do anything of that nature i am not asked for the >> license details. I wonder if what I see is that .marvel-kibana is only >> stored with one primary and one replica and when i reload the cluster >> sometimes i happen to load the nodes first which dont have .marvel-kibana >> so thats why i get that question about the license. >> >> Anyways, where would marvel should me how to add the license from the >> command line? I'd like to see that cause I haven't run into such a prompt >> yet. >> >> Thanks! >> >> On Thursday, October 9, 2014 2:40:58 PM UTC-4, Boaz Leskes wrote: >>> >>> That's weird. You should for the content of the .marvel-kibana index. >>> That's where it stored when you enter your license info in the UI. >>> >>> Is the Marvel UI allowed to post back to ES? If that's blocked it may >>> explain things. Normally you will get a message from Marvel instructing you >>> how to add the license from the command line. >>> >>> >>> On 9 okt. 2014, at 6:06 p.m., Daniel Schonfeld <downwi...@gmail.com> >>> wrote: >>> >>> Hi Boaz, >>> >>> No the data folder is persisted. And with it i have all my cluster and >>> indices data... but for some reason marvel asks for the license/order >>> number again. >>> >>> Is there a file I can check for in my data folder? >>> >>> Thanks! >>> Daniel >>> >>> On Thursday, October 9, 2014 5:46:52 AM UTC-4, Boaz Leskes wrote: >>>> >>>> Hi Daniel, >>>> >>>> When you restart the cluster, do you also wipe all content? The marvel >>>> license should persist once entered but if you clean the data folder, that >>>> will go away as well. >>>> >>>> Cheers, >>>> Boaz >>>> >>>> On Wednesday, October 8, 2014 6:12:19 AM UTC+2, Daniel Schonfeld wrote: >>>>> >>>>> Hello, >>>>> >>>>> We have recently purchase our Marvel license, but everytime we restart >>>>> our cluster it asks us for the order number again. We use docker and so >>>>> our containers are immutable. >>>>> >>>>> Is there a file or something we can change in the filesystem that will >>>>> bake the license key into the container? >>>>> >>>>> Thanks! >>>>> >>>>> Daniel Schonfeld >>>>> >>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "elasticsearch" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>> topic/elasticsearch/UzvDQObssCM/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> elasticsearc...@googlegroups.com. >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/elasticsearch/e4db266f-03d7-40b6-ae77-29262e155492% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/elasticsearch/e4db266f-03d7-40b6-ae77-29262e155492%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "elasticsearch" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elasticsearch/UzvDQObssCM/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/666c540a-bd09-477d-8a56-d3970d3ecba7%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/666c540a-bd09-477d-8a56-d3970d3ecba7%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fa411f7d-4bef-4581-9ad4-bd053d5d9678%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
