RainTown
February 11, 2025, 1:19pm
10
I did the quick test above, spun up a c8g.medium EC2 instance, and get same error as you with 8.14.3, so its not your in-house created ami.
Ah, so as the problem is just with the bundled node:
# /usr/share/kibana/node/bin/node
Illegal instruction (core dumped)
so I tried with the latest kibana release (8.17.2) and node there works OK, as does kibana in my very brief testing.
Maybe you were just unlucky with 8.14.3 build, in 8.17.3 its moved around a bit and is now at
# /usr/share/kibana/node/glibc-217/bin/node
Welcome to Node.js v20.18.2.
Type ".help" for more information.
# uname -a
Linux ip-172-31-10-19.eu-central-1.compute.internal 6.1.127-135.201.amzn2023.aarch64 #1 SMP Tue Jan 28 23:19:27 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
I guess if you have Elastic support contract you might be able to get them to release a patch/fix for 8.14.3 ? Otherwise, an upgrade should resolve it.
opened 11:58AM - 12 Nov 24 UTC
closed 01:18AM - 31 Jan 25 UTC
bug
Team:Operations
**Kibana version:**
7.17.25
**Elasticsearch version:**
7.17.25
**Server OS vers… ion:**
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy
**Original install method (e.g. download page, yum, from source, etc.):**
apt install (https://www.elastic.co/guide/en/kibana/7.17/settings.html)
**Describe the bug:**
getting "core-dump" errors on the ec2 r8g family instance.
when installing Kibana and trying to run the service.
switching to r7g works fine
elasticsearch 7.17.25 on r8g works fine
**Steps to reproduce:**
1. setup new r8g instance
2. installing elastic and kibana
3. run kibana
**Provide logs and/or server output (if relevant):**
`root@ip-xxxxxx:/home/ubuntu# sudo apt-get update && sudo apt-get install kibana
Hit:1 https://artifacts.elastic.co/packages/7.x/apt stable InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
Hit:3 http://eu-central-1b.clouds.ports.ubuntu.com/ubuntu-ports jammy InRelease
Hit:4 http://eu-central-1b.clouds.ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
Hit:5 http://eu-central-1b.clouds.ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
kibana
0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/304 MB of archives.
After this operation, 821 MB of additional disk space will be used.
Selecting previously unselected package kibana.
(Reading database ... 67265 files and directories currently installed.)
Preparing to unpack .../kibana_7.17.25_arm64.deb ...
Unpacking kibana (7.17.25) ...
Setting up kibana (7.17.25) ...
Creating kibana group... OK
Creating kibana user... OK
Illegal instruction (core dumped)
dpkg: error processing package kibana (--configure):
installed kibana package post-installation script subprocess returned error exit status 132
Errors were encountered while processing:
kibana
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
`
`× kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Tue 2024-11-12 10:43:16 UTC; 2min 10s ago
Docs: https://www.elastic.co
Process: 3252 ExecStart=/usr/share/kibana/bin/kibana --logging.dest=/var/log/kibana/kibana.lo>
Main PID: 3252 (code=dumped, signal=ILL)
CPU: 8ms
Nov 12 10:43:16 ip-172-31-67-169 systemd[1]: kibana.service: Scheduled restart job, restart count>
Nov 12 10:43:16 ip-172-31-67-169 systemd[1]: Stopped Kibana.
Nov 12 10:43:16 ip-172-31-67-169 systemd[1]: kibana.service: Start request repeated too quickly.
Nov 12 10:43:16 ip-172-31-67-169 systemd[1]: kibana.service: Failed with result 'core-dump'.
Nov 12 10:43:16 ip-172-31-67-169 systemd[1]: Failed to start Kibana.
`
**Any additional context:**
is likely the bug