in order to install magento 2.4 i need to install elasticsearch 7.x in whm cpanel
but I get errors and the service does not start.
I followed this guide:
support.cpanel.net
but I have this error:
my /etc/sysconfig/elasticsearch file
elasticsearch elasticsearch-7.10.1-1.x86_64
CENTOS 7.9 xen hvm v92.0.6
but I get errors and the service does not start.
I followed this guide:
How To Install & Run Elasticsearch
Introduction Please bear in mind that this guide only explains how to install Elasticsearch Version: 6.8.12. Additionally, there is no information regarding the provision and configuration of Elas...
but I have this error:
Code:
[email protected] ~]# vim /etc/sysconfig/elasticsearch
[[email protected] ~]# systemctl daemon-reload
[[email protected] ~]# systemctl cat elasticsearch --no-pager | grep -Eiv "(^#.*|^$)" | grep -i TMPDIR
[[email protected] ~]# cat /etc/systemd/system/elasticsearch.service.d/tmp_dir
cat: /etc/systemd/system/elasticsearch.service.d/tmp_dir: No such file or directory
[[email protected] ~]# sudo cat /etc/systemd/system/elasticsearch.service.d/tmp_dir
cat: /etc/systemd/system/elasticsearch.service.d/tmp_dir: No such file or directory
[[email protected] ~]# systemctl daemon-reload
[[email protected] ~]# systemctl daemon-reload
[[email protected] ~]# systemctl cat elasticsearch --no-pager | grep -Eiv "(^#.*|^$)" | grep -i TMPDIR
[[email protected] ~]# vim /etc/sysconfig/elasticsearch
[[email protected] ~]# systemctl cat elasticsearch --no-pager | grep -Eiv "(^#.*|^$)" | grep -i TMPDIR
[[email protected] ~]# vim /etc/sysconfig/elasticsearch
[[email protected] ~]# systemctl daemon-reload
[[email protected] ~]# systemctl cat elasticsearch --no-pager | grep -Eiv "(^#.*|^$)" | grep -i TMPDIR
[[email protected] ~]# cat /etc/systemd/system/elasticsearch.service.d/tmp_dir
cat: /etc/systemd/system/elasticsearch.service.d/tmp_dir: No such file or directory
[[email protected] ~]# sudo cat /etc/systemd/system/elasticsearch.service.d/tmp_dir
cat: /etc/systemd/system/elasticsearch.service.d/tmp_dir: No such file or directory
[[email protected] ~]# /bin/systemctl start elasticsearch.service
Job for elasticsearch.service failed because the control process exited with error code. See "systemctl status elasticsearch.service" and "journalctl -xe" for details.
[[email protected] ~]# systemctl cat elasticsearch --no-pager | grep -Eiv "(^#.*|^$)" | grep -i TMPDIR
[[email protected] ~]# systemctl daemon-reload
[[email protected] ~]# systemctl cat elasticsearch --no-pager | grep -Eiv "(^#.*|^$)" | grep -i TMPDIR
[[email protected] ~]# cat /etc/systemd/system/elasticsearch.service.d/tmp_dir
cat: /etc/systemd/system/elasticsearch.service.d/tmp_dir: No such file or directory
[[email protected] ~]# systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2021-01-02 18:37:30 EET; 24min ago
Docs: https://www.elastic.co
Main PID: 3743 (code=exited, status=1/FAILURE)
Jan 02 18:37:30 srv6.le.com systemd-entrypoint[3743]: at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161)
Jan 02 18:37:30 srv6.le.com systemd-entrypoint[3743]: at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86)
Jan 02 18:37:30 srv6.le.com systemd-entrypoint[3743]: at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127)
Jan 02 18:37:30 srv6.le.com systemd-entrypoint[3743]: at org.elasticsearch.cli.Command.main(Command.java:90)
Jan 02 18:37:30 srv6.le.com systemd-entrypoint[3743]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126)
Jan 02 18:37:30 srv6.le.com systemd-entrypoint[3743]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92)
Jan 02 18:37:30 srv6.le.com systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Jan 02 18:37:30 srv6.le.com systemd[1]: Failed to start Elasticsearch.
Jan 02 18:37:30 srv6.le.com systemd[1]: Unit elasticsearch.service entered failed state.
Jan 02 18:37:30 le.com systemd[1]: elasticsearch.service failed.
[[email protected] ~]#
Code:
################################
# Elasticsearch
################################
# Elasticsearch home directory
#ES_HOME=/usr/share/elasticsearch
# Elasticsearch Java path
#JAVA_HOME=
#
#
#####AGGIUNTO A MANO--------------------------------------------------------????????
ES_TMPDIR=/tmp
#
# Elasticsearch configuration directory
# Note: this setting will be shared with command-line tools
ES_PATH_CONF=/etc/elasticsearch
# Elasticsearch PID directory
#PID_DIR=/var/run/elasticsearch
# Additional Java OPTS
#ES_JAVA_OPTS=
# Configure restart on package upgrade (true, every other setting will lead to not restarting)
#RESTART_ON_UPGRADE=true
################################
# Elasticsearch service
################################
# SysV init.d
# The number of seconds to wait before checking if Elasticsearch started successfully as a daemon process
ES_STARTUP_SLEEP_TIME=5
################################
# System properties
################################
# Specifies the maximum file descriptor number that can be opened by this process
# When using Systemd, this setting is ignored and the LimitNOFILE defined in
# /usr/lib/systemd/system/elasticsearch.service takes precedence
#MAX_OPEN_FILES=65535
# The maximum number of bytes of memory that may be locked into RAM
# Set to "unlimited" if you use the 'bootstrap.memory_lock: true' option
# in elasticsearch.yml.
# When using systemd, LimitMEMLOCK must be set in a unit file such as
# /etc/systemd/system/elasticsearch.service.d/override.conf.
#MAX_LOCKED_MEMORY=unlimited
# Maximum number of VMA (Virtual Memory Areas) a process can own
# When using Systemd, this setting is ignored and the 'vm.max_map_count'
# property is set at boot time in /usr/lib/sysctl.d/elasticsearch.conf
#MAX_MAP_COUNT=262144CENTOS 7.9 xen hvm v92.0.6
