https://bugzilla.redhat.com/show_bug.cgi?id=902086 --- Comment #100 from jiri vanek <jvanek@xxxxxxxxxx> --- (In reply to Zbigniew Jędrzejewski-Szmek from comment #93) > Running /usr/bin/elasticsearch: > /usr/bin/build-classpath: Unable to execute xmvn-resolve. > /usr/bin/build-classpath: Make sure that XMvn is installed and M2_HOME is > set correctly. > ... > /usr/bin/build-classpath: error: Some specified jars were not found > Exception in thread "main" java.lang.NoClassDefFoundError: > com/google/common/collect/ImmutableMap > at > org.elasticsearch.common.settings.ImmutableSettings.<init>(ImmutableSettings. > java:65) > at > org.elasticsearch.common.settings.ImmutableSettings$Builder. > build(ImmutableSettings.java:1077) > at > org.elasticsearch.common.settings.ImmutableSettings. > <clinit>(ImmutableSettings.java:57) > at > org.elasticsearch.common.settings.ImmutableSettings$Builder. > build(ImmutableSettings.java:1077) > at > org.elasticsearch.common.settings.ImmutableSettings$Builder. > <clinit>(ImmutableSettings.java:664) > at org.elasticsearch.bootstrap.Bootstrap.initialSettings(Bootstrap.java:106) > at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:177) > at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) > Caused by: java.lang.ClassNotFoundException: > com.google.common.collect.ImmutableMap > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 8 more > > This seems to be a bug in build-classpath. I'll file a bug. According to 1194110, I have added the depndence. The only remaing artifact on build-classapth list is io.netty:netty:3.9.3.Final. It was not working for me with package name. If it is fixed, then the depndence can be removed again. > > After I install xmvn: > $ elasticsearch > Feb 18, 2015 10:56:21 PM org.elasticsearch.node.internal.InternalNode <init> > INFO: [Grasshopper II] version[1.4.3], pid[7546], build[${build/NA] > Feb 18, 2015 10:56:21 PM org.elasticsearch.node.internal.InternalNode <init> > INFO: [Grasshopper II] initializing ... > Feb 18, 2015 10:56:21 PM org.elasticsearch.plugins.PluginsService <init> > INFO: [Grasshopper II] loaded [], sites [] > Feb 18, 2015 10:56:23 PM org.elasticsearch.bootstrap.Bootstrap main > SEVERE: {1.4.3}: Initialization Failed ... > - ExecutionError[java.lang.NoClassDefFoundError: > org/apache/lucene/sandbox/queries/FuzzyLikeThisQuery] > NoClassDefFoundError[org/apache/lucene/sandbox/queries/FuzzyLikeThisQuery] > > ClassNotFoundException[org.apache.lucene.sandbox.queries.FuzzyLikeThisQuery] > > It seems lucene-sandbox has to be added to the script. With that added, it > seems to run fine and to respond to commands. added. > > First question: why would anyone ever run elasticsearch manually? It seem I would :) > that the script > could be moved to /usr/libexec or somewhere. Anyway I agree it is rare case. I moved the script as you wished. > > Second question: elasticsearch listens on 0.0.0.0:9200 by default, accepting > commands from the internet. > This has to be fixed. Maybe a default configuration to limit it to ::1 > should be added. I don't know what, > but something has to be done. Afaik no simple option here. The firewalld shopud do this job or any other deployment tool like nginx or similar... > > Finally: I promised to start with a service file. I'll attach one in a > moment that should be good enough as a starting point. Its main limitation > is that elasticsearch runs as Type=simple, so systemd cannot tell when it is Thank you . Included on my best, although I ddont have much experience with packaging services. (moreover walked through guidelines..) > ready to service requests. Two possible solutions: first, add notifications > and turn elasticsearch into Type=notify. Second, actually better, add socket > activation. Both require upstream changes so I guess we can leave them for > the future. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review