Member since
09-15-2015
457
Posts
507
Kudos Received
90
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
15473 | 11-01-2016 08:16 AM | |
10923 | 11-01-2016 07:45 AM | |
8288 | 10-25-2016 09:50 AM | |
1871 | 10-21-2016 03:50 AM | |
3649 | 10-14-2016 03:12 PM |
07-08-2016
06:54 PM
Awesome! Exactly what I was looking for at the moment 🙂
... View more
05-03-2016
06:35 AM
@Ramesh Mani Thanks for the help and fixing the issue! Enabling the plugin basically changed the owner of /opt/solr/server/solr-webapp/webapp/WEB-INF/classes to root:root, changing it back to solr:solr solved the problem 😉
... View more
05-03-2016
04:28 AM
You might want to look at this => https://github.com/abajwa-hw/logsearch-service Great tool for analyzing logs 🙂
... View more
04-27-2016
09:05 PM
1 Kudo
We have seen a similar error before, I believe you have enabled SSL for Ambari correct? If yes, please make sure you have setup your keystore correctly and re-run ambari-server setup-security
... View more
04-20-2016
06:01 AM
2181 is the Zookeeper port, make sure your Zookeeper ensemble is running and accessible. You might want to create a new question and describe your setup a bit more, it is probably easier to solve this problem then 🙂
... View more
04-19-2016
11:36 AM
By "enable kerberos" you mean, using Ambari to enable Kerberos security? At what step in the wizard do you see this error? In general: make sure your /etc/krb5.conf is still correct, especially the KDC host. Make sure your KDC host is running. Try to authenticate yourself on the node itself, basically running "kinit <principal>", afterwards "klist" should show a valid ticket. Is this a local MIT KDC or are you using an AD KDC?
... View more
04-18-2016
07:42 AM
@Anand Pandit what is the name of your cluster?
... View more
04-18-2016
07:41 AM
1 Kudo
@Saad Siddique check out this article https://community.hortonworks.com/articles/15159/securing-solr-collections-with-ranger-kerberos.html there is a section that covers the "Index locked for write" error. Basically you have to remove the write.lock file from the index folder and restart your solr instances
... View more
04-06-2016
03:14 PM
@Ramesh Mani I have checked your recommendation. Unfortunately it didnt help, any other ideas?
... View more
04-06-2016
11:05 AM
@Jagdish Saripella I looked into this and according to the logs, Kerberos /Spnego is the problem. Although the only feature you are missing if the test connection fails, is the lookup of solr Collections when you create policies. The plugin works even if the connection fails.
... View more