There should not be anything extra necessary to work with Marvel. The 
browser prompted you for credentials and you entered admin credentials, 
correct?

On Thursday, April 2, 2015 at 12:39:03 PM UTC-4, BEN SALEM Omar wrote:
>
> Or not, that wenti as I'd like to go :))
> Here is the last remaining issue :
>
>
> ​
> ᐧ
>
> On Thu, Apr 2, 2015 at 6:32 PM, BEN SALEM Omar <[email protected] 
> <javascript:>> wrote:
>
>> That would be a problem ! 
>> Last question (as for now :p ), how to change the marvel timepicker? I 
>> can't see any indice of mine(as I already told you)
>> And hey, thank you for your cooperation Jay
>> ᐧ
>>
>> On Thu, Apr 2, 2015 at 6:26 PM, Jay Modi <[email protected] <javascript:>> 
>> wrote:
>>
>>> Hi Omar,
>>>
>>> I think you need to add "es.net.http.auth.user" and 
>>> "es.net.http.auth_password" as additional TBLPROPERTIES. You will need to 
>>> using elasticsearch Hadoop 2.1 beta 3 for this to work as far as I know.
>>>
>>> -Jay
>>>
>>> On Thursday, April 2, 2015 at 11:18:12 AM UTC-4, BEN SALEM Omar wrote:
>>>>
>>>> Hi Jay,
>>>> Now that I have shield in both ES and Kibana, and I want to load some 
>>>> data from my hadoop cluster to ES.
>>>> I usually do this : 
>>>> ....
>>>> ....
>>>> create external table es_word_count(word string, count int)
>>>> STORED BY 'org.elasticsearch.hadoop.hive.EsStorageHandler' 
>>>> TBLPROPERTIES('es.resource' = 'test/test',
>>>> 'es.nodes'='192.168.238.130:9200');
>>>>  
>>>> INSERT OVERWRITE TABLE es_word_count SELECT s.word, s.count  FROM 
>>>> word_counts1 s;
>>>>
>>>>
>>>> what should I do or add to access to my ES cluster as the esuser I've 
>>>> created? 
>>>> Thanks
>>>> ᐧ
>>>>
>>>> On Thu, Apr 2, 2015 at 1:08 PM, Jay Modi <[email protected]> wrote:
>>>>
>>>>> Hi Omar,
>>>>>
>>>>> Have you configured Kibana and Marvel to work with Shield? For Kibana 
>>>>> 4, please see http://www.elastic.co/guide/en/kibana/current/
>>>>> production.html#configuring-kibana-shield and http://www.elastic.co/
>>>>> guide/en/shield/current/_shield_with_kibana_4.html. For Marvel, see 
>>>>> http://www.elastic.co/guide/en/shield/current/marvel.html
>>>>>
>>>>> -Jay
>>>>>
>>>>> On Thursday, April 2, 2015 at 6:45:55 AM UTC-4, BEN SALEM Omar wrote:
>>>>>>
>>>>>> Hi Jay,
>>>>>>
>>>>>> I have a question, now that I've added an esuser as an admin, I can 
>>>>>> not run my Kibana anymore, 
>>>>>>
>>>>>>
>>>>>> Any idea on what to do to overcome this?
>>>>>>
>>>>>> Another basic question, when I open the marvel, it shows no indice 
>>>>>> because the sample of data I'm working with is in "2014", how to change 
>>>>>> my 
>>>>>> time span to see my indices again?
>>>>>> btwn, before I install the shield, Marvel used to recognize my 
>>>>>> timestamp by default
>>>>>>
>>>>>> ​
>>>>>> ᐧ
>>>>>> Thank you,
>>>>>> Omar,
>>>>>>
>>>>>> On Wed, Apr 1, 2015 at 8:22 PM, BEN SALEM Omar <[email protected]> 
>>>>>> wrote:
>>>>>>
>>>>>>> When I try to add an esuser and grant him a role:
>>>>>>>
>>>>>>> bin/shield/esusers useradd rdeniro -p taxidriver -r admin
>>>>>>>
>>>>>>> It says that there is an error in the "esusers" file in the 
>>>>>>> elef['$ES_INCLUDE"] line, I think the line 31 or 38, I forgot.
>>>>>>> In the line above, there is a $...done: which ends with ":", if you 
>>>>>>> change it to done; with ";" , the error doesn't show up anymore.
>>>>>>>
>>>>>>> I'm installing the whole thing in the Hortonworks Sandbox 2.0 vm
>>>>>>>
>>>>>>> On Wed, Apr 1, 2015 at 8:14 PM, Jay Modi <[email protected]> wrote:
>>>>>>>
>>>>>>>> I'm glad you were able to fix this issue. I have a few questions 
>>>>>>>> that may help us ensure this fix is pulled back into Shield. What OS 
>>>>>>>> and 
>>>>>>>> Shell are you using? Which line in the script did you change exactly? 
>>>>>>>> I'm 
>>>>>>>> looking at the script right now and I don't see any instance of "done:"
>>>>>>>>
>>>>>>>> Just an FYI, there is another way to handle the configuration 
>>>>>>>> directory issue that is documented in the configuring your environment 
>>>>>>>> section of the shield guide:
>>>>>>>> http://www.elastic.co/guide/en/shield/current/getting-starte
>>>>>>>> d.html#_configuring_your_environment
>>>>>>>>
>>>>>>>> On Wednesday, April 1, 2015 at 2:07:28 PM UTC-4, BEN SALEM Omar 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Ok, I've managed to solve my own problem.
>>>>>>>>>
>>>>>>>>> First of all things, if you want to just remove the shield plugin 
>>>>>>>>> run under the elasticsearch :
>>>>>>>>>
>>>>>>>>> $ bin/plugin --remove shield
>>>>>>>>>
>>>>>>>>> Now, to the syntax error in the elef line in the "esusers", 
>>>>>>>>> generally, when there is such an error, it's related to things before 
>>>>>>>>> that 
>>>>>>>>> line.
>>>>>>>>> In fact there was something like this : 
>>>>>>>>> $....done: 
>>>>>>>>> correction : 
>>>>>>>>> $....done;
>>>>>>>>>
>>>>>>>>> Now, we could add users within shield and grunt them the desired 
>>>>>>>>> role.
>>>>>>>>>
>>>>>>>>> But, even if I've done it, I couldn't access to my ES cluster with 
>>>>>>>>> the "new born user"; I think because my ES is running as a service 
>>>>>>>>> and not 
>>>>>>>>> starting with bin/elasticsearch, that lead to "misunderstanding."
>>>>>>>>>
>>>>>>>>> The solution I found was to transfer the /usr/share/elasticsearch/
>>>>>>>>> config/shield under /etc/elasticsearch
>>>>>>>>> $ln -s /usr/share/elasticsearch/config/shield/ /etc/elasticsearch
>>>>>>>>>
>>>>>>>>> And that was it ! 
>>>>>>>>> Hope that could be of a help for anyone else facing the same 
>>>>>>>>> problem !
>>>>>>>>>
>>>>>>>>> On Wednesday, April 1, 2015 at 5:28:14 PM UTC+2, BEN SALEM Omar 
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> I wanted to add authentication to my ES, thus I downloaded the 
>>>>>>>>>> shield :
>>>>>>>>>> https://www.elastic.co/downloads/shield
>>>>>>>>>>
>>>>>>>>>> Then I've tried to add a user to give him the admin role as it's 
>>>>>>>>>> mentionned here :
>>>>>>>>>> http://www.elastic.co/guide/en/shield/current/getting-starte
>>>>>>>>>> d.html
>>>>>>>>>> (I've added it with root, cause I start my es with root..)
>>>>>>>>>>
>>>>>>>>>> But when I try to do so, an error occure saying that there is a 
>>>>>>>>>> syntax error in the 38 line "the elef line" 
>>>>>>>>>> elef[$ES_INCLUDE] bla bla
>>>>>>>>>> I've tried many time : 
>>>>>>>>>> bin/shield/esusers useradd omar -p omar -r admin
>>>>>>>>>> bin/shield/esusers useradd esomar -p omar -r admin
>>>>>>>>>> bin/shield/esusers useradd es_omar -p omar -r admin
>>>>>>>>>> bin/shield/esusers useradd ES_omar -p omar -r admin
>>>>>>>>>> bin/shield/esusers useradd omar  -r admin
>>>>>>>>>> bin/shield/esusers useradd esomar  -r admin
>>>>>>>>>> bin/shield/esusers useradd es_omar  -r admin
>>>>>>>>>> bin/shield/esusers useradd ES_omar  -r admin
>>>>>>>>>>
>>>>>>>>>> But the same error kept on jumping ! 
>>>>>>>>>>
>>>>>>>>>> I said enough is enough and wanted to keep on doing wwhat I was 
>>>>>>>>>> doing, tried to run Kibana, and this is what happened !
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I've then tried to open my ES marvel plugin, but there is now an 
>>>>>>>>>> authentication box 
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ​
>>>>>>>>>> I've tried ALL the combinations above, but none of them seemed to 
>>>>>>>>>> work !!
>>>>>>>>>>
>>>>>>>>>> I'm really preoccupied by this note : 
>>>>>>>>>> To ensure that Elasticsearch can read the user and role 
>>>>>>>>>> information at startup, run esusers useradd as the same user you 
>>>>>>>>>> use to run Elasticsearch. Running the command as root or some other 
>>>>>>>>>> user 
>>>>>>>>>> will update the permissions for the users and users_roles files 
>>>>>>>>>> and prevent Elasticsearch from accessing them.
>>>>>>>>>>
>>>>>>>>>> The thing is that I start my es and kibana with the root..
>>>>>>>>>> Please HELP !! 
>>>>>>>>>>
>>>>>>>>>  -- 
>>>>>>>> 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/sEZpCO7E_B0/unsubscribe.
>>>>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>>>>> [email protected].
>>>>>>>> To view this discussion on the web visit 
>>>>>>>> https://groups.google.com/d/msgid/elasticsearch/9f0ebe63-cc8
>>>>>>>> 3-4c0b-8ee9-1514e51f77f6%40googlegroups.com 
>>>>>>>> <https://groups.google.com/d/msgid/elasticsearch/9f0ebe63-cc83-4c0b-8ee9-1514e51f77f6%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/sEZpCO7E_B0/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>> [email protected].
>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>> msgid/elasticsearch/35767d7f-45d7-4113-a478-499d44abcf38%
>>>>> 40googlegroups.com 
>>>>> <https://groups.google.com/d/msgid/elasticsearch/35767d7f-45d7-4113-a478-499d44abcf38%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/sEZpCO7E_B0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected] <javascript:>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/elasticsearch/579d2139-a75f-4c17-a03e-51e0f4830faf%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/elasticsearch/579d2139-a75f-4c17-a03e-51e0f4830faf%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/9622bb08-27c8-45b0-a892-b7412ca8fdff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to