ES - MARVEL 2.0 or 2.1 NOT working under OS WINDOWS 10 due to BOOTSTRAP


#1

ES - MARVEL will not work under WIN10 OS due to error / warning sounded in the first phrase found in the log:
"
[2015-11-28 09:45:48,879][WARN ][bootstrap ] unable to install syscall filter: syscall filtering not supported for OS: 'Windows 10'
"
Is there a fix or workaround?
Thanks.


(David Pilato) #2

It's only a warn. Why do you think it does not work?


#3

Why: because I have never successfully run ES-Marvel 2.0 or 2.1 on my win10 system. But, ES-Marvel 1.7.2 runs just fine. When I inspected the different logs, that was the first thing that was different.
Here is the rest of the log for ES-Marvel 2.1 (truncated due to posting limitations):

[2015-11-28 09:45:48,879][WARN ][bootstrap ] unable to install syscall filter: syscall filtering not supported for OS: 'Windows 10'
[2015-11-28 09:45:49,004][INFO ][node ] [OHNode-1] version[2.1.0], pid[2648], build[72cd1f1/2015-11-18T22:40:03Z]
[2015-11-28 09:45:49,004][INFO ][node ] [OHNode-1] initializing ...
[2015-11-28 09:45:49,129][INFO ][plugins ] [OHNode-1] loaded [license, marvel-agent], sites []
[2015-11-28 09:45:49,144][INFO ][env ] [OHNode-1] using [1] data paths, mounts [[SSD4 (I:)]], net usable_space [446.9gb], net total_space [447.1gb], spins? [unknown], types [NTFS]
[2015-11-28 09:45:50,187][INFO ][node ] [OHNode-1] initialized
[2015-11-28 09:45:50,203][INFO ][node ] [OHNode-1] starting ...
[2015-11-28 09:45:50,328][INFO ][transport ] [OHNode-1] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}, {[::1]:9300}
[2015-11-28 09:45:50,344][INFO ][discovery ] [OHNode-1] OHN_ES/2s5zSEnCTAO8teWZSNxboA
[2015-11-28 09:45:54,422][INFO ][cluster.service ] [OHNode-1] new_master {OHNode-1}{2s5zSEnCTAO8teWZSNxboA}{127.0.0.1}{127.0.0.1:9300}{rack=n1}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2015-11-28 09:45:54,547][INFO ][http ] [OHNode-1] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}, {[::1]:9200}
[2015-11-28 09:45:54,547][INFO ][node ] [OHNode-1] started
[2015-11-28 09:45:54,610][INFO ][license.plugin.core ] [OHNode-1] license [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] - valid
[2015-11-28 09:45:54,672][INFO ][gateway ] [OHNode-1] recovered [5] indices into cluster_state
[2015-11-28 09:45:54,972][WARN ][index.translog ] [OHNode-1] [.marvel-es-2015.11.28][0] failed to delete temp file I:\ES\OHN_ES\nodes\0\indices.marvel-es-2015.11.28\0\translog\translog-299723250838168587.tlog
java.nio.file.NoSuchFileException: I:\ES\OHN_ES\nodes\0\indices.marvel-es-2015.11.28\0\translog\translog-299723250838168587.tlog
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
...
at org.elasticsearch.index.shard.StoreRecoveryService.recoverFromStore(StoreRecoveryService.java:245)
at org.elasticsearch.index.shard.StoreRecoveryService.access$100(StoreRecoveryService.java:56)
at org.elasticsearch.index.shard.StoreRecoveryService$1.run(StoreRecoveryService.java:129)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[2015-11-28 09:45:54,972][WARN ][index.translog ] [OHNode-1] [kib_default.kibana][0] failed to delete temp file I:\ES\OHN_ES\nodes\0\indices\kib_default.kibana\0\translog\translog-3855994493814347510.tlog
java.nio.file.NoSuchFileException: I:\ES\OHN_ES\nodes\0\indices\kib_default.kibana\0\translog\translog-3855994493814347510.tlog
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)

[2015-11-28 09:45:54,972][WARN ][index.translog ] [OHNode-1] [.marvel-es-data][0] failed to delete temp file I:\ES\OHN_ES\nodes\0\indices.marvel-es-data\0\translog\translog-577979268686346510.tlog
java.nio.file.NoSuchFileException: I:\ES\OHN_ES\nodes\0\indices.marvel-es-data\0\translog\translog-577979268686346510.tlog
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)


(David Pilato) #4

Nothing seems related to marvel here. Why do you think Marvel is not running?


#5

ES-Marvel 2.1 (same for 2.0):
After running Elasticsearch.bat (and getting the log I posted):
On the browser, communicate with ES (all browsers: Firefox, Edge, Chrome) with: http://localhost:9200
Result:
{
"name" : "OHNode-1",
"cluster_name" : "OHN_ES",
"version" : {
"number" : "2.1.0",
"build_hash" : "72cd1f1a3eee09505e036106146dc1949dc5dc87",
"build_timestamp" : "2015-11-18T22:40:03Z",
"build_snapshot" : false,
"lucene_version" : "5.3.1"
},
"tagline" : "You Know, for Search"
}

So, we know the ES is connected and we are communicating with it.

Try to add Marvel with: http://localhost:9200/_plugin/Marvel
Result: HTTP 404 error

Try again extending to SENSE with: http://localhost:9200/_plugin/Marvel/sense OR http://localhost:9200/_plugin/Marvel/sense.html
Result: HTTP 404 error

Changing cases with Marvel and or Sense does not make any difference. Using any of the above mentioned browsers gets the same 404 result.

That's why I think it is a Marvel problem. I could be wrong -- in fact I am certain of it. But the important thing is a solution.
I appreciate your attention, interest and efforts.


(David Pilato) #6

This is totally expected. Marvel totally changed in 2.0. You need to read the doc.

You basically have to deploy a Kibana plugin.


#7

What "is totally expected": that I can't run ES-marvel-sense without Kibana? If that is so, perhaps that's first thing that should have been said about ES 2.0 and 2.1. I have in fact scoured the documentation provided and finding no answers, I turn to this forum.

In any case, even Kibana will not find Marvel as one of the plugins; I do have the latest Kibana installed and it is "healthy"; I can communicate with it alright on port 5601. Right now, I can't get past the "index profile" requirement; how do I get an index profile in ES 2.0 when I can't get ES- Marvel - Sense up and running?

If you have successfully installed and run ES-Marvel on WIN10, please let me know what / how you did it.
Otherwise, if there is something I have missed in the reference you pointed out, please be kind enough to specifically point it out.

Thanks.


(David Pilato) #8

Did you read:

If there anything wrong when you install?


#9

Thank you very much, David, for the links.
I followed all the instructions:

  1. I am up and running, thanks to you. Yes, indeed, something changed dramatically with ES 2.0 and above. It now appears that Kibana is the motherbase, to which ES and Marvel are "attached" and Sense, too. So I am running all the latest versions on WIN10!

  2. How does Logstash get into the picture? Earlier, I did an installation but I obviously I don't find it as one of the Kibana apps. Is there another link you can direct me to so that I can install and configure it correctly (under Kibana?)

I don't know where you find the patience to do this; the least I can say is that I really do appreciate you.


(David Pilato) #10

There is no logstash app for Kibana.


#11

Thanks!


(system) #12