{"statusCode":503,"error":"Service Unavailable","message":"License is not available."}

Elastic Stack Elasticsearch
1

Hello Team,

I have installed elastic version 8.5.2 on three node cluster, it runs good.

when I take down down node 2 (master -2), cluster is up and running with other two nodes.

when I take down down node 3 (master -3), cluster is up and running with other two nodes.

but when I take down down node 1 (master -1), elasitc cluster is down with below error on Kibana.

{"statusCode":503,"error":"Service Unavailable","message":"License is not available."}

Please find the elastic configuration below.

cluster.name: dataseers-3-0
path.data: /home/elasticsearch
path.logs: /home/logs/elasticsearch
network.host: ["127.0.0.1","10.XX.XX.XXX","localhost"]
network.bind_host : 10.XX.XX.XXX
http.port: 9200
discovery.seed_hosts: ["10.XX.X.XX","10.XX.X.XX","10.XX.X.XX"]
cluster.initial_master_nodes: ["master-1","master-2", "master-3"]
xpack.security.enabled: true
xpack.security.enrollment.enabled: true
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
http.host: 0.0.0.0
transport.host: 0.0.0.0

It would be great if you guys can help me on this, Thanks. looking forward.

2

What does your kibana.yml looks like? Please share it.

3

Thanks for the response Leandro, below is the kibana config.

server.port: 5601
server.host: "10.XX.X.XXX"
server.ssl.enabled: true
server.ssl.certificate: /etc/kibana/portal.includesprivatekey.pem
server.ssl.key: /etc/kibana/portal.includesprivatekey.pem
server.ssl.keyPassphrase: XXXXXXXXXX
logging:
  appenders:
    file:
      type: file
      fileName: /home/logs/kibana/kibana.log
      layout:
        type: json
  root:
    appenders:
      - default
      - file
xpack.encryptedSavedObjects.encryptionKey: 6ad3cbc280037ce3bccd8bbb24c7ed13
xpack.reporting.encryptionKey: 06e8ae9b584894dXXXXXXXXXXXXXX
xpack.security.encryptionKey: 301df4dfd6faa2aXXXXXXXXXXXXXXX
xpack.security.session.idleTimeout: "10m"
xpack.security.session.lifespan: "8h"
xpack.reporting.csv.maxSizeBytes: 1048576000
elasticsearch.hosts: ['https://10.XX.X.XX:9200','https://10.XX.XX.XXX:9200','https://10.X.XX.XXX:9200']
elasticsearch.serviceAccountToken: AAEAAWVsYXXXXXXXXXXXXXXXXzLXRva2VuLTE2NzI5NDA1NjA5NjM6YXpYNE1qc1
elasticsearch.ssl.certificateAuthorities: [/var/lib/kibana/ca_1672940562290.crt]
xpack.fleet.outputs: [{id: fleet-default-output, name: default, is_default: true, is_default_monitoring: true, type: elasticsearch, hosts: ['https://10.XX.XX.XXX:9200','https://10.XX.XX.XXX:9200','https://10.XX.XX.XXX:9200'], ca_trusted_fingerprint: 8b14f638772df1XXXXXXXXXXXXXX}]
4

I've seen similar issues to this posted before, but don't seem to see any solutions for this specific problem.

5

Any help would be awesome, thanks

6

Hello,

I see no issue in your kibana.yml, all your 3 nodes are listed in elasticsearch.hosts, so Kibana should try another node when your master is down, which seems to be the issue.

Did this work after you give some time for your cluster to elect a new master? If it this keep happening you will need to share the logs of your nodes when you take one down.

7

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