Kibana can not use x-pack feature

chenjienn · February 3, 2019, 5:41am

I have set up elasticsearch cluster and try to use kibana, but it seems the kibana can not obtained the x-pack information

here is my kibana and es config

server.host: "10.18.1.50"
server.name: "mdw_dev"
elasticsearch.url: "http://10.18.1.54:9200"
elasticsearch.username: "kibana"
elasticsearch.password: "MvHuH7yb2f9ZY1WgXFvh"

logging.dest: /var/log/kibana/kibana.log

cluster.name: mdw_dev

node.name: ${HOSTNAME}
node.master: true
node.data: true
node.ingest: true

path.data: /app/elasticsearch/data

path.logs: /app/elasticsearch/log

network.host: 10.18.1.54

discovery.zen.ping.unicast.hosts: ["10.18.1.53:9300", "10.18.1.54:9300"]

discovery.zen.minimum_master_nodes: 1

xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: /app/elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: /app/elastic-certificates.p12
action.auto_create_index: .security,.monitoring*,.watches,.triggered_watches,.watcher-history*,.ml*,spn-*,*

warkolm · February 3, 2019, 6:13am

Please don't post pictures of text, they are difficult to read and some people may not be even able to see them

What version are you on?
What is the output of the _xpack API? (ie what license are you using)

chenjienn · February 3, 2019, 6:38am

sorry, it's my first time to use the forum

the es & kibana version is 6.5.4

the output for curl -u elastic:3RVialJiyAjS03Z75P1A 'http://10.18.1.54:9200/_xpack' is empty, and es throws the following exception:

[2019-02-03T14:34:28,482][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [MDWDevEsMaster02] fatal error in thread [elasticsearch[MDWDevEsMaster02][get][T#1]], exiting
java.lang.NoClassDefFoundError: Could not initialize class org.elasticsearch.xpack.core.XPackBuild
        at org.elasticsearch.xpack.core.action.TransportXPackInfoAction.doExecute(TransportXPackInfoAction.java:50) ~[?:?]
        at org.elasticsearch.xpack.core.action.TransportXPackInfoAction.doExecute(TransportXPackInfoAction.java:29) ~[?:?]
        at org.elasticsearch.action.support.TransportAction.doExecute(TransportAction.java:143) ~[elasticsearch-6.5.4.jar:6.5.4]
        at org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:167) ~[elasticsearch-6.5.4.jar:6.5.4]
        at org.elasticsearch.xpack.security.action.filter.SecurityActionFilter.lambda$apply$0(SecurityActionFilter.java:90) ~[?:?]
        at org.elasticsearch.action.ActionListener$1.onResponse(ActionListener.java:60) ~[elasticsearch-6.5.4.jar:6.5.4]
        at org.elasticsearch.xpack.security.action.filter.SecurityActionFilter.lambda$authorizeRequest$4(SecurityActionFilter.java:179) ~[?:?]
        at org.elasticsearch.xpack.security.authz.AuthorizationUtils$AsyncAuthorizer.maybeRun(AuthorizationUtils.java:173) ~[?:?]
        at  ........

by the way, my license is trial

warkolm · February 3, 2019, 6:49am

What do your Elasticsearch logs show?

chenjienn · February 3, 2019, 6:51am

the log is just throws the exception as mentioned above

warkolm · February 3, 2019, 6:52am

There's nothing before/after that?

chenjienn · February 3, 2019, 6:55am

the before is:
[2019-02-03T14:34:04,717][INFO ][o.e.x.s.a.s.FileRolesStore] [MDWDevEsMaster02] parsed [0] roles from file [/etc/elasticsearch/roles.yml]
[2019-02-03T14:34:05,561][INFO ][o.e.x.m.j.p.l.CppLogMessageHandler] [MDWDevEsMaster02] [controller/118186] [Main.cc@109] controller (64 bit): Version 6.5.4 (Build b616085ef32393) Copyright (c) 2018 Elasticsearch BV
[2019-02-03T14:34:06,309][DEBUG][o.e.a.ActionModule ] [MDWDevEsMaster02] Using REST wrapper from plugin org.elasticsearch.xpack.security.Security
[2019-02-03T14:34:06,728][INFO ][o.e.d.DiscoveryModule ] [MDWDevEsMaster02] using discovery type [zen] and host providers [settings]
[2019-02-03T14:34:08,215][INFO ][o.e.n.Node ] [MDWDevEsMaster02] initialized
[2019-02-03T14:34:08,215][INFO ][o.e.n.Node ] [MDWDevEsMaster02] starting ...
[2019-02-03T14:34:08,480][INFO ][o.e.t.TransportService ] [MDWDevEsMaster02] publish_address {10.18.1.54:9300}, bound_addresses {10.18.1.54:9300}
[2019-02-03T14:34:08,515][INFO ][o.e.b.BootstrapChecks ] [MDWDevEsMaster02] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2019-02-03T14:34:12,277][INFO ][o.e.c.s.ClusterApplierService] [MDWDevEsMaster02] detected_master {MDWDevEsMaster01}{MBwCwYhFQxyQoQZ_alb6Qg}{YhmAQgxsSkS44xAiMAfz_A}{10.18.1.53}{10.18.1.53:9300}{ml.machine_memory=8176611328, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true}, added {{MDWDevEsMaster01}{MBwCwYhFQxyQoQZ_alb6Qg}{YhmAQgxsSkS44xAiMAfz_A}{10.18.1.53}{10.18.1.53:9300}{ml.machine_memory=8176611328, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true},}, reason: apply cluster state (from master [master {MDWDevEsMaster01}{MBwCwYhFQxyQoQZ_alb6Qg}{YhmAQgxsSkS44xAiMAfz_A}{10.18.1.53}{10.18.1.53:9300}{ml.machine_memory=8176611328, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true} committed version [47]])
[2019-02-03T14:34:12,746][INFO ][o.e.x.s.a.TokenService ] [MDWDevEsMaster02] refresh keys
[2019-02-03T14:34:13,182][INFO ][o.e.x.s.a.TokenService ] [MDWDevEsMaster02] refreshed keys
[2019-02-03T14:34:13,240][INFO ][o.e.l.LicenseService ] [MDWDevEsMaster02] license [bc13a206-c347-4594-90ee-13f7d82d5dfd] mode [trial] - valid
[2019-02-03T14:34:13,276][INFO ][o.e.x.s.t.n.SecurityNetty4HttpServerTransport] [MDWDevEsMaster02] publish_address {10.18.1.54:9200}, bound_addresses {10.18.1.54:9200}
[2019-02-03T14:34:13,276][INFO ][o.e.n.Node ] [MDWDevEsMaster02] started
[2019-02-03T14:34:28,482][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [MDWDevEsMaster02] fatal error in thread [elasticsearch[MDWDevEsMaster02][get][T#1]], exiting
java.lang.NoClassDefFoundError: Could not initialize class org.elasticsearch.xpack.core.XPackBuild

the after is the rest of the exception stack and it is too long to paste on board

chenjienn · February 3, 2019, 8:27am

i have fixed this problem, thank you for your previously help !

warkolm · February 3, 2019, 9:00am

How did you fix it? Your solution might help others in future.

chenjienn · February 3, 2019, 9:19am

i modified the x-pack-core-6.5.4.jar before , so i just replaced it by the previous origin jar

warkolm · February 3, 2019, 9:21am

Oh. Why did you modify it?

chenjienn · February 3, 2019, 10:05am

i try to bypass validation of the x-pack for experiment

warkolm · February 3, 2019, 8:53pm

That's not really cool at all.
Not only is it against the terms of the license, you're abusing our good faith.

chenjienn · February 4, 2019, 3:16am

sorry about that, i will not do that again

system · March 4, 2019, 3:16am

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.