[elasticsearch on aarch64] systemd start fails

[rhagu]

Hi,

I installed elasticsearch on archlinux arm aarch64 on a raspberry pi 3b via pacman. Filebeat worked without a problem, but elasticsearch showed an error at install (I get the same message with a reinstall):

(4/5) Creating temporary files... error: command failed to execute correctly

$this->bbcode_second_pass_code('', '
[alarm@alarm ~]$ sudo pacman -S elasticsearch
[sudo] password for alarm:
warning: elasticsearch-7.1.0-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) elasticsearch-7.1.0-1

Total Installed Size: 103.40 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [##########################################################################] 100%
(1/1) checking package integrity [##########################################################################] 100%
(1/1) loading package files [##########################################################################] 100%
(1/1) checking for file conflicts [##########################################################################] 100%
(1/1) checking available disk space [##########################################################################] 100%
:: Processing package changes...
(1/1) reinstalling elasticsearch [##########################################################################] 100%
:: Running post-transaction hooks...
(1/5) Reloading system manager configuration...
(2/5) Applying kernel sysctl settings...
(3/5) Creating system user accounts...
(4/5) Creating temporary files...
error: command failed to execute correctly
(5/5) Arming ConditionNeedsUpdate...
')

When I try to do systemctl start elasticsearch it takes some time and fails:

$this->bbcode_second_pass_code('', '
[alarm@alarm ~]$ sudo systemctl status elasticsearch
* elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: http://www.elastic.co
[alarm@alarm ~]$ sudo systemctl start elasticsearch
Job for elasticsearch.service failed because the control process exited with error code.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.
[alarm@alarm ~]$ sudo systemctl status elasticsearch
* elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2019-06-02 21:44:43 UTC; 1s ago
Docs: http://www.elastic.co
Process: 896 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -d -p /run/elasticsearch/elasticsearch.pid (code=exited, status=1/FAILURE)

Jun 02 21:44:43 alarm systemd[1]: elasticsearch.service: Service RestartSec=100ms expired, scheduling restart.
Jun 02 21:44:43 alarm systemd[1]: elasticsearch.service: Scheduled restart job, restart counter is at 5.
Jun 02 21:44:43 alarm systemd[1]: Stopped Elasticsearch.
Jun 02 21:44:43 alarm systemd[1]: elasticsearch.service: Start request repeated too quickly.
Jun 02 21:44:43 alarm systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
Jun 02 21:44:43 alarm systemd[1]: Failed to start Elasticsearch.
')

What can I do to start elasticsearch at boot?

kind regards,
rhagu