Hi, I did a clean install windows elastic 5.4.3 starts just dandy (so did Kibana start ok). Then I installed x-pack and ES wont start. Then I uninstall x-pack and all good again. So many messages but kinda looks like the inability to find a log is where it's breaking? Lots of messages around 1.8.0_131 Java - seems like a culprit?
Keen to get x-pack in Kibana working tons of disk (Alienware lappy - Win 7 Ultimate Sp1, 64 bit, 16GB ram).
Base install with 4 minimal YML parm changes. I have a full log, but too verbose to include all (I can email a helper with full logs)
cluster.name: ek-application
node.name: "ek.data"
path.data: ../ekdata
path.logs: ../ekdata
C:\Users\EK>java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
-
inital good startup
C:\EKDev\es5.4.3>bin\elasticsearch
<snip - start up stuff removed for brevity>
[2017-06-30T15:18:43,552][INFO ][o.e.h.n.Netty4HttpServerTransport] [ek.data] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}, {[::1]:9200}
[2017-06-30T15:18:43,559][INFO ][o.e.n.Node ] [ek.data] started
[2017-06-30T15:19:01,271][INFO ][o.e.n.Node ] [ek.data] closed
Terminate batch job (Y/N)? y
...all good... -
then x-pack
C:\EKDev\es5.4.3>bin\elasticsearch-plugin install x-pack
-> Downloading x-pack from elastic
[=================================================] 100%
Continue with installation? [y/N]y
-> Installed x-pack
...still all good... -
then elastic breaks (for brevity I've removed lines that look ok, and duplicate errors. hoping I don't remove a useful line?)
C:\EKDev\es5.4.3>bin\elasticsearch
[2017-06-30T15:21:41,309][INFO ][o.e.n.Node ] [ek.data] initializing ...
[2017-06-30T15:21:41,560][INFO ][o.e.e.NodeEnvironment ] [ek.data] using [1] data paths, mounts [[OS (C:)]], net usable_space [393.6gb], net total_space [524.9gb], spins? [unknown], types [NTFS]
[2017-06-30T15:21:41,562][INFO ][o.e.e.NodeEnvironment ] [ek.data] heap size [1.9gb], compressed ordinary object pointers [true]
[2017-06-30T15:21:41,624][INFO ][o.e.n.Node] [ek.data] node name [ek.data], node ID [QDFe7VyaSa-zZxjtlgeP6Q]
[2017-06-30T15:21:41,626][INFO ][o.e.n.Node ] [ek.data] version[5.4.3], pid[8340], build[eed30a8/2017-06-22T00:34:03.743Z], OS[Windows 7/6.1/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_131/25.131-b11]
[2017-06-30T15:21:41,628][INFO ][o.e.n.Node ] [ek.data] JVM arguments [-Xms2g, -Xmx2g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:
+UseCMSInitiatingOccupancyOnly, -XX:+DisableExplicitGC, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -
Djdk.io.permissionsUseCanonicalPath=true, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -
Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j.skipJansi=true, -XX:+HeapDumpOnOutO
fMemoryError, -Delasticsearch, -Des.path.home=C:\EKDev\es5.4.3]
[2017-06-30T15:21:44,774][INFO ][o.e.p.PluginsService] [ek.data] loaded plugin [x-pack]
[2017-06-30T15:21:49,394][DEBUG][o.e.a.ActionModule] Using REST wrapper from plugin org.elasticsearch.xpack.XPackPlugin
[2017-06-30T15:22:00,219][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [ek.data] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: ElasticsearchException[Failed to create native process factories for Machine Learning]; nested: FileNotFoundException[\.\pipe\controller_log_8340 (The system cannot find the file specified)];
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:127) ~[elasticsearch-5.4.3.jar:5.4.3]
Caused by: org.elasticsearch.ElasticsearchException: Failed to create native process factories for Machine Learning
at org.elasticsearch.xpack.ml.MachineLearning.createComponents(MachineLearning.java:290) ~[?:?]
at org.elasticsearch.xpack.XPackPlugin.createComponents(XPackPlugin.java:288) ~[?:?]
at org.elasticsearch.node.Node.lambda$new$7(Node.java:411) ~[elasticsearch-5.4.3.jar:5.4.3]
at java.util.stream.ReferencePipeline$7$1.accept(Unknown Source) ~[?:1.8.0_131]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) ~[elasticsearch-5.4.3.jar:5.4.3]
... 6 more
Caused by: java.io.FileNotFoundException: \.\pipe\controller_log_8340 (The system cannot find the file specified)
at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_131]
at org.elasticsearch.xpack.ml.utils.NamedPipeHelper$PrivilegedInputPipeOpener.run(NamedPipeHelper.java:297) ~[?:?]
at org.elasticsearch.xpack.ml.utils.NamedPipeHelper$PrivilegedInputPipeOpener.run(NamedPipeHelper.java:286) ~[?:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_131]
at org.elasticsearch.xpack.ml.utils.NamedPipeHelper.openNamedPipeInputStream(NamedPipeHelper.java:139) ~[?:?]
at org.elasticsearch.xpack.ml.utils.NamedPipeHelper.openNamedPipeInputStream(NamedPipeHelper.java:106) ~[?:?]
at org.elasticsearch.xpack.ml.job.process.ProcessPipes.connectStreams(ProcessPipes.java:140) ~[?:?]
at org.elasticsearch.xpack.ml.job.process.NativeController.(NativeController.java:65) ~[?:?]
at org.elasticsearch.xpack.ml.job.process.NativeControllerHolder.getNativeController(NativeControllerHolder.java:50) ~[?:?]
at org.elasticsearch.xpack.ml.MachineLearning.createComponents(MachineLearning.java:280) ~[?:?]
at org.elasticsearch.xpack.XPackPlugin.createComponents(XPackPlugin.java:288) ~[?:?]
at org.elasticsearch.node.Node.lambda$new$7(Node.java:411) ~[elasticsearch-5.4.3.jar:5.4.3]
at java.util.stream.ReferencePipeline$7$1.accept(Unknown Source) ~[?:1.8.0_131]
... 6 more
now no good...darn it...
-
but uninstall x-pack
C:\EKDev\es5.4.3>bin\elasticsearch-plugin remove x-pack
-> removing [x-pack]...
-> preserving plugin config files [C:\EKDev\es5.4.3\config\x-pack] in case of upgrade; delete manually if not needed -
then all good again....
C:\EKDev\es5.4.3>bin\elasticsearch
[2017-06-30T15:23:34,828][INFO ][o.e.n.Node] [ek.data] initializing ...
[
[2017-06-30T15:23:50,924][INFO ][o.e.n.Node] [ek.data] started
[2017-06-30T15:24:08,640][INFO ][o.e.n.Node] [ek.data] closed
Terminate batch job (Y/N)? y
help/pointers gratefully received. I saw a thread on permissions (Debian?) but if good, then no good, then good again after 'remove' , I'm hoping security is not a prob? Perhaps I need to manually make log files?
Kind regards,
Emmet (elastic newbee)
