# Elasticsearch can not be started by service **URL:** \ **Category:** Elasticsearch\ **Created:** [December 6, 2020, 11:39am UTC](https://discuss.elastic.co/t/elasticsearch-can-not-be-started-by-service/257773 "2020-12-06T11:39:14Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mkkang66](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@mkkang66](https://discuss.elastic.co/u/mkkang66)\ **Post date:** [December 6, 2020, 11:39am UTC](https://discuss.elastic.co/t/elasticsearch-can-not-be-started-by-service/257773/1 "2020-12-06T11:39:14Z")
I installed an elasticsearch 7.10.0 by tar.gz archives because my network is a closed network. I can run it as a deamon with ' ../bin/elasticsearch -d -p es.pid' but systemctl command can not be run. The followings are my server setting, service file and logs ------------------------------------------------------------------------------------- \* Server - CentOS 7.4 - Cloud Server \*Result of 'systemctl status elasticsearc.service' ● elasticsearch.service - ElasticSearch 7.10.0 Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Thu 2020-12-03 15:05:52 KST; 3s ago Docs: [https://www.elastic.co](https://www.elastic.co) Process: 25446 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DIR}/elasticsearch.pid --quiet (code=exited, status=143) Main PID: 25446 (code=exited, status=143) Dec 03 15:04:37 p-frida-pk1-e03 systemd[1]: Starting ElasticSearch 7.10.0... Dec 03 15:05:52 p-frida-pk1-e03 systemd[1]: elasticsearch.service start operation timed out. Terminating. Dec 03 15:05:52 p-frida-pk1-e03 systemd[1]: Failed to start ElasticSearch 7.10.0. Dec 03 15:05:52 p-frida-pk1-e03 systemd[1]: Unit elasticsearch.service entered failed state. Dec 03 15:05:52 p-frida-pk1-e03 systemd[1]: elasticsearch.service failed. \*Error Log ... [2020-12-02T17:51:58,699][INFO][o.e.p.PluginsService] [node-1] no plugins loaded [2020-12-02T17:51:58,774][INFO][o.e.e.NodeEnvironment] [node-1] using [1] data paths, mounts [[/data (10.220.190.107:/p\_frida\_pk1\_nas)]], net usable\_space [4.3tb], net total\_space [4.3tb], types [nfs] [2020-12-02T17:51:58,775][INFO][o.e.e.NodeEnvironment] [node-1] heap size [1gb], compressed ordinary object pointers [true] [2020-12-02T17:51:59,097][INFO][o.e.n.Node] [node-1] node name [node-1], node ID [aRZHNwmsS32V7tvXL1ysFQ], cluster name [elk-server], roles [transform, master, remote\_cluster\_client, data, ml, data\_content, data\_hot, data\_warm, data\_cold, ingest] [2020-12-02T17:52:03,325][INFO][o.e.x.m.p.l.CppLogMessageHandler] [node-1] [controller/1707] [Main.cc@114] controller (64 bit): Version 7.10.0 (Build ac991e2e31f99d) Copyright (c) 2020 Elasticsearch BV [2020-12-02T17:52:03,972][INFO][o.e.x.s.a.s.FileRolesStore] [node-1] parsed [0] roles from file [/etc/elasticsearch/roles.yml] [2020-12-02T17:52:05,560][INFO][o.e.t.NettyAllocator] [node-1] creating NettyAllocator with the following configs: [name=unpooled, suggested\_max\_allocation\_size=256kb, factors={es.unsafe.use\_unpooled\_allocator=null, g1gc\_enabled=true, g1gc\_region\_size=1mb, heap\_size=1gb}] [2020-12-02T17:52:05,660][INFO][o.e.d.DiscoveryModule] [node-1] using discovery type [zen] and seed hosts providers [settings] [2020-12-02T17:52:06,084][WARN][o.e.g.DanglingIndicesState] [node-1] gateway.auto\_import\_dangling\_indices is disabled, dangling indices will not be automatically detected or imported and must be managed manually [2020-12-02T17:52:06,474][INFO][o.e.n.Node] [node-1] initialized [2020-12-02T17:52:06,474][INFO][o.e.n.Node] [node-1] starting ... [2020-12-02T17:52:06,724][INFO][o.e.t.TransportService] [node-1] publish\_address {127.0.0.1:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300} [2020-12-02T17:52:07,207][WARN][o.e.b.BootstrapChecks] [node-1] max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144] [2020-12-02T17:52:07,207][WARN][o.e.b.BootstrapChecks] [node-1] the default discovery settings are unsuitable for production use; at least one of [discovery.seed\_hosts, discovery.seed\_providers, cluster.initial\_master\_nodes] must be configured [2020-12-02T17:52:07,209][INFO][o.e.c.c.Coordinator] [node-1] cluster UUID [GgY95KdmRQi7Y0VHz3Hbmw] [2020-12-02T17:52:07,227][INFO][o.e.c.c.ClusterBootstrapService] [node-1] no discovery configuration found, will perform best-effort cluster bootstrapping after [3s] unless existing master is discovered [2020-12-02T17:52:07,368][INFO][o.e.c.s.MasterService] [node-1] elected-as-master ([1] nodes joined)[{node-1}{aRZHNwmsS32V7tvXL1ysFQ}{KoQOdrzoT\_CCEwFUpzTsdg}{127.0.0.1}{127.0.0.1:9300}{cdhilmrstw}{ml.machine\_memory=25111715840, xpack.installed=true, transform.node=true, ml.max\_open\_jobs=20} elect leader, _BECOME\_MASTER\_TASK_, _FINISH\_ELECTION_], term: 13, version: 182, delta: master node changed {previous , current [{node-1}{aRZHNwmsS32V7tvXL1ysFQ}{KoQOdrzoT\_CCEwFUpzTsdg}{127.0.0.1}{127.0.0.1:9300}{cdhilmrstw}{ml.machine\_memory=25111715840, xpack.installed=true, transform.node=true, ml.max\_open\_jobs=20}]} [2020-12-02T17:52:07,517][INFO][o.e.c.s.ClusterApplierService] [node-1] master node changed {previous , current [{node-1}{aRZHNwmsS32V7tvXL1ysFQ}{KoQOdrzoT\_CCEwFUpzTsdg}{127.0.0.1}{127.0.0.1:9300}{cdhilmrstw}{ml.machine\_memory=25111715840, xpack.installed=true, transform.node=true, ml.max\_open\_jobs=20}]}, term: 13, version: 182, reason: Publication{term=13, version=182} [2020-12-02T17:52:07,620][INFO][o.e.h.AbstractHttpServerTransport] [node-1] publish\_address {127.0.0.1:9200}, bound\_addresses {[::1]:9200}, {127.0.0.1:9200} [2020-12-02T17:52:07,621][INFO][o.e.n.Node] [node-1] started [2020-12-02T17:52:07,884][INFO][o.e.l.LicenseService] [node-1] license [f93e3bd4-e269-4db1-a5fc-65ddaa48e7d0] mode [basic] - valid [2020-12-02T17:52:07,886][INFO][o.e.x.s.s.SecurityStatusChangeListener] [node-1] Active license is now [BASIC]; Security is disabled [2020-12-02T17:52:07,892][INFO][o.e.g.GatewayService] [node-1] recovered [6] indices into cluster\_state [2020-12-02T17:52:09,684][INFO][o.e.c.r.a.AllocationService] [node-1] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[ilm-history-3-000001][0]]]). [2020-12-02T17:53:00,392][INFO][o.e.n.Node] [node-1] stopping ... [2020-12-02T17:53:00,396][INFO][o.e.x.w.WatcherService] [node-1] stopping watch service, reason [shutdown initiated] [2020-12-02T17:53:00,396][INFO][o.e.x.m.p.l.CppLogMessageHandler] [node-1] [controller/1707] [Main.cc@154] ML controller exiting [2020-12-02T17:53:00,397][INFO][o.e.x.w.WatcherLifeCycleService] [node-1] watcher has stopped and shutdown [2020-12-02T17:53:00,397][INFO][o.e.x.m.p.NativeController] [node-1] Native controller process has stopped - no new native processes can be started [2020-12-02T17:53:00,639][INFO][o.e.n.Node] [node-1] stopped [2020-12-02T17:53:00,639][INFO][o.e.n.Node] [node-1] closing ... [2020-12-02T17:53:00,651][INFO][o.e.n.Node] [node-1] closed - Elasticsearch service File [Unit] Description=ElasticSearch 7.10.0 Documentation=https://www.elastic.co Wants=network-online.target After=network-online.target [Service] Type=notify RuntimeDirectory=elasticsearch PrivateTmp=true Environment=ES\_HOME=/usr/share/elasticsearch Environment=ES\_PATH\_CONF=/etc/elasticsearch Environment=PID\_DIR=/var/run/elasticsearch Environment=ES\_SD\_NOTIFY=true EnvironmentFile=-/etc/sysconfig/elasticsearch WorkingDirectory=/usr/share/elasticsearch User=opr Group=opr ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DIR}/elasticsearch.pid --quiet # StandardOutput is configured to redirect to journalctl since # some error messages may be logged in standard output before # elasticsearch logging system is initialized. Elasticsearch # stores its logs in /var/log/elasticsearch and does not use # journalctl by default. If you also want to enable journalctl # logging, you can simply remove the "quiet" option from ExecStart. StandardOutput=journal StandardError=inherit # Specifies the maximum file descriptor number that can be opened by this process LimitNOFILE=65535 # Specifies the maximum number of processes LimitNPROC=4096 # Specifies the maximum size of virtual memory LimitAS=infinity # Specifies the maximum file size LimitFSIZE=infinity # Disable timeout logic and wait until process is stopped TimeoutStopSec=0 # SIGTERM signal is used to stop the Java process KillSignal=SIGTERM # Send the signal only to the JVM rather than its control group KillMode=process # Java process is never killed SendSIGKILL=no # When a JVM receives a SIGTERM signal it exits with code 143 SuccessExitStatus=143 # Allow a slow startup before the systemd notifier module kicks in to extend the timeout TimeoutStartSec=75 [Install] WantedBy=multi-user.target # Built for {project.name}-{project.version} (${project.name}) ------------------------------------------------------------------------------------------------ Owner of related directories is 'opr'. Can you help me? ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [December 6, 2020, 3:01pm UTC](https://discuss.elastic.co/t/elasticsearch-can-not-be-started-by-service/257773/2 "2020-12-06T15:01:51Z")
When you start from the command line, are your root? If so, you probably get unlimited resources. Systemd will usually use a different id that may be subject to limits. Some doc is in this part [https://www.elastic.co/guide/en/elasticsearch/reference/current/file-descriptors.html#file-descriptors](https://www.elastic.co/guide/en/elasticsearch/reference/current/file-descriptors.html#file-descriptors) But I don't see memory limits right now, but I'm betting it's a ulimit thing. ---
**Author:** ![mkkang66](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@mkkang66](https://discuss.elastic.co/u/mkkang66)\ **Post date:** [December 7, 2020, 12:53am UTC](https://discuss.elastic.co/t/elasticsearch-can-not-be-started-by-service/257773/3 "2020-12-07T00:53:19Z")
Thanks for your reply. Elasticsearch from the command line is started by id 'opr', not 'root'. I added the following line to this file'/etc/security/limits.conf' elasticsearch - nofile 65535 and added this file '/etc/systemd/system/elasticsearch.service.d/override.conf' with the following lines. [Service] LimitMEMLOCK=infinity But result is same. ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [December 7, 2020, 3:55am UTC](https://discuss.elastic.co/t/elasticsearch-can-not-be-started-by-service/257773/4 "2020-12-07T03:55:33Z")
> ---
**Author:** ![vincenbr](https://avatars.discourse-cdn.com/v4/letter/v/8edcca/32.png) [@vincenbr](https://discuss.elastic.co/u/vincenbr)\ **Post date:** [December 7, 2020, 9:52am UTC](https://discuss.elastic.co/t/elasticsearch-can-not-be-started-by-service/257773/5 "2020-12-07T09:52:07Z")
Hi, When you install elasticsearch with a plain tarball, you have to configure manually the virtual memory setting as per: [https://www.elastic.co/guide/en/elasticsearch/reference/7.10/vm-max-map-count.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/vm-max-map-count.html) Besides, you have the bootstrap checks running, their role is to help elastic from running if not properly configured (for safety reasons). If your goal is to run a single-node install, check your elasticsearch.yml and set `discovery-type` to `single-node` as per [https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 4, 2021, 9:52am UTC](https://discuss.elastic.co/t/elasticsearch-can-not-be-started-by-service/257773/6 "2021-01-04T09:52:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.