You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by dlyle65535 <gi...@git.apache.org> on 2016/10/03 19:17:17 UTC
[GitHub] incubator-metron pull request #288: METRON-480: Kibana 4.5+ Requires http.co...
GitHub user dlyle65535 opened a pull request:
https://github.com/apache/incubator-metron/pull/288
METRON-480: Kibana 4.5+ Requires http.cors.enabled set to false on ES
Tested with simulated Docker cluster.
Installed Elasticsearch and Kibana services together post-install and verified Kibana could initialize.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dlyle65535/incubator-metron METRON-480
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/288.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #288
----
commit 83a8a4e6c304bd715fd336854e17c6a6cf8d4b17
Author: David Lyle <dl...@gmail.com>
Date: 2016-10-03T15:45:28Z
METRON-480: Kibana 4.5+ Requires http.cors.enabled set to false on ES
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/288
Ah, chased down the JIRA. Looks like it is.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by anandsubbu <gi...@git.apache.org>.
Github user anandsubbu commented on the issue:
https://github.com/apache/incubator-metron/pull/288
I have verified this fix on a 12-node openstack cluster.
Generated a fresh set of RPMs with the fix provided in this pull request, and setup the cluster afresh. After the installation completes, the Kibana dashboard comes up fine.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
Re: [GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+
Requires http.cors.enab...
Posted by David Lyle <dl...@gmail.com>.
Got it. This will keep that from happening. If you don't want to
reprovision- add a property http.cors.enabled. The display name and the
actual property name are different.
-D...
On Thu, Oct 6, 2016 at 4:07 PM, nickwallen <gi...@git.apache.org> wrote:
> Github user nickwallen commented on the issue:
>
> https://github.com/apache/incubator-metron/pull/288
>
> I am seeing this on a cluster that I deployed with the mpack from
> 'master'. ES is happy and excited to play. When I hit up Kibana I get
> this error.
>
> ```
> Courier Fetch Error: unhandled courier request error: Authorization
> Exception
> Version: 4.5.1
> Build: 9892
> ```
>
> In researching the error, I ran across this on [Github/Kibana](
> https://github.com/elastic/kibana/issues/6719) which refers to the
> `http.cors.enabled` setting. I remembered you opening this PR and thought
> it might connect.
>
> Now I'm confused though because in this PR you set a
> `http_cors_enabled` variable which uses underlines versus
> `http.cors.enabled` which is mentioned in the link above.
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastructure@apache.org or file a JIRA ticket
> with INFRA.
> ---
>
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/288
I am seeing this on a cluster that I deployed with the mpack from 'master'. ES is happy and excited to play. When I hit up Kibana I get this error.
```
Courier Fetch Error: unhandled courier request error: Authorization Exception
Version: 4.5.1
Build: 9892
```
In researching the error, I ran across this on [Github/Kibana](https://github.com/elastic/kibana/issues/6719) which refers to the `http.cors.enabled` setting. I remembered you opening this PR and thought it might connect.
Now I'm confused though because in this PR you set a `http_cors_enabled` variable which uses underlines versus `http.cors.enabled` which is mentioned in the link above.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron pull request #288: METRON-480: Kibana 4.5+ Requires http.co...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/288
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by dlyle65535 <gi...@git.apache.org>.
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/288
Darn. Can't edit on the phone. Are you seeing this on an existing cluster? A default ES instance should default to false.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/288
Was this intended to fix the following error thrown by Kibana when it tries to talk to Elasticsearch?
```
Courier Fetch Error: unhandled courier request error: Authorization Exception
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by dlyle65535 <gi...@git.apache.org>.
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/288
No, it defaults to false, so no user action is required.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/288
+1 This PR did fix the issue that I was seeing. Tested on a live cluster.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/288
If I manually login to each ES master and remove the `http.cors.enabled = true` from `/etc/elasticsearch/elasticsearch.yml` then restart ES, I am able to connect to ES with Kibana.
Of course, once Ambari gets involved it undoes my manual edit. I have not yet figured out how to 'unset' this through Ambari yet.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-metron issue #288: METRON-480: Kibana 4.5+ Requires http.cors.enab...
Posted by nickwallen <gi...@git.apache.org>.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/288
To fix this using Ambari on an existing ES cluster would I just go to...
Elasticsearch -> Configs -> Custom elastic_site -> Add Property -> key=http_cors_enabled, value=false?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---