-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use marija with elasticsearch 5.0.2 over ssh tunnel #42
Comments
|
@ckuethe did you use the latest commit? Or a release version? |
Just pushed a version that disables sniffing (this resolves the ip from the Elasticsearch nodes), causing probably your issue. |
Thanks for looking into this. Unfortunately even with the latest commit I still see this behavior... I'll clear my browser storage and do some more testing in the morning. |
I haven't tested it yet with ES 5 over a tunnel, but it works with older versions. Will setup some things to see if we can reproduce. Keep us posted, we're eager to solve this issue. |
Something I noticed before, sometimes there are too many fields in the index (we'll look into this issue), could you remove all but the relevant indexes, and retry refreshing the fields? |
There about 125 fields in each of the indices as I'm exploring syslog with a bunch of different hosts, log types, and fields courtesy of filebeat and logstash |
Could you export the mapping so we can try to reproduce the environment? |
thx, we'll look into this issue |
I'm connecting to a remote Elasticsearch 5.0.2 instance over an SSH tunnel; the tunnel works because:
Attempting to "use the refresh icon to refresh the list of available fields" or "add the fields [...] to use as nodes" gives an error
Error executing query: The connection was closed abnormally, e.g., without sending or receiving a Close control frame
In my terminal the following messages are visible:
Any suggestions on what to do next?
The text was updated successfully, but these errors were encountered: